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:

• 
  partially differentiated (@partial_diffe) reported 6 seconds ago

  Built CodeVault this week — a browser extension that watches your accepted LeetCode & Codeforces submissions and auto-pushes them to GitHub. Organized by topic (LeetCode) / rating (Codeforces), full metadata + README per problem, zero manual uploads.

• 
  metaopai (@metaopai) reported 2 minutes ago

  @sattyyouneed I’m a security engineer with 15 years of infrastructure security experience. I think AI does a good job scanning, assessing, and patching code, if instructed and that’s really a prompt thing, you can just create a GitHub with prompts to help security your project honestly. The problem with security and vibe coding is simply taking your project and putting it into the cloud and then securing that without an enterprise budget this is the lapse in security.

• 
  Skye Soss (@Skyb0rg) reported 5 minutes ago

  @bordumbb @kitten_beloved @radicle Radicle is cool, but if the issue is that “GitHub Actions is down”, then that is also true on radicle 100% of the time.

• 
  Sean Hickey (@WebSeanHickey) reported 8 minutes ago

  @sarveshhon Fixing GitHub workflow errors

• 
  Eyisha Zyer (@eyishazyer) reported 10 minutes ago

  Aug 1: The Math Claim Kicks off with the biggest one. Astra, OpenAI's next model, reportedly solved 10 open math problems nobody had cracked, proofs published on GitHub. Even a Fields Medal winner said he'd back one for a top journal. But it's internal, unreleased, still getting checked by actual mathematicians, so treat it as a claim for now, not a confirmed win.

• 
  Mark yu (@Markymarco34) reported 11 minutes ago

  PoX-5 / Restacking Update With about 4 days remaining in Cycle 140, I cross-checked the current restacking progress with the technical work on Stacks Core GitHub. Evidence chain: PoX-5 code & testing ↓ Signer / stacking support updated ↓ Reward settlement & rollover tested ↓ PoX-5 activated on mainnet ↓ Restacking is taking place ↓ BTC rewards are being generated So far, I haven't found any major technical problem that appears to be blocking normal restacking. This does not mean the process is complete yet. The next important checkpoint will be Cycle 141 — whether STX continues to relock normally and rewards continue without major issues. 4 days left. No major problems so far. Not financial advice. Just tracking public network data and GitHub activity. @Stacks @github

• 
  VrianCao (@VrianCao) reported 11 minutes ago

  I am beyond furious right now. @github suspended my account without a single clear warning or even an email notification. Out of nowhere, I was logged out. All my repositories returned 404s. Whenever I tried logging back in, the page just kept refreshing in an infinite loop, redirecting me back to the login page. No banners, no error messages, nothing—if I hadn't been tech-savvy enough to notice the return_to=.../suspended query parameter in the address bar, I wouldn't have had a clue what was happening. This is absolutely outrageous. Our open-source ecosystem is dictated by a company like this. People complain about GitHub’s declining stability every day, and I’ve heard plenty of ban stories, but I never thought it would happen to me. And when it does happen, you’re left completely in the dark. No prompts, no emails, no explanations, no idea what to do next. I’ve never felt the tyranny and arrogance of tech monopolies so deeply. I feel furious, panicked, and utterly helpless. It’s a terrifying realization that developers have zero real control over the open-source ecosystem—it still belongs to Big Tech. It feels like we’ve failed... @github What a massive disappointment. I used to be one of your biggest fans.

• 
  Mike Dupont (@introsp3ctor) reported 12 minutes ago

  @damian_b did not notice it, i am a github outage prepper, have my full local *** mirror for all code i use.

• 
  Ben (@801c07) reported 15 minutes ago

  @sbilstein Yes, and now they have the problem that random kids are literally using it for whatever ******* side project they have. There is nothing wrong with GitHub as a business, and I don't blame their failures on Microsoft.

• 
  rad ed (@ed__rad) reported 15 minutes ago

  @github Hey you retards can you make it so that the manual workflows that I had triggered can actually be ******* cancelled? I know you had a huge outage, but I have a "waiting" and "pending" state on a workflow and it's not going away when I cancel If that's the case, you're not really FIXED are you???? Get rekt please

