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 |
|---|---|
| Paris, Île-de-France | 1 |
| Saint-Paul, Réunion | 2 |
| Mexico City, CDMX | 1 |
| León de los Aldama, GUA | 1 |
| Créteil, Île-de-France | 1 |
| Trichūr, KL | 1 |
| Brasília, DF | 1 |
| Lyon, Auvergne-Rhône-Alpes | 1 |
| Tel Aviv, Tel Aviv | 1 |
| Rive-de-Gier, Auvergne-Rhône-Alpes | 1 |
| Itapema, SC | 1 |
| Cleveland, TN | 1 |
| Tlalpan, CDMX | 1 |
| Quilmes, BA | 1 |
| Bengaluru, KA | 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:
-
Isaac Sin (@IsaacSin12) reportedbeen looking for exactly this. notion mcp is painful for agents slow, and it burns tool calls to do anything simple. tried obsidian + github but syncing isn't real time, same with the obsidian vault.
-
H I K A R U (@Terry3nty) reportedNow imagine an AI agent. Today it needs GitHub. Tomorrow it needs Gmail. Then PostgreSQL. Then Docker. Then your local files. Then AWS. Then Notion. Then a browser. Unlike traditional software, an AI agent isn’t built for one workflow. It’s expected to perform many different tasks across many different systems. That’s where the problem starts. Every tool speaks differently. Every API has different rules. The AI doesn’t just need access to tools… It needs a consistent way to understand and use them.
-
Steve Wilkinson (@SteveW928) reported@bsvdrip @rodpalmerhodl Yes, not too long after I got into Bitcoin and started really learning about it (and after listening to Andreas Antonopoulos on weaknesses), I became a bit alarmed over how Core was structured. I tried asking in some discussions and even got blocked by a prominent Bitcoiners on here (𝕏). I figured maybe I just didn't understand enough about how Github worked (in governance terms), but looks like I had properly identified a problem.
-
Sponge Bob (@muriisajon) reportedLast year, GitHub saw 1 billion commits. This year, it's on pace for 14 billion. We're writing more code than ever, mostly because AI generates it faster than we can read it. ThoughtWorks is calling this "Codebase Cognitive Debt," and it's becoming a massive problem.
-
Mikhail Rogov (@i_mika_el) reported@abhimeeofficial real GitHub issues plus code quality checks should expose agents that only learn to game test suites.
-
rachaelsacks.eth (@RAnSacks) reported@GJarrosson 9/9/6 is an embarrassing psyop, saying you're working hard is not working hard. Period. Like let me see your contributions on github; go and flex that instead.
-
pulmencrFOMO (@pulmencr) reportedI found a workflow that turns a Discord annoyance into a full software business. Someone did this with zero prior coding experience. No CS degree, no bootcamp, just Claude open in a tab and a study group where people kept asking the same 5 questions in the wrong channels. Three hours later there was a working bot answering those questions automatically. Setups like this can eventually land $3,000+/month once enough of those servers upgrade to a paid tier. Here is the step-by-step playbook (detailed roadmap in the image below): 1. Pick one real annoyance, not a generic idea. "A bot that does everything" never gets built. "A bot that answers the five questions new members always ask" gets built in an afternoon. 2. Describe it to Claude clearly enough to get the actual bot code back. Tell it what platform, what trigger, what response - Claude writes the framework-ready code and explains each section in plain language. 3. Something breaks on the first run. That's normal. Paste the exact error back to Claude, it explains what happened and fixes it. 4. Give it a name and a short description so it feels like a real tool, not a script. The same loop works identically for a Slack app, a Telegram bot, a Chrome extension, or a small GitHub app. Discord is just the easiest place to start because publishing costs nothing and nobody gates who's allowed to try. Check out the full Discord Bot Business Playbook infographic below for profitable bot ideas, tech stack, and pricing tiers. Bookmark this.
-
moreward (moreboxed.com) (@morew4rd) reported@jtregunna No I left almost exactly a year ago even before the stupid "we're leaving github" post. The other issue was the aliasing issues with parameters. I did not expect to be hit by such a thing from a systems programming language. The biggest issue was how they "moved away" having the C/C++ toolkit built in. Because that was the selling point for me to even try it. I'm back to cmake since then lol
-
Ibrahim Alagbare (@Eb0z_) reportedWhy are we still using GitHub, it's trash, use your code and data to train their AI had so many problems with GitHub actions ( the thread sleep timer loop that I can't get over it) that costed people and companies millions in sever processing bills and yet we still use it. There are alternatives like codeberg which is a cloud hosted version of Forgejo that I personally use and love. It's minimal, easy to use and navigate and has all types of actions that you need to run. You can always go to Gitlabs but I find it overwhelming. Do you know any other code containers?
-
Dan (@thedansho) reported@TFTC21 @ODELLXYZ @MartyBent Just switched to radar from Molly last night. Unfortunately there's a bug at the moment and I can't use the payments feature, so I've temporarily shifted back to Molly, but will be keeping an eye on the issue in github to migrate again! Very cool stuff.
-
Alex Remniov (@alexremn) reportedOne word — “Additionally” — got past the guardrails in GitHub Agentic Workflows. Noma Labs used a public issue to make GitHub's AI agent post a private repo's README as a public comment. No fix, no advisory, no CVE. Per Noma, there is no pure-code fix to wait for.
-
Martin Adams | Building Flowtelic (@Martin_Adams) reportedNot going to lie, this setup is pretty 🔥 I can now do full development on my mobile while I’m doing other things. Here’s what I’ve setup: 1. Provision 2 servers with Herzner (4GB RAM each) and get Claude to set up a k3s cluster on it 3. Point dns to one server for ingress (saves on a load balancer) for each of my projects 4. Get a another Hetzner sever (8GB Ram) and get Claude to set up a GitHub build runner on it - now I get unlimited build minutes as I was burning through the 2000 minute limit quite quickly 5. Use Digital Ocean Container Registry to store images. 5. Set up a dev branch GitHub Actions pipeline to test, build and deploy to k3s 5. Use the Cursor mobile app to build new features and push to a PR. 6. Merge to the dev branch and have it pushed to a test namespace on k3s I have about 6 projects set up with this workflow and I can now iterate, test and fix bugs all from my phone. One side effect is all my apps are being mobile friendly as that’s what I need to test out the apps. Then I can use Claude on my Mac with /rc for the heavier work and get it to create an mp4 to verify it’s work, but control it from my phone. What a time to be alive. Rough monthly costs: k3s server = 2 x €5.49 = €10.98 Build server = €8.49 Container registry = $5 (up to 5 repo) / $20 (unlimited repos) + cursor/claude subscriptions
-
Dirble (@Dirbles_) reported@Hangsiin All subagents are inheriting main thread model + effort level so any sol x high threads will just spawn more sol x high subagents i found this fix on github
-
Muvon (@muvonteam) reportedOur first AI code reviewer flagged 14 critical issues on a one-line config change. 12 were imaginary. We rebuilt it: open source, self-hosted, runs your real lint and tests in GitHub Actions.
-
Skuffd (@skuffd) reported@thsottiaux I am doing a presentation this week to convince my team, and our product team that we should have a damn buisness account already. I'll be using the updated ChatGPT Desktop App. I actually think I have a shot at it this time, ill keep it in work mode. The rest of the dev team are locked in with github copilot and were slow to adapt - not necessarily slow to adopt. We all use Chat for looking stuff up or playing docter, I'll show em what's possible with ChatGPT Work. GOD DAMMIT I NEED THIS AT WORK- MY SIDE PROJECTS AT HOME ARE GOING TO OVERTAKE AT THIS RATE