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 |
|---|---|
| Colima, COL | 1 |
| Poblete, Castille-La Mancha | 1 |
| Ronda, Andalusia | 1 |
| Montataire, Hauts-de-France | 2 |
| 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 | 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 |
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:
-
Emile 🏴🇬🇧 (@HSTemile) reported@planefag Github is s code repository, not a download server. If you want to download the .exe, host it on some other website or make it into a torrent.
-
yata (@whoyatagarasu) reported> i committed .env to a public repo in my second month of coding. > didn't notice for 6 weeks. > the key was rotated by the provider automatically. got lucky. >most people don't. > 29 million secrets leaked on GitHub last year. 64% of credentials from 2022 are still valid today. not because hackers are good. because developers never revoke what they leak. > your .gitignore is probably a template you copied on day one and forgot about. > it was written before .claude/ existed. before .cursor/ existed. before AI tools started storing your API tokens in config files you don't even think about. > one line in an ignore file. that's the difference between a normal tuesday and explaining to your team why production is down. full breakdown of what actually needs to be in it 👇
-
Priyal Raj (@Capta1nCodes) reportedHey devs, I need a small help. I have a CI/CD for Github Actions, the issue is I am getting an error and it's hard to re-deploy on GH Actions everything, can I run those CI/CD directly from my PC? Locally I mean? About to GPt, but want your inputs too.
-
BrianEMcGrath (@BrianEMcGrath) reportedGPT-5.5 just landed in GitHub Copilot, M365 Copilot, Copilot Studio, and Foundry. No new vendor review. No security exception. No procurement cycle. Dropped straight into the stack my IT team already approved. I built a workflow in 10 minutes this week that immediately solved a problem for my treasury team. 10 minutes!
-
FHILY👑 (@Oluwaphilemon1) reportedBREAKING NEWS: This 13-year-old Thai student solves Codeforces rating 800 problems in C++ in 45 seconds through an AI agent he built himself on Claude Code and posted to an open GitHub repo. He sits in a regular school room with a MacBook Air on the desk, a silent HHKB Type-S keyboard for $300, and a timer in the frame. In the browser Codeforces is open, in VS Code an empty .cpp file, and in the corner of the screen a Claude Code window.
-
Heavy Polo (@RLPCFelix) reported@github @GitHubCopilot I pay for Copilot Pro and the mobile coding agent is failing before it edits anything. Simple task: create 3 basic JS smoke-test files. Actual failure: *** rev-parse --abbrev-ref HEADHEAD exit 128 Then: *** checkout copilot/add-js-smoke-test exit 1 This looks like an agent setup bug, not a repo/code issue. Can someone help route this?
-
yajnadevam (@yajnadevam) reported@RTanunapatah The grammar is machine verified using vidyut library. If you find errors, we can certainly raise an issue on their GitHub. Im not sure what “try to confuse” means regarding math.
-
jan (@ironcarbs) reported@tonilopezmr you may have an app (Rize) that is using github regularly to store data. I recall this was an issue a few months ago. I’m unsure if it has been resolved.
-
james (@midnightbobarun) reported@s13k_ GitHub would never go down, that's for sure
-
yata (@whoyatagarasu) reportedi committed .env to a public repo in my second month of coding. didn't notice for 6 weeks. the key was rotated by the provider automatically. got lucky. most people don't. 29 million secrets leaked on GitHub last year. 64% of credentials from 2022 are still valid today. not because hackers are good. because developers never revoke what they leak. your .gitignore is probably a template you copied on day one and forgot about. it was written before .claude/ existed. before .cursor/ existed. before AI tools started storing your API tokens in config files you don't even think about. one line in an ignore file. that's the difference between a normal tuesday and explaining to your team why production is down. full breakdown of what actually needs to be in it 👇
-
Arjun Iyer (@arjuniyer_) reported@github 4/6 The structural problem: Coding agents write code autonomously. They can't validate it against real systems with real dependency graphs. Every change inherits a validation burden, and that burden lands on devs and CI that were already strained before agents arrived.
-
Shrit (@Shrit1401) reportedit's so funny github is struggling to be live because pre AI commits were not that much, however everybody is using agentic AI / vibe coding wtvr u name it, we're spamming commits, and github is reaching it's limit for resources it will be interesting to see how they try to solve this problem.
-
Nexus Void Ai - Your Autonomous CISO (@NexusVoid_Ai) reported@authzed The GitHub incident is the one worth sitting with. Not a zero day. Just a single over-permissioned PAT wired into an MCP server, and one poisoned issue was enough to pull private repo contents into a public PR. The agent did exactly what it was configured to do. That's the uncomfortable part. Clean code, no exploit, fully exposed. The trust boundary between untrusted content and tool scope has to be explicitly designed or it doesn't exist.
-
Conor (@Common_Conor) reportedGithub issues caused by clankers adding broken CICD files to every repo and no one wanting to break flow to go deal with them
-
Scott Martinis (@scottmartinis) reported@morganlinton pretty much every gtm process can be reduced to code plans > github projects milestones issues software setup > yamls resembling terraform setup playbooks > skill files workflows > deployed skill orchestration regular reporting > trace logs how agent artifacts are prompted by humans, deployed, and produce pipeline outcomes verified by predefined operating model sql slices that point to a data lake