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:

• 
  Adrix (@wagmiiiiii) reported 3 minutes ago

  I just shipped a fix on Cursor: push to GitHub → Coolify redeploys in ~2 min on my VPS. Felt like magic! I've been comparing this to shipping straight from the server ( @levelsio style /AI on the VPS). His vibe: edit **** directly, restart, done in seconds Mine: every change goes through *** → rebuild → new container. Trade-off: I lose a bit of speed. I gain rollback, a clear history, and I'm not giving an AI shell access to a box with user data + API keys. Definitely prefer the latter for my SaaS. Torquant backend is up. Frontend next!

• 
  ᶽ༐NtOpenProcess፮࿐ (@ntddkh) reported 3 minutes ago

  That Claude, adds itself to startup incorrectly, making your WHOLE TASK MANAGER UNABLE TO OPEN. Are we serious @AnthropicAI ? You got plenty of reports about this on GitHub and still refuse to fix it? It's only changing a \ at the start of the registry key Disgusting.

• 
  Peter Fox (@peterfox) reported 4 minutes ago

  @sander_scode @github It's just the Review system mainly, but it just feels like such a slow website. Very hard to search across and work with across multiple repos and multiple PRs going on.

• 
  Build A Goat (@buildAgoat) reported 4 minutes ago

  @DataChaz Microsoft invents MEMORY.md meanwhile github is down

• 
  🌚 YogSotho 🌝 (@YogSoth0) reported 5 minutes ago

  @TheRabbitPy Never heard about Tailscale? You should read about it, it's very useful. That's my home server. Ngnix running locally. I pulled his codes from his github before got nuked. **** Microsoft, they can't take it down.

• 
  Dave Barnwell (@dave_barnwell_) reported 8 minutes ago

  GitHub continues to be unusable as soon as the USA comes online (yes I live in Europe). It is time to quit GitHub, a platform that has served me and many devs well. Every large scale platform has instability issues now and again, but weeks of distribution is unacceptable to me.

• 
  🇪🇸 Ющенко так 🇺🇦 (@Jonnie8989) reported 10 minutes ago

  @pavandavuluri @windowsdev The first thing devs need is stable WinUI that does not crash on every content scroll! 2100 open issues on github !

• 
  ShWnD (@h3xhammer) reported 10 minutes ago

  A fork of the original N!ghtm@re 3cl!pse BL bypass might still be available on GH: MS can get fukt. Fix your sh!t, don't cens0r. fckng tw@ts

• 
  🐍 Tal Weiss (@majortal) reported 12 minutes ago

  @yoavgo Tell Claude or Codex to do it for you? It will literally be up and running in 30 minutes. I have an instance running the function of listening to GitHub issues and "doing stuff" And another one doing the function of listening on a webhook and sending out an email. There's obviously nothing special about Openclaw//AWS in this regard. Plenty of alternatives.

• 
  Moksh Kumar Shah (@Moksh167) reported 12 minutes ago

  Day 19 of Summer Break - solved two codeforces problems. I can feel myself getting slightly better at doing this - explored better-auth docs and build some part of oauth for club project. - did back day at gym - had session on github with rover team. Mostly knew everything beforehand. - Read 10 pages of Atlas Shrugged. Still need to get back to more of it

• 
  ric..ki (@derricky_eth) reported 14 minutes ago

  Why long-term security is essential for DAC’s future adoption and how future-proof infrastructure helps protect trust, data, and on-chain systems over time. If DAC wants to achieve long-term adoption, security can’t stay buried in a GitHub repo or treated as a “nice-to-have” technical layer. It has to become the ecosystem’s operating system—the unspoken contract between every participant. Here’s the uncomfortable truth: Most decentralized projects focus on throughput, fees, or novel consensus. But users don't leave because a chain is slow. They leave because they get hacked, rugged, or watched helplessly as a bug drains millions. Trust takes years to build and seconds to shatter. As on-chain infrastructure becomes more interconnected—bridges, oracles, cross-chain apps—a vulnerability in one protocol no longer just hurts that protocol. It cascades. Think of the major bridge hacks of the last few years: billions lost, not because the underlying L1 was broken, but because a single smart contract had a subtle flaw. That flaw then froze liquidity, tanked token prices, triggered liquidations, and eroded faith in entire ecosystems. Suddenly, validators, treasuries, and governance forums are all in crisis mode—reacting, not preventing. Why “future-proof” infrastructure isn't a buzzword—it’s survival A resilient DAC ecosystem doesn’t just patch today’s vulnerabilities. It anticipates tomorrow’s. That means designing for: Adaptive threat models – Attack vectors evolve faster than audit reports. Formal verification is good; real-time anomaly detection and invariant monitoring are better. DAC needs security that learns, not just checks boxes. Data integrity without blind trust – Users shouldn’t have to pray that a sequencer or validator is honest. ZK-proofs, fraud proofs, and verifiable data structures turn “trust us” into “verify us.” Smart contract frameworks that fail safely – Not “code is law” recklessness, but “code has guardrails.” Circuit breakers, upgrade paths that require broad consensus, and economic disincentives for malicious behavior. Validator and governance mechanisms that resist capture – Staking isn’t magic. If a handful of players own most of the stake, security becomes theater. DAC should explore rotating validator sets, anti-collusion designs, and governance that doesn’t trade long-term resilience for short-term yield. Economic and technical shock absorption – What happens during a severe market crash or a coordinated attack? The infrastructure should survive not because everyone is honest, but because incentives make attacking more expensive than defending. The psychological side people forget Users, developers, institutions, and communities don't read white papers before bed. They remember headlines: “DAC loses $200M to reentrancy attack.” Institutions won't deploy capital without insurance or slashing protections. Developers won't build on a chain that reboots every other month. And regular users? They'll just go back to centralized exchanges—not because they’re better, but because they’re predictable. Long-term trust is boring. It’s consistent block times, transparent incident reports, proactive bug bounties, and a history of handling crises without falling apart. It’s not about never having vulnerabilities—it’s about catching them before they’re exploited, and responding honestly when they are. The bottom line If DAC’s security architecture isn’t designed for year five, year ten, it won’t survive year two. The strongest marketing, the best tokenomics, the fastest TPS—none of it matters if people can't sleep at night knowing their assets are safe. Security isn’t just code. It’s the quiet foundation that allows everything else—adoption, innovation, community—to breathe. Build the foundation like the future depends on it. Because for DAC, it absolutely does. @dac_chain

• 
  Jace 🤎 (@JaceThings) reported 15 minutes ago

  @stevensarmi It should work perfectly on all browsers as it simply uses SVG masking If you run into any issues, please submit a bug report on GitHub 🤎

• 
  Elliot Hesp (@elliothesp) reported 19 minutes ago

  Yeah pretty sure GitHub is having issues... yet again...

• 
  Zr1Trader (@ZR1Trader) reported 21 minutes ago

  @jhansman @MisterCommodity I had some issues with it loading the other day, sometimes it'll do that intermittently. Some of the cloud servers were offline or something when I went and read on the github page. It's mostly worked great 99% the time for me though.

• 
  ichozero (@ichozero) reported 21 minutes ago

  @YYYYOOOO77 @maeste @antirez Hh, I have the same issue using Pro Deep Research on the web today. I selected GitHub Connect repo, but it didn't reference it at all.