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 |
|---|---|
| Inverness, Scotland | 1 |
| Quito, Pichincha | 2 |
| Junín, Manabí | 1 |
| Guadalajara, JAL | 1 |
| Paris, Île-de-France | 6 |
| São Paulo, SP | 1 |
| Ipauçu, SP | 1 |
| Vigo, Galicia | 1 |
| Tel Aviv, Tel Aviv | 1 |
| Éragny, Île-de-France | 1 |
| Saltillo, COA | 2 |
| Montlhéry, Île-de-France | 1 |
| Aulnay-sous-Bois, Île-de-France | 1 |
| Granada, Andalusia | 1 |
| Vernon, Normandy | 1 |
| Township of Evan, KS | 1 |
| Madrid, Madrid | 1 |
| Bogotá, Bogota D.C. | 1 |
| Lyon, Auvergne-Rhône-Alpes | 1 |
| Lima, Lima | 1 |
| Aix-en-Provence, Provence-Alpes-Côte d'Azur | 1 |
| Trento, Trentino-Alto Adige | 1 |
| Le Chambon-Feugerolles, Auvergne-Rhône-Alpes | 1 |
| Antananarivo, Analamanga | 1 |
| Lure, Bourgogne-Franche-Comté | 1 |
| Ashkelon, Southern District | 1 |
| Veigné, Centre | 1 |
| Saint-Paul, Réunion | 2 |
| Mexico City, CDMX | 1 |
| León de los Aldama, GUA | 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:
-
Luciano655 (@Luciano655dev) reportedBuilding a startup in 2026 is cheapest - Claude = coding. ($0–$20/mo) - Supabase = backend + database. ($0/mo) - Vercel = deployment. ($0/mo) - GitHub = version control. ($0/mo) - Cloudflare = DNS + security. ($0/mo) - Clerk = authentication. ($0/mo) - Resend = emails. ($0/mo) - PostHog = analytics. ($0/mo) - Sentry = error tracking. ($0/mo) - Upstash = Redis. ($0/mo) - Pinecone = vector DB. ($0/mo) - Hugging Face = AI models. ($0/mo) - Groq = AI inference. ($0/mo) - Figma = UI/UX design. ($0/mo) - Canva = design + marketing. ($0/mo) - Notion = docs + planning. ($0/mo) - Linear = project management. ($0/mo) - GitHub Actions = CI/CD. ($0/mo) - Google Analytics = web analytics. ($0/mo) - Cloudflare Pages = hosting. ($0/mo) Total infrastructure cost to build your first startup: $0–$20/month. The barrier isn't money anymore. It's execution. What's holding you back?
-
Julian Goldie SEO (@JulianGoldieSEO) reportedCursor just gave your code a second home right next to your AI. It's called Origin. Repos, pull requests, and an agent built right in. You keep GitHub as the source of truth. Origin just syncs alongside it. Change something in Cursor and it shows up on GitHub in seconds. The AI reads your code, fixes it, and opens the pull request itself. GitHub went down for 6 hours the same week this launched. Most people think it's Cursor versus GitHub. It's actually built to use both at once.
-
Michael S. Collier (@MichaelCollier) reportedDoes the GitHub Copilot CLI (v1.0.80) support Agent Plugins 1.0 and Copilot-specific extensions? I've tried putting an "agents", "instructions" and "hooks" folder under the "com.github.copilot" folder, but I never them in the CLI. Skill and MCP server OK. #GitHubCopilot
-
Leo Lemos (@mrlemoos) reported@thekitze I said this months ago when GitHub first went down: GitHub is the next GitHub. Open source won't migrate off it. Period.
-
Victor (@victor_vibing) reported@tdinh_me What did he build? Proof is in the outcome. I have several genuinely useful projects on github that break the impossible barrier. In a sense that a similar problem has never been solved by companies with 1 billion+ cap, this efficiently anyway. Or never solved as fast as I did it
-
Bellache (@ABellacheh49800) reported@gailcweiner I suspect it was heavily trained on github issues and ticket discussions. As well other troubleshooting boards. Probably to boost reliable output. But now the model sounds like a dweller of these places.
-
Pratik Sharda (@pratiksharda2) reportedThousands of passengers injured every year by turbulence no one sees coming. Clear air. No clouds. Radar misses it completely. A problem that can't be sensed, only felt. One of our buildathon engineers put an ML model on an ESP32 reading an IMU at 400 kHz. Classifies severity on device. No cloud. Streams live telemetry to a 3D flight viz in the browser. In just 4 hours... Github repo in comments.
-
ton (@tontheneko) reportedOn Github, there are two type of accounts: - Individual (for people) - Organization (for companies) Pump does not support organization claims. Organizations are unable to login to Pump website and claim coins. This coin cannot be claimed by Slopius team. $SLOPIUS y5tmt3dkV5EzkiBECUWoNioN66NsS8rG3BZ5ik6pump (I'm not in any other coins, only providing information)
-
Syed Daim Kazmi (@D_kazmi) reported• Added GitHub rate-limit protection that blocks calls when the remaining quota drops below a safe threshold • Added safeguards around write operations such as issue creation and limited repeated tool usage during an agent query
-
Lucas Rodrigues (@olusrodri) reportedi would like so much contribute to the @XDevelopers api developement but is so sad there is not a official way to open a issue or something else like github repo issues
-
Kappaemme (@Kappaemme1926) reportedMY CODEX SKILL JUST HIT 1,000 GITHUB STARS! I’m honestly so happy right now. I built First Customer Finder to help founders use Codex to find potential customers backed by real public signals. Seeing 1,000 people support something I made feels unreal. Thank you to everyone who starred it, tried it, shared it, opened an issue, or contributed. I’m going to keep making it better. What should I add next?
-
Gerred Dillon (@sloppenheimer) reported@ajambrosino this is my biggest complaint. i've had to fix so many unverified commits because it's not available to the sandbox, or gh shows as unauthenticated. it'll even open Chrome to browse authenticated github instead of just...checking the sandboxing?!
-
John Koretoff (@JohnKoretoff) reportedWhen a ship ran aground, nobody asked for the shipyard drawings first. They asked for the log. The drawings said what the vessel was supposed to do. The log said what it actually did. Wind. Heading. Who had the watch. Where the sounding changed. If you could not produce the log, you could not stand behind the voyage. Software used to work like the drawings. You read the code and you knew what would happen. The logic lived in a file. A debugger was a convenience. The source of truth was the repository. Agents do not work like that. Harrison Chase said it plainly on Sequoia’s Training Data: in software, the code is the source of truth. In agents, you send a trace. The model is a black box of parameters you cannot usefully read. The harness is the opinionated scaffolding around it — a planning tool, compaction when the window fills, a file system so the run can put work down and pick it back up. An LLM in a loop, for hours, not one prompt and out. That loop is finally working. Coding first. Then research. An incident writeup. A first draft a human still has to look at. The models got better. That is half of it. The other half is the harness caught up. AutoGPT was the idea years ago. An LLM deciding what to do, over and over. The models were not good enough, and the scaffolding was not either. Chase’s cut is that the same simple algorithm started to work once people got serious about context: what is actually in the window at step fourteen, after thirteen tool calls nobody typed by hand. A single model call is inspectable from the prompt. You wrote the prompt. You know what went in. An agent at step fourteen has pulled files, compacted history, spawned a subagent, and stuffed the window with things no one authored. If you cannot see that window, you do not know the program you shipped. “Send us the code” was the old debug. “Send us a trace” is the new one. Copies got cheap. First drafts. First pull requests. First incident notes. The scarce thing is not another model. It is a record of what the agent actually did, so a person can permit the next hour of work. Permission without a log is a guild with no minutes. That is why a trace is not observability as a nice-to-have. It is the ledger. Tests get built from it. Teams argue over it instead of a GitHub diff. If memory ever becomes a moat, it will be because the system learned from yesterday’s traces without lying about what happened. I already wrote that the bottleneck moved from talent to permission. This is the mechanism. You do not get permission for a non-deterministic actor unless you can show the run. The harness is how it stays on the rails long enough to matter. The trace is how you prove it did. When intelligence is cheap, the unprintable thing is the path it took.
-
Oscar Diedrichs (@oscardiedrichs) reported@Candid_Apples @linuxuser1996 I still use github for useless stuff. The problem is the lack of alternatives. We as users tend to become lazy, find a great service and the tadaaa Microshit buys it or some other horrible company. The list of services and tools I've lost off the top of my head: - Wunderlist - Swiftkeyboard (can be used on graphene or other devices where you can turn off network traffic) - Github I most also say Ubuntu. I ran 22.04 for years, because I lacked the time to upgrade, then I broke it during upgrade to 24.04 so I put in cachyos instead. Have 24.04 at work and it feels like Windows 11. Just that they try clone dumb **** from windows no one wanted tells the tale. Luckily I could disable the horrible window alignment crap that was introduced in 24.04 but it really feels like Microsoft Linux and I guess it's where they want to go. Microsoft delenda est!
-
Mahmoud (@thisismahmoud) reported@cderm @Railway hmm, I'm unable to reproduce the issue. Login with GitHub works for me in both Chrome and Firefox Are you consistently running into this?