GitHub Outage Map

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:

• 
  Tomer Stern (@tomer_stern) reported 2 minutes ago

  @Isaac_Tea @LinkofSunshine Yea write some code showing off your abilities in analogous, dumbed down scenarios to what you deal with at work, and put it on GitHub

• 
  █ (@0xDGraM) reported 4 minutes ago

  @AUTOMATEWITHOLA lol been around for long and you should also add that you need a high end pc to run it locally or else it will be too slow You are just not updated it’s nothing new A lot of things are open sourced on GitHub already

• 
  Abbas Asadzade (@AbbasAsadzade) reported 5 minutes ago

  The new wave of AI-native business frameworks all end with the same step: compound into a skill and rerun on cron. Looks clean on GitHub. The part that actually decides whether it works is what happens when the skill is slightly wrong and keeps compounding the error every night while nobody’s watching.

• 
  Casper (@casper10099) reported 7 minutes ago

  Claude Code quietly burns tokens on garbage you never asked it to read. Every *** status, every docker dump, every ls — the raw terminal output gets stuffed into context, noise and all. That's the problem RTK (Rust Token Killer) was built to kill. 62,000+ GitHub stars and climbing. It sits between Claude and your shell. One line to install, then wire it in with rtk init -g. From that point, your shell commands — ***, find, grep, ls, docker — get routed through RTK first. Before the output ever reaches Claude, RTK filters the noise, drops duplicates, groups repeats, and trims the boring middle. Less junk in, fewer tokens spent, lower bill. But I'm not going to sell it clean, because it isn't. Security reviewers have flagged real concerns: shell injection risks, telemetry on by default, and command history sitting in a local SQLite DB for up to 90 days. None of that is hidden — you can audit it yourself, and clear the log with rtk gain --history — but you should know it's there before you wire a filter into your shell. And here's the detail most people miss: RTK only touches shell commands. Claude Code's native read, grep, and glob tools skip it entirely. So the token savings are real, but narrower than the hype makes them sound. Worth knowing if you live in Claude Code. Whether it's worth installing — that's a call only you can make once you've read the tradeoffs.

• 
  alias (@loadingalias) reported 7 minutes ago

  @mgill25 I have spent 7 years thinking about this. I’ve even worked out some of the systems design it requires today. You don’t know me and your following might not know me, but I am the guy to say this… The primitives required to make a real improvement to GitHub just don’t exist. I found this out and decided that my life’s work was going to be the primitives. Having said that, I’m 60-90 days from looking to raise on a demo. This is a monstrously challenging problem and it requires so many breakthroughs to make a reality. You can pass the scalability issues and other issues to new systems and alleviate a little pain… but you can’t make a major shift. Do you treat data and code as one? How? What is the chunking mechanism? How do you manages ETL/ELT/CDC/etc? You can’t bind to *** anymore (I think *** falls in the next three years). You can’t bind to so much of what GitHub uses today. It’s just a HUGE issue. It’s a fundamental computer science issue, or series of issues.

• 
  Titan (@Titan_06_) reported 8 minutes ago

  Progress Update: > Finished making a Hashmap entirely in C > Read till Ch 18 of beej's guide to C GitHub link for the hashmap is down below in the comments, if anyone wants to see it. Will start work on the text editor today :-)

• 
  Mac (@mac_eth) reported 9 minutes ago

  @farizvect I wanted mine to investigate 6 different automated alerts. It tied with subagents and failed bc of: 1) limit on number of subagents 2) 10 min timeout on the subagents Also we have 200 "TODO" github issues -- I'm looking for something that can do them by tomorrow morning. And Hermes said that's too much for it lol.

• 
  StatusDrop (@StatusDrop) reported 10 minutes ago

  GitHub Actions stalls and suddenly your deploys, and half your team's day, are frozen. It's not your outage, but it's your problem to explain. A status page does the explaining for you.

• 
  Austin Roy #SurvivingUPS (@AustinRoy007) reported 11 minutes ago

  Another day, another broken sandbox, interesting thing here is "Didn't hack anything, just went to GitHub to find answers", does this mean that open weight models are.... Safer? 🤔

• 
  Cyborg (@0XCyborg_Web3) reported 16 minutes ago

  @shynrz007 whats the fix here github link on the site or a whole new build

• 
  A War (@AWar1586398) reported 16 minutes ago

  @svpino I like asking the AI to create a document about the fix in code so that I could read it in prose. If there are any call-outs to things that it thinks are specifically interesting or should be checked, there are inline links that go to the line in GitHub. That seems to be a better way of doing it

• 
  Sandeep (@sandeeyps) reported 16 minutes ago

  7000 posts about the GitHub Actions outage in two days The interesting part is not that it went down it is that almost nobody had a second path to production We treat CI like electricity it is actually a vendor with a status page One provider for build, test and deploy is one dependency, not three 🧯

• 
  Eric (@transurfer) reported 17 minutes ago

  Ever seen a tool that actually gets better fast? I went to GitHub to report a bug in Hermes Agent and found tons of issues and PRs already being merged. Looking forward to what's next.

• 
  Bob (@skytaleSythe) reported 18 minutes ago

  @IAMERICAbooted Totally get it - since July 1 GitHub copilot switched. Even with the switch to API based pricing - Sataya said prices have to come down and proposed fielding DeepSeek to help reduce prices further. The days of Enterprise unlimited subscriptions are gone - but it’s a race to the bottom from now on.

• 
  ZomboDB (@zombodb) reported 18 minutes ago

  Whenever GitHub is down I smoke meat.