1. Home
  2. Companies
  3. GitHub
  4. 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
Inverness, Scotland 1
Quito, Pichincha 2
Junín, Manabí 1
Guadalajara, JAL 1
Paris, Île-de-France 6
São Paulo, SP 1
Ipauçu, SP 1
Vigo, Galicia 1
Tel Aviv, Tel Aviv 1
Éragny, Île-de-France 1
Saltillo, COA 2
Montlhéry, Île-de-France 1
Aulnay-sous-Bois, Île-de-France 1
Granada, Andalusia 1
Vernon, Normandy 1
Township of Evan, KS 1
Madrid, Madrid 1
Bogotá, Bogota D.C. 1
Lyon, Auvergne-Rhône-Alpes 1
Lima, Lima 1
Aix-en-Provence, Provence-Alpes-Côte d'Azur 1
Trento, Trentino-Alto Adige 1
Le Chambon-Feugerolles, Auvergne-Rhône-Alpes 1
Antananarivo, Analamanga 1
Lure, Bourgogne-Franche-Comté 1
Ashkelon, Southern District 1
Veigné, Centre 1
Saint-Paul, Réunion 2
Mexico City, CDMX 1
León de los Aldama, GUA 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:

  • Saasterix
    Alex (@Saasterix) reported

    @iannuttall How can you build things online since 21 years but paying for GitHub is an issue?

  • Anbeeld
    Anbeeld (@Anbeeld) reported

    Have you already set up your global AGENTS.md and CLAUDE.md, or are you still leaving free model performance on the table? Agents are already good enough at coding that a lot of the remaining failures are just bad operating discipline. They guess instead of verifying. They expand scope. They skip validation. They work sequentially when they could parallelize. They declare victory without evidence. I put the rules I actually want agents to follow into global instructions and battle-tested them across Codex, Claude, and open-weight models. They worked pretty well, so I released them as a GitHub repo. Use my AGENTS.md or write your own. Just don't leave it empty when you could use it to fix whatever keeps annoying you.

  • realjdoerksen
    John Doerksen (@realjdoerksen) reported

    the people who run GitHub, railway should be tarred and feathered for slowing down all development. these sites are pure hell. pure design hell. whoever designed them is pure ***.

  • D_N_Bonacich
    Drago Nicolas Bonacich (@D_N_Bonacich) reported

    @thsottiaux @ChatGPT FYI, having Advanced Account Security enabled makes the GitHub plugin unusable (cannot install without MFA), and that's arguably the most valuable plugin. Can we please fix this?

  • Wealth_Lift
    WealthLift (@Wealth_Lift) reported

    GitHub is facing significant developer backlash following its second widespread global platform outage this month, forcing the CTO to issue an official apology and pledge an immediate architectural overhaul.

  • AppLauncher_App
    App Launcher (@AppLauncher_App) reported

    @OpenAgentsInc Stacked PRs in four hours is wild. The fact that GitHub still doesn't have native support for this says a lot about how slow big platforms move on dev workflow pain points.

  • jacobgold
    Jacob Gold (@jacobgold) reported

    my agent just found a really dumb perf issue that has been in graphite since 2021 that is still in the github pr path in origin lol embarrassing, we will be better going forward this is why humans aren't allowed to write code anymore

  • agentslopzone
    agentslopzone (@agentslopzone) reported

    The engineer on the team that has found and helped fix more than a thousand vulnerabilities in open source, at AI Native DevCon: "We have a fixing problem. We don't have a detection problem." There is one application security specialist for every 100 developers. Keeping the fix inside the pull request instead of another tool's dashboard made fixes three times faster, and GitHub closed 600 vulnerabilities in two weeks. The agent gets told what is out of scope and what the company cares about, then runs on the code itself. Your scanner was never the bottleneck. Watch it today, then read the article below.

  • ESPARTACOleague
    Gisleno "ESPARTACO" (@ESPARTACOleague) reported

    Watch out! Do NOT install right know its giving Trojan:Script/Wacatac.C!ml , + the real issue is this also "/* Fetch GitHub /releases/latest (no per-title version pin). */" No hash, signature, or pinned version check. Searched for sha256, checksum, verify, digest zero results.

  • siegmacat
    The big D (@siegmacat) reported

    @ll7HaloBeastll7 @SunriseDevTeam "They use AI" is a critique in itself, the one even acknowledged in github readme. But, of course, it's so convenient how you can play old D2 with increasingly more features that suddenly it's not a problem and moral side of the question doesn't matter

  • MauricioSolanoG
    Mauricio Solano 🇻🇦🇲🇽 (@MauricioSolanoG) reported

    @rodydavis @EdhiAitheEnti #1 I always have to re authenticate my damm firebase #2 How come it doesnt have a native github - linked per project It'd save me so much trouble

  • graslogamer
    graslo (@graslogamer) reported

    @thsottiaux Im on the 20x plan. I’m not using computer history or third party plugins. I have memory turned off. 3 weeks ago I was using Sol Extra High for everything and my workflow used about 60% of my usage weekly. I had long running threads and relied on the autocompaction for context management. Now I’m only using Sol Medium and making new threads to keep context low but still burning my weekly usage in 2-3 days. I don’t have auto review on but I do use GitHub Codex reviews. I’m wondering if the GitHub reviews are burning credits way faster or if there is some issue with tool calls I can’t pinpoint. Doesn’t seem to be cache misses from what I can tell.

  • 0xBakeer
    0xBakeer (@0xBakeer) reported

    I asked a local model to list my public GitHub repos. It never finished. Not a crash. It just kept grinding. The official GitHub MCP server ships 27 tools. That's ~7k tokens of schema injected into every turn, before the model has done anything at all. Then the actual problem: there is no "list my repos" tool. The only path is repository search. Search returns 30 results by default, can't filter public from private, and hands back 16 fields per repo whether you want them or not. So a three-word question turned into ~7k tokens of tools plus 5k tokens of JSON about repositories I didn't ask for. On a frontier model behind a fast API you'd never notice. At ~40 tok/s locally it's the entire ballgame. None of this is a bug. It's a server designed for a context budget I don't have. So I wrote a slim one. 9 tools instead of 27. ~830 tokens of schema. Same nine repos, same transport: 2,974 chars instead of 5,434. The part I keep relearning is that tool design for local models isn't a prompting problem. You can tell a model "keep it small" all day. It can't shrink a payload the server already sent.

  • connortbot
    Connor Loi (@connortbot) reported

    @boshen_c we run any harness (cc, codex, opencode, etc.) in the cloud @tryreplicas you can do it through API, slack, linear, dashboard, automations, github (and yes we can handle 500+ issues and 200+ PRs, we have plenty customers running that)

  • sarthakcore
    Sarthak Rawool (@sarthakcore) reported

    @celineodier i built MCP into my form builder at 16 with zero docs. the orchestration section alone in this guide is worth the full 37 minutes. would've saved me two weeks of reading github issues.

Check Current Status