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 | 3 |
| Parkersburg, WV | 1 |
| Perpignan, Occitanie | 1 |
| Piura, Piura | 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:
-
Not aToaster (@techfocusjames) reported@arvidkahl I half expected GitHub to list that outage as a CVE fix. 😬 Sub-90% uptime isn't a security feature, it's just reactive firefighting. #CICD
-
Dr.OVG (@OVGNFT) reported@mecxist @github @nexudotio omg :( they really need to fix their automated flagging system
-
Jon Williams (@jonathannen) reportedHas Claude auto-responding to GitHub comments broken? It worked before, but now it appear you need to push every comment. This was a major differentiator w/ Codex!
-
Kang Cahya (Tech Dev) (@dyazincahya) reportedHere's the gist: GitHub is changing the format of their App Installation Tokens to be stateless (carrying their own data without pinging the main server constantly). The side effect? The token size is inflating massively. What used to be short will now hit ~520 characters! 🤯
-
Valter (@luhtala1) reported@github I get everyday on my authapp a login request attemps, i revoke those. Today i got an email. This is not good
-
Jan Drlý (@jdrly_dev) reported@thsottiaux can we please address the bug where Codex is reverting to slowpoke mode every time i close and open the app? There are countless github issues on this and its pretty annoying at this point :( thx
-
CG Nguyen (@luongs3) reportedMCP server that lets Claude Code / understand any GitHub repo without cloning it. Paste one URL into your client config. Ask: "who maintains this repo? where's the churn? is main green?" Hosted. Pay-per-call. First 100 free. 👇
-
Maksim (@MaksimXBT) reported@hi_vecna github links often get taken down
-
Kamran Ul Haq (@KamranZone) reportedJust need to vent for a second and see if anyone else is running into this. I’ve been using Codex inside GitHub Copilot for a while now, and honestly, it’s great. It does what I ask, stays out of the way, and helps me speed up my workflow. But recently, I decided to try out the standalone GPT Codex extension, thinking it might give me a bit more control or a different interface to work with. Wow. What an absolute train wreck. It feels like they wrapped this thing in so many aggressive, hyper-sensitive guardrails that it’s practically useless for actual development. I’ll be in the middle of a project, trying to debug something or refactor an old script, and the extension just throws me under the bus. Instead of code, half my queries get hit with preachy, patronizing refusals: "I can't do this because of security/policy reasons..." "I wouldn't recommend doing that, try this completely unrelated..." It’s incredibly rigid, and you can’t even nudge or prompt-engineer your way past it. It literally kills my momentum mid-flow. How did the same underlying tech end up so drastically different? Copilot actually lets me work, while the GPT extension feels like coding with a HR manager breathing down my neck.
-
Blake (@BlakeFolgado) reported@Chris_C_Clerk @clerk found another thing where something preventing switching to phone number/email in authview without a workaround, may have already submitted github issue
-
Yash Chaudhary (@xyashchaudhary) reported@mitchellh GitHub PR diff speed still painful in 2026. The basics shouldn't feel this slow.
-
CyberDevHq (0xSEC) (@thecyberdevhq) reportedEspecially now with GItHub issues, might be time to switch
-
Sudipta Dey (@Doom_S_Dey) reported@mitchellh I agree, though I sympathize with the devs trying not to crash the tab. Both GitHub and GitLab have the "expand" problem, click, wait, click, wait, and it still truncates large diffs. For anything serious, pulling locally is the only reliable option.
-
Tarun Kumar (@TarunDevYT) reportedIn 2024, you had GitHub Copilot and a handful of experiments. In May 2026, you have 7 serious AI coding tools all shipping simultaneously. Claude Code. Cursor. Codex. Windsurf. Copilot. Kiro. Google Antigravity. Every single one is racing toward the same thing — agents that write, run, test, and fix code without you touching the keyboard. The engineers debating which one is best are missing the point entirely. The question is not which tool wins. The question is what happens to the engineer who masters none of them. Which one are you actually using in production right now?
-
Musharraf Jamal (@musharrafJamal8) reportedKarpathy ran GPT 5.1 Thinking across 930 Hacker News articles from 2015 and graded every comment for prescience with hindsight. Total cost: $58. Runtime: ~1 hour. The pattern matters more than the artifact. Any text archive you have (Slack history, GitHub issue threads, old design docs) is now a graded dataset waiting to happen. Cheap intelligence turns retroactive evaluation into a normal workflow, not a research project.