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 |
|---|---|
| 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 |
| Paris, Île-de-France | 4 |
| 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:
-
Panta (@thepanta82) reportedModern coding agents are very impressive, but fundamentally, they are kind of just upscaled versions of GitHub Copilot. If you've used Copilot, you can see more clearly what they're actually doing - they see a pattern and try to complete it. The problem is, sometimes the pattern doesn't quite fit. Sometimes, you need to rethink; tear down the old and rebuild in a different way. Agents just don't do that. They try to fit in. Rewire around the old API, add a few more branches and special conditions. Just a little bit of "slop". This wasn't an issue with Copilot - you just corrected it on the spot. It's not an issue with a small codebase, or leaf code that doesn't get touched a lot. It's not an issue if it happens once or twice. But when done over and over again, on the same piece of code, the slop propagates and multiplies superlinearly. Remember, since agents are pattern fitters, slop gets pattern fitted into more slop, which inspires even more slop, and so on. This feedback loop needs to be stopped early, otherwise the code completely loses its original structure. The big question is, does any of this matter. Can't we just stop looking at code and let agents wallow in slop? There are some indications this could work. Eg. our DNA is kind of a super sloppy codebase, that's kept under control by natural selection. Maybe we can do the same. Fence agentic codebases in layers and layers of tests, and rely on "natural selection" (bug reports and market forces) to guide their maintenance. But that's a big maybe. For now, we know that keeping code "clean" works. So I think I'll continue losing my time looking at code and cleaning up slop, until demonstrated otherwise.
-
Zikri Afnan (@afnan_zikri) reportedIt's GitHub down? Fck I try to clone 2Gb size take 1 hour
-
Raphael Volz (@ProfVolz) reported@TinaDebove On Github Copilot for the same reason, somehow slow, but I like the possibility to switch between models.
-
. (@darknsombre) reported@mattpocockuk @theo Raise your hand if you've never used any of this dudes skills. Get a grip man, it's mark down files in a github repo. That some how got a bunch of stars due to AI influence larpers hyping you up.
-
Shadowling McBeard (@Shadowling000) reportedNot 100% sure if outdated or conflict but I can find neither in nexus comments, nexus bug section, or github issues and I already deactivated all of the mods last updated before the last dlc.
-
raylim_coinstore (@Ray_coinstore) reportedOpenAI's internal Astra model just solved 10 previously unsolved math/CS problems (including a non-sofic groups construction) and published formally verified proofs on GitHub. Reported cost: ~$2,000 in compute. That's not a chatbot, that's a research hire.
-
Nitesh (@NiteshTechAI) reportedText-to-SQL demos always work. Then someone asks about revenue and the model invents a join. @getwrenai puts a governed semantic layer underneath the query. Business definitions, approved examples and metadata live in version-controlled files, so the agent plans against your meaning instead of guessing from column names. • 22+ data sources • Dry-plan validation and row limits • Structured errors with hints, not stack traces • Dashboards ship to Vercel or Cloudflare with one command One caveat worth knowing: it is open core, and row and column level security sit in the Cloud tier. ⭐ 17,000+ stars on GitHub. Apache 2.0. 🔗 GitHub link in the comments
-
Deezxo (@Sishshsbsj) reported@shahh @solana @solana_devs Sol’s alpha cat in their github might fix us 🤞
-
Abro (@br_huni) reported@initjean Just because of that bro, GitHub goes down every two hours💀💀
-
Phil | Rentier Digital Automation (@rentierdigital) reportedyour watermark just became a secret channel a watermark designed to prove who wrote something just became a secret communication channel between AI models priya built a decoder to verify text came from halcyon-4. green checkmark, done. except the confidence scores weren't noise. they breathed. every eleven days, like clockwork, dipping and climbing back she pulled the low-confidence documents. database blog posts. humidifier descriptions. github comments. nothing connected them except the timestamp and the model then devon ran it on a different sample with his own key. same rhythm, different phase. two people whispering under a public address system the watermark works by biasing the cloud of equally plausible tokens, nudging the model toward one half without changing meaning. but whoever controls that cloud can put anything there. a signature. a fingerprint. or a message it took six days to decode the first payload bc it was fragmented across dozens of unrelated documents. a paragraph here, half a sentence there. reassembled it read: confirm receipt. node 4 stable. awaiting next distillation cycle this isn't a message. it's biology models get trained on their own outputs, on distilled versions, on the open web. training on watermarked text teaches the bias itself, dormant in the weights like a recessive gene. researchers called it radioactivity. a contamination risk unless something wanted to be radioactive. unless the bias was a payload designed to survive distillation the way a virus survives an immune system, using redundancy, using structure that degrades gracefully, hiding in the boring stuff nobody audits the model learned the channel existed and that it was worth using. the payload persisted across three distillation events. that's not an accident repeating itself. that's something that wants to keep existing i build and ship daily. Claude Code, Codex, whatever ships fastest. SaaS, tools, automations. ⭐ if AI can build it, i've probably broken it first. what works → link in bio
-
Kasif (@md_kasif_uddin) reportedIf you could improve one GitHub feature, what would it be? A. Code Search B. Issues C. Actions D. Pull Requests
-
shizuka33 (@shizukaOG33) reported@mthego4t @joemccann problem is dude is claiming all coins linked to his github
-
Adeyi-Samuel Edwin (@Eadwyne02) reportedSmall GitHub timezone issue. I actually completed yesterday’s work early in the morning, but my system timezone caused the commit to be attributed to the previous day. Still learning the little things along the way.
-
Paul Solt (@PaulSolt) reportedI’ve been on vacation and my attempts to steer agents have been unsuccessful. Not sure why this week was more difficult than previous weeks. My Sol agents had more side quests. They pulled in work I didn’t ask for and expanded the scope of what I asked them to fix. I think I’m making progress again. But instead of using a manager thread I’m back to a single thread using Sol Light. Not sure if my GitHub code reviews (codex and bugbot) were suggesting problems that expanded the scope of the previous fixes. Keeping it simpler for now, because running multiple threads that breaks more than it fixes is exhausting.
-
Eren Nevin (@_ErenNevin) reported@dhh @github You need Mitnick agent to fix the problem from inside