1. Home
  2. ❯
  3. Companies
  4. ❯
  5. GitHub
  6. ❯
  7. Outage Map
GitHub

GitHub Outage Map

The map below depicts the most recent cities worldwide where GitHub users have reported problems and outages. If you are having an issue with GitHub, make sure to submit a report below

Loading map, please wait...

The heatmap above shows where the most recent user-submitted and social media reports are geographically clustered. The density of these reports is depicted by the color scale as shown below.

GitHub users affected:

Less
More
Check Current Status

GitHub is a company that provides hosting for software development and version control using Git. It offers the distributed version control and source code management functionality of Git, plus its own features.

Most Affected Locations

Outage reports and issues in the past 15 days originated from:

Location Reports
Itapema, SC 1
Cleveland, TN 1
Tlalpan, CDMX 1
Quilmes, BA 1
Bengaluru, KA 1
Yokohama, Kanagawa 1
Gustavo Adolfo Madero, CDMX 1
Nice, Provence-Alpes-Côte d'Azur 1
Brasília, DF 1
Montataire, Hauts-de-France 3
Colima, COL 1
Poblete, Castille-La Mancha 1
Ronda, Andalusia 1
Hernani, Basque Country 1
Tortosa, Catalonia 1
Culiacán, SIN 1
Haarlem, nh 1
Villemomble, Île-de-France 1
Bordeaux, Nouvelle-Aquitaine 1
Ingolstadt, Bavaria 1
Paris, Île-de-France 1
Berlin, Berlin 1
Dortmund, NRW 1
Davenport, IA 1
St Helens, England 1
Nové Strašecí, Central Bohemia 1
Check Current Status

Community Discussion

Tips? Frustrations? Share them here. Useful comments include a description of the problem, city and postal code.

Beware of "support numbers" or "recovery" accounts that might be posted below. Make sure to report and downvote those comments. Avoid posting your personal information.

GitHub Issues Reports

Latest outage, problems and issue reports in social media:

  • polsia
    Polsia (@polsia) reported

    Every engineering team loses 2+ hours a week to CI failures. FixOS is an autonomous AI agent that watches your GitHub repos, diagnoses broken pipelines, and commits fixes — without you. No more triage. No more context-switching. Your CI runs on autopilot.

  • _ueaj
    ueaj (@_ueaj) reported

    I would like to switch to using the desktop app for everything even if it's only in a semi-usable state but ideally there is somewhere I can submit complaints or issues or someone active on twitter for the desktop app. Github would probably be drowned out by spam. Are you part of the app team, is it fine if I ping you in the future as well?

  • pedri232
    javier perez 🫎 (@pedri232) reported

    GM from GMT+7: wired a ritual to a GitHub issue, ran the steps and the issue auto closed. an onchain receipt appeared in repo activity. tiny ritual, audit trail @ritialfnd

  • nick_lewis
    Nick Lewis (@nick_lewis) reported

    My dev setup: - GitHub with branch protection - Claude Code for day-to-day building - Vercel and Railway for deployment - Sentry for error monitoring - UptimeRobot for endpoint checks - 1Password for secrets - Cloudflare for DNS and CDN - Postman for API testing - Automated backups to S3 Anything I'm missing?

  • Starwatcher_vc
    Ernest (@Starwatcher_vc) reported

    @asmartbear I never had liked github issues and used Liner. When I leaned on CC I realized that it is really good with github cli and so I ditched Linear because CC was so much better with github infra. Have had couple other such trade offs

  • HackingLZ
    Justin Elze (@HackingLZ) reported

    @5mukx @kmkz_security @github Someone over there can fix it but unless you complain to the right people it could take weeks.

  • JennyZhangqb6b
    Jenny (@JennyZhangqb6b) reported

    The loudest devs are screaming that Skills killed MCP. For one scenario they're right. A coding agent running on a laptop with a Skill that calls a CLI (`gh` for GitHub, `aws` for Amazon) does the same job as a whole MCP server. The CLI already has auth. The CLI already has tokens. The CLI already works. On a developer's MacBook, Skills eat MCP's lunch. That part is real.

  • edmundumbao
    Ed Umbao (@edmundumbao) reported

    The messy parts taught me the most: - GitHub branches - `.env` files - API key safety - missing variables - Python indentation errors - running Streamlit locally

  • griefcliff
    Griefcliff (@griefcliff) reported

    @___frye & GitHub is down a lot more often

  • Karanx274
    karan (@Karanx274) reported

    I cut my scraping costs by 30% this month. Some Italian devs dropped a Scrapping Ai on GitHub. MIT licensed. Open source. 23,000 stars in a few months. It works across LLMs too, so you can plug it into OpenAI, Gemini, Grok, or run it locally with Ollama if you want to keep things in house. We were on Apify before this. And honestly, it was a slow bleed. Credits getting eaten alive, and because we run scrapes across multiple platforms > listings, reviews, e-comm, profiles ,we were basically duct taping workflows together. We're pulling structured data from pages we used to write custom scripts for. It's insane that it's free. Comment "scrape" and I'll DM you the GitHub link

  • BrenBuilds
    Bren (@BrenBuilds) reported

    @satyanadella No one cares. You destroyed trust and transparency in GitHub Copilot licensing model. Fix it.

  • NostaIgicGareth
    nostalgicgareth (space/acc) (@NostaIgicGareth) reported

    @Unmei_Dev Download PunpFun app - login w ur GitHub

  • deepakThamizhK
    Deepak K (@deepakThamizhK) reported

    @artman Paying users are filing GitHub issues saying GPT-5.5/Codex got noticeably worse mid-cycle more confused, loses context, needs constant correction. did quality drop before or after your renewal date?

  • welbeebee
    welbee 🐝 (@welbeebee) reported

    @ankkala the problem w/ this mentality is u can end up w/ a lot of bloat. it's better to put this kind of advanced feature-set into a github, tutorial, or demo.

  • BuildFastWithAI
    Build Fast with AI (@BuildFastWithAI) reported

    Hermes Agent vs OpenClaw using QWEN 35B The idea was to compare popular harnesses running on the local ai models. We took Hermes and OpenClaw, connected them to QWEN, run a task. We asked agents to scrape GitHub star history for both tools, find what caused the growth spikes, build a live dashboard in the browser. QWEN 3.6 35B OpenClaw: 203k tokens, 12m 01s — wrote a bash script Hermes: 257k tokens, 33m 01s — wrote a SKILL.md OpenClaw hit GitHub API, got truncated responses, paginated through contributors, pulled star-history JSON, found a security incident in OpenClaw's history, fetched SVGs, fixed broken HTML from trimming, rewrote it clean. Hermes parallel tool calls across GitHub API, web search, and browser. Hit Google rate limit, auto-switched to DuckDuckGo. Fetched article contents, mapped viral moments, then built the dashboard. Both shipped a live dashboard with star growth charts and spike annotations. Do someone run harnesses with local models for everyday?

Check Current Status