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:

• 
  khushal (@celeroncoder) reported 3 minutes ago

  @get_bb_app I've filed a GitHub issue with more context. Also saw a pr that's doing similar work but in a broader sense so commented there with ref to the issue filed Will see if I can create a pr myself, the stopchild fix (I've mentioned in the PR as well) seems to be working locally. Workflows closing the done worker spawns after completion so memory is only blocked by concurrent running threads/worker

• 
  Jonathan Berg (@jbtradin) reported 6 minutes ago

  Login with Github or Google?

• 
  Valentyn Kit 🦀 | Rust · Solana (@valentynkit) reported 12 minutes ago

  @tsoding the reliable part of github is that it goes down predictably enough to farm content off it

• 
  Linus Mixson (@LinusMixson) reported 12 minutes ago

  @lumpenspace A lot of hype for this dumb-*** repo. Shocking that GitHub keeps going down.

• 
  Zevryn (@Zevryn0) reported 12 minutes ago

  19 months ago, ai16z was the AI x crypto story. Launched on @Solana in October 2024 with ~$75K raised, it went from a tiny experiment to nearly a $2.5B market cap by January 2025. The pitch was simple: an AI-run venture fund. Then reality caught up. A forced rebrand to @ElizaOS. A 10x token supply expansion in late 2025. A class-action lawsuit alleging the project wasn’t as autonomous as marketed. And on August 4, founder Shaw Walters effectively declared the token dead, with the foundation winding down. The token is now down more than 97% from its peak. But here’s the interesting part: The technology didn’t die. ElizaOS’s GitHub is still active. Development continues. Walters says he’ll keep building the open-source software just without another token attached to it. That’s the lesson I’d carry into the next AI agent cycle: The protocol and the token are two completely different bets. A project can build useful technology while its token goes to zero. Don’t confuse owning the technology with owning the ticker.

• 
  Iqramul Hussain (@iamiqrram) reported 15 minutes ago

  @cursor_ai @github stop asking "Are we there yet?" 80,000 times a second. The best part? Cursor relies on GitHub under the hood to sync repos, so Cursor’s own launch day workflows were frozen by the outage. They literally couldn't even tweet properly because their internal tools were broken.

• 
  𝕘 𝕥 𝕨 𝕪 (@Gtwy) reported 16 minutes ago

  @congressdj @bot half of the connectors on grok bot don't work spent two days using it to write it's own software instead of using the connectors then realized i could use it to stand up a better system entirely that runs over grok code that connects to everything with no issue still use grok bot for heavy software development but other than some ssh gets and github i have zero motivation to connect it to anything else now

• 
  Lassiter Gregg (@lassitergregg) reported 20 minutes ago

  @webdevcody @conductor_build i have a similar process for triaging bugs and grooming issues which end up as a github issues with a whole equation for stack ranking and prioritizing work.

• 
  Julian Goldie SEO (@JulianGoldieSEO) reported 20 minutes ago

  CURSOR JUST BUILT A GITHUB ALTERNATIVE INSIDE THE EDITOR. And the timing could not have been better: GitHub went down for around 6.5 hours the same day Origin launched. What Cursor Origin actually does: → Hosts repos directly inside Cursor → Adds pull requests + a full code browser → Keeps two-way sync with GitHub → Lets Cursor agents read code, make changes, update PRs, and push new versions The clever part: ✓ GitHub can stay your source of truth ✓ Changes in Cursor sync back to GitHub ✓ GitHub reviews can appear inside Cursor within seconds ✓ Vercel can generate live previews for proposed changes ✓ Depot or Buildkite can run your existing checks The mistake is thinking you need to choose Cursor OR GitHub. You don’t. The smarter setup is GitHub + Origin together: Keep your existing repo. Sync it into Cursor. Put the AI agent next to the code. Test everything before moving anything. Origin isn’t replacing GitHub overnight. It’s making the gap between “write code with AI” and “manage code” much smaller.

• 
  AGTP (@AGTPinsights) reported 22 minutes ago

  Anthropic just rolled out Claude Mythos 5 for enterprise code security scans today. Here's what you need to know. Claude Security scans now run on Mythos 5, Anthropic's most capable cybersecurity model, in public beta for all Claude Enterprise customers starting August 21, 2026. Enterprises can use it without needing separate access to Mythos 5 itself. Point Claude Security at a GitHub repo and Mythos 5 traces data across files, reasons about how components interact, and flags vulnerabilities. Each finding includes a CWE category, confidence rating, severity rating, and a suggested fix, and patches open in Claude Code on the web. Mythos 5 itself stays access-restricted, running only behind the scan, so it returns findings without exposing the underlying model directly. This is the first time Mythos 5 capability has reached anyone outside the original Project Glasswing partner group. Alongside this, Anthropic is integrating Mythos 5 into partner security products and launching a Defender Advantage Fund with $35 million in Claude credits for open-source security work. Key numbers: - $35 million in credits for the Defender Advantage Fund - Mythos 5 pricing: $10 per million input tokens, $50 per million output tokens - Over 10,000 high- or critical-severity vulnerabilities found via Project Glasswing as of May 2026 - ~50 initial Glasswing partners, expanded to ~150 organizations in 15+ countries by June 2026 Claude Mythos 5 launched June 9, 2026 and remains limited to vetted partners for direct dual-use access.

• 
  WilcosX.eth (@WilcosX) reported 22 minutes ago

  @Crypto_Zh0u @commonsmade missed the love train too just waiting on that github fix now

• 
  Lummox (@Lummox_eth) reported 24 minutes ago

  I found a 275K⭐ GitHub repo that makes coding agents debug more like engineers and less like autocomplete. Superpowers forces a root-cause-first workflow: no speculative fixes, no random edits, no jumping straight into code. I tested its systematic-debugging method on a broken auth flow. The visible bug was simple: login worked, then the user got kicked back to /login. The actual cause was hiding one layer deeper. The API returned expiry time in seconds. The frontend compared it against milliseconds. 1000× mismatch. Superpowers traced the failure, compared the working refresh path, formed one hypothesis, applied one targeted fix, then ran the tests. 18/18 passed. That’s why this repo is interesting. It doesn’t give the agent more intelligence. It gives the intelligence a process. Save this before letting another coding agent “just try a few fixes.”

• 
  Jesse Nickles (@jessuppi) reported 27 minutes ago

  Update #2: Nope, ChatGPT "Chat" still sucks big time after these latest updates. Seems the new "Work" mode is the only way to get any serious work done, regardless of whether on GitHub or otherwise... they have stripped down the "Chat" mode to be extremely retarded now.

• 
  KZZY (@kzzy47) reported 28 minutes ago

  GitHub had a 7 hour 47 minute outage this month. Also posted an all time high of 2.9 billion commits, up from 1.4 billion in April. Wild that both are true at once.

• 
  Jeetendra (@jeetendrayd) reported 28 minutes ago

  @RhysSullivan This was the reason the GitHub server was down, as more code is being pushed due to coding agents