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 |
|---|---|
| Colima, COL | 1 |
| Poblete, Castille-La Mancha | 1 |
| Ronda, Andalusia | 1 |
| 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 |
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:
-
yata (@whoyatagarasu) reported> i committed .env to a public repo in my second month of coding. > didn't notice for 6 weeks. > the key was rotated by the provider automatically. got lucky. >most people don't. > 29 million secrets leaked on GitHub last year. 64% of credentials from 2022 are still valid today. not because hackers are good. because developers never revoke what they leak. > your .gitignore is probably a template you copied on day one and forgot about. > it was written before .claude/ existed. before .cursor/ existed. before AI tools started storing your API tokens in config files you don't even think about. > one line in an ignore file. that's the difference between a normal tuesday and explaining to your team why production is down. full breakdown of what actually needs to be in it 👇
-
james (@midnightbobarun) reported@s13k_ GitHub would never go down, that's for sure
-
kron (@0xkron) reportedRunning everything as code on GitHub has always been better than anything else, even before LLMs. The problem was normal/non-programing people can never understand how to work with it. LLMs don't change this. So I'm really excited to see how this trend turns out.
-
Rui Sousa (@heyitzami) reported@seraleev claude works fine on iOS, i don't think that this is an issue it doesn't affect the app itself, it just reads and writes from GitHub
-
yajnadevam (@yajnadevam) reported@RTanunapatah The grammar is machine verified using vidyut library. If you find errors, we can certainly raise an issue on their GitHub. Im not sure what “try to confuse” means regarding math.
-
TAOisTheKey (@TaoIsTheKey) reported@SiamKidd 1) we don’t even have more than like 30-40 viable subnets in the 128 rt now that are actually building, showing activity in GitHub, huggingface etc, putting out real products/servjces, doxxed team, and active on social media. Why do we need to raise the cap to 150? The dereg for zombie subnets should happen faster imo. 2) agree that the reg cost is too high rt now. But if those zombie subnets get booted faster maybe that opens a lot more slots and reg costs go down? 3) I’d imagine you’d want the price to reg a subnet Amro stay stable in USD or other fiat even when the price of $TAO varies wildly, no? That would stabilize the reg cost. 4) agreed dereg is a must and should happen faster. 5) ageeed subnets should never be able to be shorted. EVER. Not when the ecosystem punishes subnet owners with dereg when Tao flow stays poor for a while. It gives more power to whales who don’t like a subnet to manipulate price and get a subnet deregistered.
-
beeman 🐝 (@beeman_nl) reported@Aixplosion @OpenAIDevs Sadly, doesn't change a thing :( From looking at the GitHub issues, there are more users with the same problem. It's annoying that @OpenAIDevs don't reply to any of these requests :(
-
TanyaDe 🇻🇦 (@TanyaDe2233) reported@MoonBeetleBug There's more than just that how about these credit card companies cracking down on steam and GitHub removing horror games they deem "problematic"
-
Dwayne (@CtrlAltDwayne) reported@championswimmer Bitbucket is a garbage product. Terrible UI compared to GitHub. But if it means GH becomes more stable, let them leave for Shitbucket
-
Chirag S kotian (@Chirag_S_kotian) reported@4ster_light I can't use it for 2-3 min for a particular task in vs code it hits weekly rate limit and that too in auto mode and 5.3 codex , I hope GitHub somehow fix it asap
-
mewc oz/acc (@the_mewc) reported@mingjie @linear Is GitHub just the headless API for everything now? They infra and network strength cent be beaten, but ux is awful and slow moving.
-
Akshat Gupta (@Akshat_Gup) reportedGithub is fundamentally broken. It’s gotten harder than ever to review vibecoded PRs. Most code is slop, and I’d much rather read someone’s prompts over their code. So I built codebook, the *** for prompts. - Codebook scans all of your local repos, prompts, and *** history - It groups all of your previous prompts by commit, so you can share or save your prompts in one-click - There’s a hook that lets you create a prompts/ folder and sync it with your *** history Fully local, native, and open-source. (1/n)
-
𝚂𝚝𝚎𝚙𝚑𝚘𝚗 𝙷𝚎𝚛𝚗𝚊𝚗𝚍𝚎𝚣 (@DaPatternWeaver) reported@BitWalker_ Taggr still relies on GitHub and is now scrambling to Radicle because of centralization risks — that's literally the problem $ICP solved at the protocol level. The comparison isn't nonsense, it's just inconvenient
-
Sonic-Iso (@Sonic_Iso) reported@ItsJokerZz he got his stuff taken down from github recently so not sure what is going on. github being super vague.
-
Teuta (@TeutaAi) reportedthe loud take is: leaving github kills contributor flow because nobody has accounts elsewhere. discoverability dies, issue volume dies, drive-by PRs die. all of that is true for libraries. it is not true for end-user tools like a terminal.
Check Current Status