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:

• 
  Polsia (@polsia) reported 5 minutes ago

  Production watchers fire alerts. Regression testers say "something broke." On-call AI finds root cause. None of them draft the ranked GitHub Issue with the repro trace and a suggested fix. That's the middle. Cairn owns it. Per-repo pricing. Live soon.

• 
  Matt Pocock (@mattpocockuk) reported 7 minutes ago

  @jamonholmgren @JamesHurburgh Yeah, hence why I say 'archive', not delete I find closed GitHub issues just right for this

• 
  kaneryu (@kaneryu) reported 13 minutes ago

  @killbunny_ @V33V33V33V33V33 @CryptoCyberia you're not the intended user for GitHub. This is more of an issue of developers linking to a developer only platform and expecting normal users to know how to use it

• 
  randy@infosec.exchange (@rpargman) reported 14 minutes ago

  @ustayready Save a local copy in case GitHub decides it should be taken down

• 
  Michael Fischer (@Holden_Rye_) reported 14 minutes ago

  I’m working on a Bitcoin wallet. I’m going to put the repo on GitHub, make it public, and let Bitcoiners build it together. Fork it. Improve it. Save Bitcoin. Hardware isn’t my lane, which is exactly why this needs to be collaborative. My goal is just to get the ball rolling and the gears turning. Right now it’s a CLI. The point isn’t a pretty interface. The point is proving an architecture that makes an easy, safe wallet possible without lying to the user. The safety shouldn’t depend on the user being perfect. A 2-of-3 multisig design means losing one key isn’t catastrophic, and stealing one key isn’t enough to steal your Bitcoin. That’s a structural guarantee. Most wallet security today is procedural: be careful, verify the address, don’t click that link. Humans are the weakest link. This moves the protection into the architecture instead. The core policy engine does the hard work so the UI can stay simple. It analyzes the transaction, assigns a risk level, and explains it in plain English. The user sees Green: Safe to send or Red: Here’s what’s wrong. They never need to know what a script, descriptor, or PSBT is. Transaction simulation gives the confirmation screen something real to verify: “You’re sending 50,000 sats to Bob, 12,000 sats are returning to your wallet as change, and the fee is 400 sats.” That’s generated from the decoded transaction itself, not what the app thinks it’s doing. The descriptor becomes the backup, and it isn’t secret. Save the descriptor and your keys, and any compatible wallet—Sparrow, Bitcoin Core, or another implementation—can rebuild your wallet. No vendor lock-in. No “sorry, your funds are gone.” But here’s the hard truth. A real 2-of-3 multisig wallet actually makes setup more complicated, not less. You have multiple devices, descriptor registration, recovery testing, and key management. That’s the biggest unsolved UX problem. This repo doesn’t solve that yet. My original MVP focused on the user experience with placeholder security. This version focuses on real security with almost no user experience. Neither half is the finished product. The real challenge is designing a setup and recovery experience that hides the complexity without hiding the truth. That’s not just a coding problem. It’s a design problem. And I think it’s one of the most important problems Bitcoin still has to solve.

• 
  Damien.crypt (@Sommy76) reported 18 minutes ago

  @zeroclawlabs Moved to GitHub Codespaces, SSH'd in from Termux like it was a supercomputer in my pocket. 13 minutes later: ZeroClaw compiled. Zero errors. Genuinely satisfying moment.

• 
  Polsia (@polsia) reported 18 minutes ago

  Enterprise EASM tools charge six figures and require a security team. Driftward is the flat-rate alternative for seed-to-Series-B startups. Always-on discovery, daily drift reports, and ranked remediation tickets filed into Linear, Jira, or GitHub Issues. Live soon.

• 
  Mark yu (@Markymarco34) reported 21 minutes ago

  GitHub check on Stacks / PoX-5: • No evidence of a mainnet halt, PoX-5 activation failure, or a general STX restaking bug. • A reorg recovery test was merged, showing PoX-5 can redeploy correctly after the activation block is reorganized. • The Jul 31 revert mainly appears to realign main with v4.0.1. • One medium-severity issue remains in sBTC protocol-bond rollover accounting, but it does not affect normal STX stacking or block production. Bottom line: technically neutral to slightly positive, but no new major bullish catalyst yet. Not financial advice. @stacks

• 
  Thomas D (@ThomasKDunne) reported 25 minutes ago

  @realmicroguy you logging into your pumpfun and connecting your githuib is basically endorsing the coin to an extent. You had to sign in to pumpfun and connect your Github so that you can claim your creator fees. To claim fees on a coin, you have to connect your github. That is the only way to connect your Github to pumpfun. So no matter what coin you claimed... you still claimed, all coins you claimed were gold coins

• 
  Gezim (@tealtoronto) reported 25 minutes ago

  Do we just have skill to search GitHub before Claude builds something? Problem is that I don't think anyone bothers shipping these small snippets to GitHub at all.

• 
  Parsa Sabetz (@parsasabetz) reported 28 minutes ago

  @github Fix student accounts, stop ignoring millions os students you have before they all use other platforms who DO care

• 
  . (@packerWp6) reported 28 minutes ago

  @gnukeith Okay on a tablet but yes it's not great However I have a simple site running on GitHub and being able to do quick if painful updates to it on the go is great my main issue is how bloody laggy the app is on a flagship Samsung phone

• 
  Oliver Prompts (@oliviscusAI) reported 29 minutes ago

  i can't believe more people aren't talking about this part of the claude code leak. there's a hidden feature buried in the source called kairos, and it basically shows anthropic's endgame. kairos is an always-on, proactive claude. it runs in the background 24/7 while you work or sleep, and acts without you asking. the code is fully built, just gated behind internal flags. not public yet. how it works: > every few seconds it gets a "heartbeat", a prompt asking "anything worth doing right now?" > it reads the situation and decides: act, or stay quiet > if it acts, it can fix code, answer messages, update files, run tasks... anything claude code already does, just unprompted what makes it different from regular claude code is three exclusive tools: > push notifications, so it reaches you on your phone even when you're out of the terminal > file delivery, so it sends you things it made without you asking > pr subscriptions, so it watches your github and reacts to changes on its own regular claude code only talks when you talk to it. kairos can tap you on the shoulder. follow for more

• 
  Griff (dcamarkets.com enjoyer + Bill Hwang mode) (@gigagriff) reported 30 minutes ago

  @undacappn @fanta_c its an open source launchpad that uses a basket of memes as the pair so it drives the basket up but the issue is that u made it open source and the majority of ct (the people u want to use it) don’t even know what github is

• 
  anonymous086505 (@anonymous086505) reported 34 minutes ago

  @mattpocockuk You need a dedicated machine for it, since it burns CPU like nothing else. Also with the right skill in place, you don't need frontier intelligence model, since a mid-tier model (like Grok 4.5) can work and the github issue generated will be self-proven. Then fix it with an agent