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 |
|---|---|
| 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 |
| West Lake Sammamish, WA | 2 |
| Parkersburg, WV | 1 |
| Perpignan, Occitanie | 1 |
| Piura, Piura | 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:
-
Hrutik Kumthekar (@bushido_hk) reported@KaiXCreator Build something small that solves a problem you actually have. Employers care more about what you've shipped than what you've studied. Your GitHub matters more than your GPA.
-
Working-Ref (@kkotkkio) reportedThe real unlock is Routines — Claude auto-triggered by cron, GitHub webhooks, or API. PRs get reviewed. Security scans run overnight. Fix PRs ship automatically. I'd start by defining a rubric before you 'let it cook'.
-
Thiago Salvador (@bettercallsalva) reported@TopStockAlerts1 github ownership without product velocity is the cautionary tale here. copilot was first but the iteration speed of cursor and claude code on workflow ux ran them over. distribution doesn't save a product that ships slow.
-
Sean Davis (@SeanChDavis) reported@ajaydsouza Also, it isn't a real roadmap, like what you would have as GitHub issues. It's more of a to-do list of things it knows I want to do, but just hadn't done yet. That's probably the key to the behavior right there.
-
✰λster✰ (@4ster_light) reported@tymofii Wdym, this is all I have to show for it, in GitHub web the tag and release are non-existent but if I try to create it manually from there it also errors saying the tag was used on an immutable release
-
oscar gabriel (@oscabriel) reported@mitsuhiko @badlogicgames I think you're right that github is less to blame for some of the new problems with open source, and that it instead lies more in all the ppl who irresponsibly point their agents at repos w/o regard to the humans on the other side of their (often passive) requests. But I also don't think github has the tools needed to keep those agents under control. If something is to come after gh, it should be something that does that filtering on behalf of maintainers
-
Owen (@owenyuwono) reported@ChShersh with github going down and getting hacked every week you might be onto something
-
Jordan Barrand (@0X_Barrand) reportedMegalodon wasn’t random. Infostealer malware is the root cause. Hacked dev accounts pushed malware to 5,000+ GitHub repos in 6 hours. Hudson Rock checked the usernames: 33% were already in infostealer logs. Manual checks push it near 100%. Bigger problem: 24,000+ companies have employees with leaked GitHub creds. Accenture, Dell’s partners, ABB, Anheuser-Busch InBev all on the list. Infostealer logs = the fuel for the next mass supply chain attack.
-
Prakash Acharya (@pracharya2601) reported@scalekitinc handles the agentic authentication so the agent can securely push live update analytics directly to the team in Slack and GitHub issues. Roadmap - connect to the coding agent and automatically create the pr to mitigate any potential vulnerabilities.
-
Damian Barabonkov (@damian_b) reportedLow stakes projects are OK to be vibed. Slop is a new tool and it shouldn't be universally rejected. Just like how we have Python vs C to solve different problems, there is now Curated vs Slop. This new paradigm needs a new way to be reviewed. GitHub PRs are for Curated code. For slop projects, it is often untenable to review the code since it often comes in large sizes with poor organization. Instead of looking at the code, the reviewer would get much more signal by looking at the prompts, which model was used and resulting LLM diffs. This way, it is much easier to determine if the features implemented are reasonable and inline with the project's direction. We still don't have such a tool, but it's hopefully on the radar of those building the post-AI GitHub.
-
Docsbook.io (@docsbook) reported@yuuki1645 yuuki-lab is one of those rare projects where the idea and execution both land. Problem is the docs are buried in GitHub — people bounce before they even understand what it does. Built a hosted docs site so the first impression actually sticks. Go take a look.
-
x (@xaoticatech) reported@github You just got the best engineering volunteer upgrade of your life because I was the only engineer who had the cojones to stand for Microsoft against the narcissist Xbox UX director! 30% of Microsoft's revenue. Buckle up @satyanadella because you and Sam Altman got a problem. 👇
-
Kaidu (@xkaidus) reported@BHolmesDev @mattpocockuk the /handoff idea is smart but i feel like github issues would turn into a black hole for me do u tag them as someday or actually come back?
-
0xZyo (@Zierax_x) reported@nowisar1878 Hi, can you open an issue in GitHub with detailed information please so I can fix it soon
-
Bnaf.OG | 🟧 (@bnafOg) reportedGitHub trending hook: OpenPipe ART is pushing agent RL into the practical stack. Useful eval: reward quality, task diversity, regression tests, rollback, and cost per accepted fix. GRPO demos are cheap; durable agents need receipts.
Check Current Status