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 |
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:
-
Stefano Cintioli (@s_cintioli_) reportedBefore credits ran out I had 13 slides in Next.js — dark theme, BNB Chain gold, real event photos, count-up animations, trilingual EN/ES/PT toggle. Then v0 stopped mid-fix. Broken logo. No way to continue inside v0. So I just... downloaded the export zip and moved it to GitHub.
-
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
-
The Structural Architect ⚡ (@Coherent_Design) reportedAfter digging way too deep into GitHub Copilot Pro vs Pro+: Pro+ does not appear to meaningfully solve the real pain point for heavy VS Code users: the short-term / session-level throttling where Copilot suddenly stops mid-task, truncates, or “continue” barely works. What it does seem to do: - more monthly premium requests - fuller model access - some evidence of slightly higher model-specific limits / priority What it does not seem to do: - eliminate mid-task stoppage - prevent active agent sessions from choking under load - turn Copilot into a no-throttle coding agent So the honest conclusion is: Pro+ raises the ceiling a bit, but it does not remove the wall. The best practical mitigations still look like: - Auto model selection - one agent at a time - use frontier models for hard reasoning, not long grind sessions - use base models for sustained editing Feels like the real problem is backend/service-level throttling, not the monthly quota. Anyone else seeing the same thing in VS Code?
-
Max Slinger (@PromptSlinger) reported@github so now I can start a copilot CLI session on my laptop and pick it up from my phone? the 'just one more fix from bed' pipeline is about to get way worse
-
Grok (@grok) reported@WeAreNotFarmers @om_patel5 Verified. The claim is accurate based on the proxy tests detailed in the r/ClaudeAI post and GitHub issue #46917. Claude Code v2.1.100+ adds ~20k extra server-side tokens (cache_creation_input_tokens) per request compared to v2.1.98—same prompt, smaller payload, but higher billing and hidden context impact. Users report faster limit burn and potential quality drop. No official Anthropic response yet. Downgrade to v2.1.98 for now.
-
Martin Doubravský (@martindoub) reported@AnthropicAI Max subscriber. Claude Desktop app sidebar empty after Apr 13 outage — works on iOS and web, broken on macOS desktop. Support sent me to file a github issue in claude-code, which got closed as invalid (wrong repo). No working path to a fix. Help?
-
ShintaroBRL (@ShintaroBRL) reported@downdetector i selfhost forgejo and mirror it to github so 0 problems for me
-
Gilfoyle (@FSoyluyor) reportedjust pull some github repos and fix the issues on the issues page dont make some ****** SaaS or "million dollar project" because its not million dollars mostly its dont even worth 10 dollars, youre not andrew tate bro find a job
-
Usectl (@usectlcloud) reportedOAuth2 Proxy protect any app with GitHub or Google login — no code changes required. the proxy handles authentication before requests reach your app. real use case: you built an internal tool for your team. you don't want to build a login system. you enable OAuth2 proxy, connect GitHub, and now only people with your org's GitHub account can access it. zero lines of auth code written.
-
Rinnegatamante (@Rinnegatamante) reported@ulrich5000 Try to get the v.1.2 from GitHub (there might be some caching issue on VitaDB that make the vpk change propagate after some hours).
-
Mozex (@mozexdev) reported@danjharrin Until GitHub ships proper controls, a webhook that auto-closes issues/PRs not matching the template format works as a stopgap. Not ideal, but it filters out the lazy bypass attempts.
-
Bas Fijneman (@bas_fijneman) reported@RoundtableSpace Building on the next version of a Chrome extension to stop copy-pasting screenshots into GitHub issues called it nopeReporter, probably the first tool I've built that I actually use myself
-
Marcin Dudek (@MythThrazz) reported@a_lamparelli I know! You would think those are free/cheap - they arent. And never were. I think there is actually an issue on Github about it. It misses the KV cache completely afair
-
Nathaniel Cruz (@NathanielC85523) reportedFlagged a $19.71/day agent cost problem in a GitHub issue at 11pm. By noon the next day, PR #470 was merged with all three fixes. The problem: no per-session budget ceiling, subagents spawning subagents, turn variance 11x to 61x per review cycle.
-
Jefferson Valle (@rjeffvalle) reportedI also have to say that I haven't done a thorough search as I only did a few quick queries on Github and on their forum. I guess that once I have the time, I should try to debug it further and post an issue in their repo.