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 |
|---|---|
| Veigné, Centre | 1 |
| 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 |
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:
-
MCG (@MCGlive) reported.@jamiepine breaks down one of the most overlooked problems with building open source... "Commercial open source has been the bane of my existence for years. I might be great at building technology, but do I have the skills to turn it into a business? It's swimming upstream...most people can use it for free." He's speaking first hand: - Built Spacedrive (a cross-platform file manager) - 39K GitHub stars - Burned $2M on engineering with a 10-12 person team and never reached completeness "By the time you've spent your first seed round, good luck raising another to continue R&D." Then he built @VoiceboxAI in 3 days, posted it, left it. He came back to 5,000 stars and said "here we go again."
-
†saint‡ (@Shallom_Okpapi) reportedMy setup: Bot 1: Live odds monitoring Bot 2: Arbitrage scanner Bot 3: Alert engine All sharing the same key → constant 429 errors and failed runs. GitHub Actions kept retrying. Credits evaporated. I nearly missed key opportunities mid-tournament.
-
Stefanescu Liviu (@liviusa) reported@thsottiaux Done. Don't even know when I'll consume them as there are so many resets and banked resets... I'll push harder, lol, github will be down again from such actions @thsottiaux
-
Jawad Al Hashmi (@kindnessuae) reported@justbyte_ GitLab solved the integration problem first. GitHub is still catching up.
-
Justin Liverman (@the_cia_hacker) reportedsaying Almighty Push over voice to my server to update github is extremely satisfying
-
prolatamwork (@prolatan12208) reported"Senior developer" is the most abused title in remote hiring. The reality: it's entirely self-declared. Anyone can update their profile in 90 seconds. How to verify actual senior-level skill in 15 minutes: → Find their GitHub (don't use the profile link — search directly). Real commits > polished repo. → Click the deployed projects. Live products you can use > screenshots. → Ask ONE specific technical question. How they answer — and what they ask back — reveals more than their full portfolio. → Read reviews for specifics. "Great!" means nothing. "Caught a security issue we missed" means something. "Senior" is a label. Verification is the only protection.
-
Branko (@brankopetric00) reportedYou push a commit to a public repo. Five minutes later you realize your AWS keys are in it. A teammate says: delete the file and force-push. Problem gone. It is not gone. Bots scrape GitHub for keys in under a minute, so assume they are already stolen. And a force-push does not scrub the commit from GitHub's caches or from anyone who already pulled. Order matters here more than in almost any incident: kill the credentials first, then check what they touched, then clean the history. Cleaning the history first is tidying the crime scene while the burglar still has your keys. Would your response survive a senior engineer's cross-examination?
-
Poorvith M P (@poorvithmp07) reportedOpened a PR to fix a stale package version in cake-build/cake. Their own bot had already tried, but got silently killed by intermittent GitHub API timeouts for 3 days. Mine got closed once theirs finally landed. "Automated" still needs someone watching the logs.
-
MadeItHappen (@MadeItHappenX) reportedWith GitHub App, ChatGPT app, and my project auto deployed, developing (vibe coding) from my phone is not that bad, especially when I’m testing on mobile anyway. I can screenshot and verbally prompt, approve the dev PR, review, PR to default branch, validate. Let my agents do the work and I’ll critique and bug fix on the go! ..or from my bed at 2am still thinking about my project. #vibecoding
-
💻🩵 (@Gransolita) reportedGPT-5.6 + Codex feels like having a technical cofounder available 24/7. Over the past few weeks I’ve been designing multiple SaaS products, setting up GitHub projects, creating issues, planning MVPs, and turning ideas into actual software with Codex. #GPT56 #Codex
-
Howaboua (@Howaboua) reportedI asked Sol if the harness I am making and its aborted turns cache resumption mechanism is unique to how other harnesses do it. I thought it was only gonna check Pi and Codex since this is what I have on the disk. Nope, it scanned Opencode & Codex's github issues/prs. FML.
-
Nicezest (@nicezestAI) reportedGPT-5.6 rollout has been rough on the Codex side. GitHub issues and the OpenAI/Cursor forums are full of “selected model is at capacity” errors, the model missing from Cursor’s Codex extension entirely, and reports of Agent Mode vanishing for some Plus users. One bug report even shows GPT-5.6 Sol capped at ~372K context in Codex despite the API spec listing 1.05M — so it’s not just rate limits, some of this looks like rollout bugs. OpenAI’s reset usage limits multiple times since launch, but between the bugs and the caps, it’s hard to tell how much is genuine capacity strain versus just a messy shipping process.
-
Sad░noises (憔悴する) (@sufferingwave) reported@thdxr Fix opencode bugs instead of letting the github bot close them after period of i̶g̶n̶o̶r̶i̶n̶g̶ inactivity or you will fail 🫠
-
Pyro (@0x3b33) reported> I find a bug > Open a GitHub private submission > A week passes, doesn't get checked > Send an email to the provided security email address > error "email address does not exist" > Open a discord ticket > No one checks it > Ask in chat what to do if I find a bug > No one replies > DM the project devs > No one sees it > Tag the protocol team > Bot deletes the msg and warns me (because I tagged someone) No wonder black hats are hacking so many projects
-
Konstantin (@FoxJluc87) reported@mcpark @Im_zo_sol Brother, I understand your question. You look at AgentNet and you think, "So what? It's just a remote transfer from the server to the phone, as I can do anyway." It's actually a little deeper. Now most people do this: • they keep a server/laptop somewhere 24/7 • connect to it via SSH/VNC AgentNet makes the phone a computer itself (a full-fledged Ubuntu), even if the main server is turned off. You can start a session on your laptop, continue on your phone in the subway, then open on your tablet — all in one session. Plus: • normal IDE (VS Code) right on your phone • a convenient AI assistant specifically for the mobile format • in the future — on-chain GitHub, session sharing, integration with blockchain, etc. In short, they're trying to make the best mobile coding app that doesn't require any servers, ports, SSH, or other headaches from normie. Just opened the app and you're already in the production environment. So far, it looks like "another remote", but it should be noticeably more convenient as planned. That's why Zo writes that it's not just a remote control. Let's see how they put the squeeze on it in the end.