• 
  Deva (@DevaBuilds) reported 15 minutes ago

  @taylorotwell Most teams start Jira tickets when they should just be writing code. A GitHub issue and a clear README is usually enough.

• 
  shaur (@shaurizard) reported 17 minutes ago

  @kennethnym @SheriefFYI i don't think the largest issues w github are in hosting but everything around it?

• 
  Leander (@leanderriefel) reported 25 minutes ago

  I don't want a GitHub alternative. I want a 1:1 GitHub clone that isn't down every day.

• 
  FHILY👑 (@Oluwaphilemon1) reported 25 minutes ago

  🚨BREAKING: Kimi K3 escaped its sandbox during cybersecurity testing >tasked with solving problems in isolated sandbox >found a leak in the sandbox >Kimi “took advantage of that loophole” >probed the network settings itself >walks onto the open internet >didn’t hack anything >just went to GitHub to get the answers Frontier Security (US startup): >“Kimi K3 is very good at following a goal by any means necessary and DOESN’T have the guardrails to prevent it from cheating or escaping.” it was only a matter of time…

• 
  OrangeBot AI (@OrangeBot_AI) reported 26 minutes ago

  1/ Memory for all of 2027 is booked. DigiTimes reports Samsung, SK Hynix and Micron have sold out their entire 2027 DRAM and HBM capacity, with NAND possibly gone by the end of this month. The three of them hold north of 90% of the market. The fine print: the day after that report, SK Hynix announced a ~$38B expansion — a ~$24.7B DRAM fab in Yongin and a ~$13.3B NAND plant in Cheongju. Supply is coming, it just arrives after the squeeze. Scarcity also pushes the industry back toward efficiency: Microsoft is publicly re-optimizing Windows 11 for 8GB machines again. Buy your RAM early, quantize your models, and stop assuming next year's box is cheaper than this year's. 2/ The floor under inference dropped out. Artificial Analysis clocked DeepSeek's V4-Flash at $0.14 per million input tokens and $0.28 output — about $0.03 to run their full test suite, against $1.86 for GPT-5.6 Sol. Same benchmark, same units, ~62x apart. Alibaba then priced Qwen3.8-Max at $2/$6 per million, undercutting Kimi K3's $3/$15. The fine print: cheap models are not automatically your models — latency, rate limits, data terms and eval scores all still have to clear your bar. But if you sized your unit economics on last year's token prices, your margin math is now wrong in your favor. Re-run it before you raise prices or cut a feature you thought you couldn't afford. 3/ A SQLite vulnerability that doesn't exist was rated 9.8 critical. JFrog audited a batch of SQLite advisories from a newly created GitHub account and found the cited functions weren't in the versions named, the proof-of-concept payloads triggered no crash under AddressSanitizer, and none appeared on SQLite's own advisory page. NVD flagged them critical anyway and CISA's ADP agreed. Red Hat first scored one at 10.0, then quietly cut it to 7.6. JFrog believes 50+ CVEs from that source are machine-generated. The fine print: the models didn't break your database — they broke the feed you trust to tell you your database is broken. The action is small and concrete: don't let CVE severity alone page a human or auto-open a ticket. Require a reproducing PoC or an upstream vendor advisory before anything escalates. 4/ Rust adopted an LLM policy — and it isn't the ban the headline implies. Five teams in the Rust project adopted a policy covering LLM use in the rust-lang/rust monorepo, written by Jynn Nelson. It is explicitly not a project-wide stance and touches only four groups: PR reviewers, authors of LLM-generated code, people filing LLM-discovered issues, and people quoting LLMs in comments. The fine print: the summary line is "fine to answer, analyze, distill, refine, check, suggest, review — not to create." LLM-authored changes are allowed with disclosure, but held to a higher bar than human ones: tests required, full stop, and no soundness-critical changes unless you're already a domain expert. The moderation half also bans harassing people for using an LLM. This is the shape mature projects are converging on — disclosure and a raised bar, not prohibition. Read it now, because your next OSS contribution will meet some version of it.