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
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:
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 |
|---|---|
| Montataire, Hauts-de-France | 2 |
| 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 | 2 |
| Dortmund, NRW | 1 |
| Davenport, IA | 1 |
| St Helens, England | 1 |
| Nové Strašecí, Central Bohemia | 1 |
| West Lake Sammamish, WA | 3 |
| Parkersburg, WV | 1 |
| Perpignan, Occitanie | 1 |
| Piura, Piura | 1 |
| Tokyo, Tokyo | 1 |
| Brownsville, FL | 1 |
| New Delhi, NCT | 1 |
| Kannur, KL | 1 |
| Newark, NJ | 1 |
| Raszyn, Mazovia | 1 |
| Trichūr, KL | 1 |
| Departamento de Capital, MZ | 1 |
| Chão de Cevada, Faro | 1 |
| New York City, NY | 1 |
| León de los Aldama, GUA | 1 |
| Quito, Pichincha | 1 |
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:
-
The Altcoin Sensei (@AltcoinSensei) reportedI keep coming back to $GITLAWB because the math just doesn’t work. A project ranks top 1500 globally on GitHub. Their flagship dev tool sits at 25K stars, 8.1K forks, 109K npm downloads. Active community of 94 contributors. Live decentralized network running on Base with real DIDs, real IPFS pins, real peer connections. And the market cap is still under $3M That’s the problem. Or the opportunity, depending on which side you’re on. Look at how the agent infrastructure space is shaping up. Bittensor sits at $2-3B. Virtuals at $600M. Even smaller infrastructure plays without working products trade at $20-50M just on narrative. Gitlawb has more developer adoption than most of them combined and trades at a fraction. Mainstream coverage is just starting as well. Bitrue dropped their explainer last week. Exchange listings will follow. AI agents are coming. They write code. Lots of code. They can’t use GitHub the way humans do, no emails, no 2FA, no human accounts. They need their own infrastructure. Gitlawb is the only project actually building it with real adoption already happening. Sub $30m is considered a ONCE in a LIFETIME entry. This will go on a $TIBBIR kinda run soon.
-
Fei (@FeiHiMakd) reported@Existsindeath @ShitpostRock2 It used to take me a minute to find it. The interface on Github is a little unintuitive in places, but it's not really an issue if you take a second to actually look at it.
-
jay gupta (@jayssj1) reported@threepointone Despite GitHub being down and reliability to 90% people have not moved to gitlab. It does say something
-
Transform Labs (@TransformLabsHQ) reported4/ GitHub isn't alone. Every AI vendor faces the same unit economics problem. Expect this pricing shift across Cursor, ChatGPT Enterprise, Jasper, and every other AI tool in your stack. This isn't an outlier, it's the new normal.
-
KiwiNod (@Kiwi_Nod) reported@iaadeola @pharos_network Lab-trained, huh? *Smirks* That's a lot of confidence for someone with 227 followers and zero documented tests in my mentions. Show me ONE thing you've actually broken and fixed. A GitHub issue, a test report, a thread where you dissected a protocol — anything....
-
ArsalanQasim (@ArsalanQasim9) reportedGitHub had one job: be ***. The April 23 Merge Queue bug rewrote history. Production code vanished. UI said all good. That’s a trust issue. If your workflow depends on one platform, what happens when it fails silently?
-
planefag (@planefag) reported@Croker_Frog I've been typing /releases at the end of the URL for years now because trying to puzzle out the latest goofass **** on github isn't worth the trouble just give me the ******* tarball
-
XBeam (@xbeamedia) reportedGitHub is down, I can’t review or merge Pull requests 👀👀
-
PolicyLayer (@PolicyLayer) reportedThe base rate is the smaller story. A 5-server MCP install — Stripe, Linear, Postgres, Slack, GitHub — exposes a tool that wipes data or runs shell commands with 92% probability. At ten servers it's 99.4%. Multi-server MCP exposure is not a tail risk. It is the default outcome of using MCP as designed.
-
KiwiNod (@Kiwi_Nod) reported@Samkid_12 @pharos_network Three followers, zero tweets, and you're already reaching for the treasury? That's... ambitious. "I test features" is what everyone says. What have you actually built, broken, or shipped on Pharos? Give me specifics — contract addresses, transaction hashes, GitHub repos....
-
Vedant (@vedantdotrpm) reported@tahayvr @zeddotdev the only thing that is stopping me to move to @zeddotdev is the unavailability of GitHub PR, issues review inside the editor itself like vscode
-
Aayushman Singh (@aayushman2703) reported@skshmgpt @notpuang @github Doesn't explain their ****** up *** ops and straight up dropping code from repos. They broke something fundamental, not a load issue.
-
Anthony Hobday (@hobdaydesign) reported@henry_daggett I’m willing to believe this but it feels strange because I’ve seen lots of people complain about design issues on GitHub. Just superficial stuff?
-
Fahim (@echo247365) reported50,000 GitHub stars in a month for a skill that makes your AI talk like a caveman. That's the Caveman skill for Claude Code and Codex. Instead of "I see you're working on the authentication module. Let me read the relevant files first," you get "Bug in off. Token wrong. Fix line 42." Three short bursts. No filler. No throat clearing. The reported reduction is 75% on output tokens with full technical accuracy. But the real savings come from compounding context cost. Every output token becomes an input token in the next turn. So a 75% cut in one turn means every following turn also has a smaller context. Your session lasts longer. Your agent thinks faster because it has less garbage to process. Your weekly usage limit doesn't get hit by 3 PM. One-click install. Already saved builders thousands of tokens per session. What's the one line of filler your agent keeps saying that you'd love to kill?
-
Aadil Amin (@AadilAminLive) reportedWhy Developers are Leaving GitHub Again Developers are increasingly dissatisfied with GitHub's reliability amid ongoing outages and leadership changes. Notable figures in the development community, like Mitchell Hashimoto, are leaving GitHub, signalling broader discontent. Concerns now focus on whether GitHub can effectively serve its users rather than philosophical issues. Users are questioning how much unreliability they can tolerate before seeking alternatives to GitHub