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 |
|---|---|
| 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 |
| Tlalpan, CDMX | 1 |
| Quilmes, BA | 1 |
| Bengaluru, KA | 1 |
| Yokohama, Kanagawa | 1 |
Check Current Status
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:
-
Vanta (@0xVantaa) reported9/ the team is not just random CT accounts. @dcc_crypto is the technical builder. @0xSquid_Sol is the co-founder / public face. both are @superteam builders. and the github trail shows squid wasn’t just tweeting about the engine. he was opening issues, PRs, and security fixes around toly’s tooling.
-
Virtus Cybersecurity (@VIRTUSCYBER) reportedOn May 11, 2026, SailPoint disclosed unauthorized access to a subset of GitHub repositories through a third-party application issue. Third-party trust keeps showing up in the incident timeline.
-
Paul Raimi💊 (@PaulRaimi11) reported$BASE B20 may get delayed again due to issues with GITHUB.
-
JesterHodl〚BIP-110〛 (@maciejsoltysiak) reported@bitcoincoreorg @HumbleWarrior I don't think the leveldb github issue link is correct. 61? shows a 16yo issue from jgarzik "Leveldb •#61(bitcoin-core/leveldb): Disable seek compaction "
-
Ahmed Said (@ahmed25s37) reported@github My account (formerly ffathy-tdx) was taken over on July 1, password & 2FA changed without my consent, then suspended. I'm a Pro subscriber and can't access the appeal form since I can't sign in. Ticket #4524519 open 7 days, no human response. Please help.
-
JoneMarrow (@JONEMARROW) reported@T3chFalcon “took down their github” I am dead in the ground and worms are infesting my corpse
-
Raven (@heyraven_io) reported@GoogleAIStudio @github step 1: one click. step 2: three days of why is this broken.
-
Andrew Mwangi (@Kiburei) reported@ayesha_fatiima Naisha... then na kumbuka Github suspended my account without explanation. Support's wakanighost Turns out the billion-dollar part isn't storing your code in folders—it's convincing all of us to trust them with our digital lives. Sahii na host my own *** server and CI/CD.
-
Electronic Intelligence Agency (@EI3065) reported@github @LinkedIn prevents acess for selected nationalities with programers doing imposible security checks on login; on repeat level of app becomes low of low for conflict
-
Keeta Github Tracker (@KeetaCode) reported🐆 Keeta GitHub PR Merged 📦 Repo: anchor 🔀 PR #386: Fix: Prefer Generalized Time 🌿 Branch: feat/prefer-generalized-time → main 👤 Originally opened by: @sephynox 🧠 Overview: This pull request updates how Keeta’s code handles time data, aiming to use a more general format where it fits, which likely helps avoid edge-case issues and keeps data handling more consistent. From the public description, this appears to be a small technical fix rather than a user-facing feature. It is labeled as a bug fix, includes one commit, and was approved on July 1, 2026. - “Generalized time” is a standard way of writing date/time information in structured data, so this change likely improves compatibility behind the scenes.
-
Solomon De Leon (@solomonjcdeleon) reportedI grew up from a young age playing/learning the guitar seriously Dad was a musician Learned it the right way took lessons, theory, scales, reading, aural training, exams and all that But then... I found out about tabs years after (my dad frowned upon me using it) Tabs are basically a number system to play the songs you want No theory needed, don't have to read the notes, don't have to understand scales and stuff just press the fret of the number you see on the screen It's probably how 80% of hobby guitarist learn to play the songs they like And it's nothing wrong with it tbh the end result you want is to play the song So now, vibe coding/creating with AI is like playing the guitar through tabs You can play the song but you have no idea how it works So vibe coding/creating anything for that matter works It just depends on what your goals are And for most people, "using tabs" is the right call If the goal is to ship, to move fast and test ideas, burning months on theory first is the wrong trade The tab player is playing the song this weekend. The theory student is still on scales Then again, even tabs need a floor You can't just read numbers off a screen and expect music to come out, you still need to know how to hold the pick, where your fingers go, how to fret a note cleanly Vibe coding has the same floor. If you don't know what GitHub is, what an API does, or how a database talks to your app, you won't even get the vibe coding to work in the first place So learn the basics. Version control, how to read an error log, what the moving parts of an app actually are and how they connect. Enough to not be flying blind. Because the person who only knows tabs hits a ceiling fast They can play the songs but can't write their own, can't improvise, and the second something breaks they're stuck Vibe coding is the same You move fast, right up until something breaks And the real trap is not that AI can't fix it. AI is an executor, it'll happily keep trying It's that you don't actually know what's wrong So you fall into slot machine prompting, pulling the lever again and again hoping the next prompt is the one, with no idea what you're even looking for Tabs can take you far, but if you want to write your own (good) music, you need the theory, you need to know what's happening under the notes So who should vibe code? Honestly most people who want to build simple but powerful tools Who should vibe code seriously? product, biz, marketing guys who are willing to learn If you're on the business side and you want to ship, test, get something real in front of people, vibe code away, it's the right tool for that Just know where the ceiling is, and learn enough of the basics that you're never fully at the machine's mercy Afterall as a non technical, your alpha is finding out what the right thing to build is (what people want), and selling it (monetizing it) Let the engineers take your 0-1 to 1-100 And if you want to be great, to be the engineer who builds the hard things, go for it and learn it properly, AI will still write code for you but you'll knock it out the park That skill isn't getting replaced. If anything it's worth more now, because everyone else stopped at the tabs Move fast with the tabs. But if you ever want to write your own music, learn the theory.
-
Electronic Intelligence Agency (@EI3065) reported@github @LinkedIn prevents acess for selected nationalities with programers doing imposible security checks on login; on repeat level of app becomes low of low for conflict
-
Zach Vorhies / Google Whistleblower (@Perpetualmaniac) reported5 attempts to drop a malware payload. @github please fix this
-
Daniil (@hey_daniil) reportedI built DevIntern because I was my own bottleneck: agents were idle while I context-switched, my focus shredded by checking in on them. The tools weren't slow. Supervising them was. DevIntern makes the whole loop async, and here's exactly how: 1. It connects to your existing tracker — Jira, Linear, Trello, Asana, Azure DevOps, GitHub Issues, even markdown files. Your tickets are already the input. 2. Vague ticket? It specs it into something an agent can execute, so prompt quality is never the bottleneck. 3. It runs your coding agent, your model, your API keys inside your repo — and the subscriptions you're already paying for finally work around the clock, not just when you're watching. No lock-in, no token markup. 4. Output is a pull request. Review, merge, done. The output of a team of agents, the headspace to do your best work. No supervision, no burnout.
-
Alan Lam 🔥 (@extralam) reported@AndreiOnel @github more say what we want to solve is my issue. Private repositories often have limited GitHub-hosted Actions minutes.
Check Current Status