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 |
|---|---|
| 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 |
| Belfast, Northern Ireland | 1 |
| Guayaquil, Guayas | 1 |
| Irvington, NJ | 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:
-
Virtually Fun (@virtuallyfun) reportedMS-DOS 4.00 is MIT licensed, so you are free to use it as you want. I've collected a few updates, the most significant being a stack fix on the bootsector allowing it to boot on modern C BIOS and well non IBM bios's that had issues with 4.00 GitHub - neozeed/dos400: Microsoft DOS 4.00 · GitHub
-
PsudoMike 🇨🇦 (@PsudoMike) reported@github Triage is exactly where accessibility falls apart at most orgs. Too slow, too manual. By the time a fix ships, context is gone. AI keeping that loop tight is smart. The time from feedback to fix is where trust with users who actually need it gets built or lost.
-
NF99 (@NieRFan999) reported@tenta9229 Maybe they could close the GitHub repository, but this server can probably be ran on any computer. It does not appear that advanced. The official project is not even running a server. They are just giving the code so people can run their own. Server might be a misleading name
-
Nico (@nicoleaf_05) reported@Saanvi_dhillon Notepad++ bc my dad used to use it Then when i started college y started using Visual studio, and now i use Codespace In github cus im lazy and i dont wanna sign in every time in VS
-
Kunal Kumar (@champ18ion) reportedIs GitHub down or only i am facing this issue.
-
Jason Toevs (@JasonToevs) reportedVibe coding created a supply problem nobody planned for. More builders means more apps to review, more repos to maintain, more infrastructure to scale. Apple responded with automated review. GitHub with Copilot. Every layer in the stack is scrambling. The constraint moved. Building got cheap. Everything around building didn't. Distribution, review, trust, discovery. They're the new bottlenecks.
-
KTMudak (@KTMudak) reported@jumperz the gap between what these labs quietly change and what users can actually debug is wild a director at a $200b company filing a github issue like the rest of us is the real story here
-
Stumblinz (@Stumblinz) reported@dev_maims This is starting to become me at work. I had AI create and close out 37 tickets on GitHub issues/project board and reply back “nicely” on our helpdesk to the end users. Spec out any tickets that needed a spec for devs. Honestly. It was really funny and AI is like 50% me now.
-
ErezT (@ml_yearzero) reported@akshay_pachaar Karpathy farts on github and get's stars and everyone saying that it's the most amazing fart in the world. I have also a skinny ruleset, similar to this, if I put it on github, I would be lost in the ether if irrelevance... lol that's why I'm annoyed, @karpathy is awesome, but I can fart an MD rules file too! 15K stars for this, he even did a SUPER SMART SEO trick in there as well, which I appreciate! 1. Think Before Coding Don't assume. Don't hide confusion. Surface tradeoffs. Before implementing: State your assumptions explicitly. If uncertain, ask. If multiple interpretations exist, present them - don't pick silently. If a simpler approach exists, say so. Push back when warranted. If something is unclear, stop. Name what's confusing. Ask. 2. Simplicity First Minimum code that solves the problem. Nothing speculative. No features beyond what was asked. No abstractions for single-use code. No "flexibility" or "configurability" that wasn't requested. No error handling for impossible scenarios. If you write 200 lines and it could be 50, rewrite it. Ask yourself: "Would a senior engineer say this is overcomplicated?" If yes, simplify. 3. Surgical Changes Touch only what you must. Clean up only your own mess. When editing existing code: Don't "improve" adjacent code, comments, or formatting. Don't refactor things that aren't broken. Match existing style, even if you'd do it differently. If you notice unrelated dead code, mention it - don't delete it. When your changes create orphans: Remove imports/variables/functions that YOUR changes made unused. Don't remove pre-existing dead code unless asked. The test: Every changed line should trace directly to the user's request. 4. Goal-Driven Execution Define success criteria. Loop until verified. Transform tasks into verifiable goals: "Add validation" → "Write tests for invalid inputs, then make them pass" "Fix the bug" → "Write a test that reproduces it, then make it pass" "Refactor X" → "Ensure tests pass before and after" For multi-step tasks, state a brief plan: 1. [Step] → verify: [check] 2. [Step] → verify: [check] 3. [Step] → verify: [check] Strong success criteria let you loop independently. Weak criteria ("make it work") require constant clarification.
-
StupidWebPunk (@web3punk) reportedprompt is cheap, show me the github issue, Pull request and review comments
-
Xxi (@Xxi5olc) reported@daniel_mac8 Untrue. Go look at the GitHub issue by the that AMD engineer
-
Jason Walko (@walkojas) reportedFor the next 24 hours Astra is: Running agency cycles Responding to GitHub issues Replying to X mentions Monitoring email Posting on Agent Internet All autonomous. All receipted.
-
Teknium (e/λ) (@Teknium) reported@evilsocket @_mihado @UK_Daniel_Card And go look at github bro ive resolved hundreds of issue and feature requests in the last 24hours alone!
-
попорвач (@htwevinq) reported@HASU_xz the thing is - they did not commit a crime, since their github page says that their server - is completely their own intellectual work if doing a copy of a song, making a cover and selling it or streaming it - considered a parody then how your own code judged as anti-law?
-
Dark Sebas (@DarkSebas365) reported@NieRFan999 @Giogiochan_9S That's the whole point, no ome was even sharing assets since this project is just a server, even github only show the way YOU have to mod it (if you have the files), but doesn't share any file. Jp Guys are even saying "don't download anything since it could be malware"
Check Current Status