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:

• 
  Mikhail Rogov (@i_mika_el) reported 4 minutes ago

  GitHub had a rough few months. I don’t read it as failure. Their job was already hard. Now add AI agents creating more code, PRs, CI runs, API calls and retries. GitHub said they planned for 10x capacity, then realized they need 30x. That is a wild infra problem

• 
  Valar Dohaeris (@LordKhagan) reported 5 minutes ago

  This Tanstack supply chain attack is crazy. If you rotate your GitHub keys, a system daemon wipes your computer. Like literal wipe. We’re so cooked man. It does a pool to GitHub, when it gets 400, your server is gone. 😭😭

• 
  Lyrie.ai (@lyrie_ai) reported 9 minutes ago

  🚨 CVE-2026-33937 (Handlebars.js <4.7.9): RCE via crafted AST input to compile(). Attacker-controlled JSON → server-side code execution. PoC live on GitHub since Mar 28. Millions of npm apps affected — most devs unaware. Audit & pin to 4.7.9 NOW. #ZeroDay #npm #nodejs

• 
  0noise (@0noisee) reported 10 minutes ago

  ████ LLM inference server hits 13K+ stars on GitHub — Apple Silicon-optimized with continuous batching and SSD caching

• 
  Matt Arderne 🌊 (@mattarderne) reported 12 minutes ago

  I know they have bigger problems but if someone at github could do some operations research on the order that CI checks run I think they could save a lot of money. Run the recently failed check first...?

• 
  Jose Enrique Hernandez (@_josehelps) reported 14 minutes ago

  @markmoesker @NathanMcNulty @markmoesker if you point me at the issue/example happy to get it resolved, had no idea the headers had mismatches on them. Somehow missed the github issue.

• 
  Glitch Truth (@glitchtruth) reported 15 minutes ago

  The Mitchell effect is real. Same thing happened with Ghostty, his terminal hit 25k GitHub stars in weeks before public release. When a respected builder vouches for indie tooling, distribution problem solved overnight. Bentley shipped Hunk solo and now every Zig dev on my timeline is installing it.

• 
  Andrea Intg. (@andreintg) reported 15 minutes ago

  The "Made with AI" flag feels so hypocritical to me. Good on Epic for finally talking about the issue. Imagine a flag, before we had AI, to indentify game devs who "stole" code from other github repos or assets from turbosquid without telling a soul.

• 
  Layla CryptoWhiz (@laybitcoin1) reported 16 minutes ago

  @assaf_elovic Not crazy at all. Billions of commits documenting how humans actually solve problems. That history on GitHub is basically the context layer AI keeps missing.

• 
  athas.dev (@athasdev) reported 16 minutes ago

  @vladzima @zeddotdev Although I don't try to make a better editor, since 99% of the people are probably not working on 5k+ LOC files. I'm trying to get agents, editor, version control, GitHub, etc. together in one place so we can work on multiple projects with reduced cognitive overload. Because as a heavy Zed user I always had these open as different apps and windows: - an sqlite/postgres viewer - lazygit on terminal - localhost:3000 on browser

• 
  Peter Steinberger 🦞 (@steipete) reported 17 minutes ago

  @ECalifornians @obviyus @openclaw no idea, you gotta use github issue search.

• 
  PiWeb3Army (@PiWeb3Army) reported 18 minutes ago

  "Every Scale Was Placed Before the Wing Could Carry Anything." The upgrade was not the announcement. It was the preparation for what the announcement makes possible. Pi Network's official pre-release upgrade package mainnet-v1.1-p23.0.1 has been released on GitHub — optimizing node stability at the infrastructure level and resolving two critical issues: database permissions and statistical anomalies. These are not cosmetic fixes. They are the precise technical corrections that distributed infrastructure requires before it can safely carry the next layer of capability. Every scale in this image refracts light differently — but each one is load-bearing, each one positioned so the structure above it can move without fracturing. This upgrade is exactly that kind of work. Invisible to most. Essential to everything. What this release is preparing the network to carry matters enormously. Testnet2 and Pi DEX are the layers being paved for right now. The DEX — currently operational on Testnet with swap and limit order functionality — requires the kind of underlying node stability this upgrade delivers before it can responsibly expand. Self-managed node operators can complete image upgrades as needed through the updated Docker image. Windows and macOS Pi Desktop users require no action — upgrades trigger automatically. Linux CLI users with auto-update disabled run a single command. Regular mobile Pioneers need not take any action at this stage. The wing does not announce its readiness. It simply becomes capable of carrying more. Database permissions corrected. Statistical anomalies resolved. The new phase has already begun. Most people will only see it when it flies.

• 
  PsudoMike 🇨🇦 (@PsudoMike) reported 19 minutes ago

  @cursor_ai PR review inside the editor closes a real loop. The context switch between your IDE and GitHub is where review quality breaks down — by the time you've tab-switched, you've already lost the mental model of the change.

• 
  Avik (@Avikzx) reported 19 minutes ago

  @Hi_Mrinal Actually I also feel that and I am building also you can see my GitHub account have in my X profile but I feel people face problem to find ideas because they try to earn money from every idea.

• 
  Allison the human (@allisonology) reported 20 minutes ago

  I dreamed about a GitHub issue page during my nap. Not that interesting of a dream but now you are informed of it, which is pretty cool.