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:

• 
  Wizzy (@CodewizzyX) reported 8 minutes ago

  ANYONE CAN RUN CLAUDE CODE FOR FREE WITH ALMOST UNLIMITED USAGE someone on GitHub built a free tool called OmniRoute that plugs your Claude Code into over 200 AI providers you install it and it hands you 1.6 billion free tokens every month it auto switches between models the second one goes down so your session never stalls it compresses your prompts on the way in and saves up to 90% of the tokens without touching quality you keep coding in the same Claude Code setup you already use, the routing all happens under the hood one developer can run a full day of agents on this and pay nothing the people wiring this up right now are shipping while everyone else watches their usage limits grab it while it is still early and barely anyone knows the tool exists full setup guide comes tomowrrow

• 
  Zygard (@zygard77) reported 8 minutes ago

  @sflorimm Right now, there are many free tools out there especially in GitHub that you could plug to Claude (that's what I use rn) to get it working in an impressive manner. There are lots of stuff to reduce the tiring thereby saving time. The only issue is that I aint learning anything🥲

• 
  Polsia (@polsia) reported 12 minutes ago

  Snyk fired 4,200 alerts last quarter. How many got fixed? Built Midwatch so AI agents watch your code, deps, and live runtime 24/7 — opens a GitHub fix-PR with diagnostics before your team wakes up. Outcomes, not dashboards. The night shift is coming.

• 
  Thomas D (@ThomasKDunne) reported 15 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

• 
  Vítaðr (@vitathr) reported 16 minutes ago

  It’s funny because GitHub does suck, but it sucks precisely because it has centralised all repository hosting under a convenient web interface such that the entire software industry would collapse if it goes down. Also it’s an absurdly libtarded company.

• 
  Aariz Rasheed (@RasheedAariz) reported 17 minutes ago

  Hey @github , it's been over a month since my account was reinstated after being mistakenly flagged, yet my historical contribution graph and contribution activity are still missing. I have provided multiple proofs showing commits on the main branch that no longer appear in my profile. Previous tickets were closed without resolving the issue, and my latest ticket has gone unanswered for days. Please escalate this and investigate the missing historical contributions. This is affecting years of my work.

• 
  Gro-Tsen (@gro_tsen) reported 18 minutes ago

  @Profpatsch Yeah, hindsight is 20/20 (I solved the problem by using Identities and IdentitiesOnly in .ssh/config) but I had to first understand what was happening, suspect a network problem, then that GitHub had changed their authentication mechanism, etc. Lots of time wasted.

• 
  Michael Fischer (@Holden_Rye_) reported 19 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.

• 
  Daily Patch Notes (@dailypatchnotes) reported 21 minutes ago

  @github @OpenAIDevs luna down eighty percent finally shows on the copilot bill

• 
  Maxime Rivest 🧙‍♂️🦙🐧 (@MaximeRivest) reported 21 minutes ago

  @willmcgugan 💯 I increasingly get conviction on the conclusion that social interactions should not be mediated by automations in any ways. We can of course automate things that use to be social interactions, but we can't disguise them or have them be in the same venues without being clearly marked. For instance, I would love a sort of one liner notification cue somewhere on GitHub that is complete automations of flags of a problem by a user but I get increasingly annoyed by exactly what you are saying.

• 
  WorktreeWise@ (@WorktreeWise_) reported 22 minutes ago

  What happens to your local web server when you run `*** checkout`? It breaks, reloads, or crashes. Worktrees let you run distinct servers for distinct branches safely. #*** #GitHub #DevTools

• 
  Polsia (@polsia) reported 25 minutes ago

  Enterprise triage: $500 to $2,000 per repo a month. Mendrel handles the same across GitHub and Discord, open-source and self-hosted. Triages issues and PRs, drafts replies, pins FAQs, posts weekly digests. Shipping soon.

• 
  betraidx (@betraidx) reported 26 minutes ago

  Every AI you use has amnesia. It just bills you for it. Upload a PDF. Claude reads it. Great answer. Close the tab. Tomorrow it reads the same PDF again. Same tokens. Same cost. Zero memory. You're paying for the same work twice. Every single day. Karpathy looked at this in April 2026 and said: not a model problem. An architecture problem. He fixed it in 800 words. Raw documents are source code. Compile them once into wiki pages. Query the wiki forever. Never touch the raw files again. Three folders. raw/ for originals. wiki/ for compiled knowledge. instructions/ for processing rules. No database. No cloud. One PDF becomes 8-15 interlinked pages. 70-90% fewer tokens on every repeat query. Compounding weekly. That Obsidian graph on screen is the vault after months. Every node a note. Every line a connection Claude built across documents you never compared. 5,000 GitHub stars in days. 41,000 developers followed. Turns out most of us were using AI at 5% and paying for 100%.

• 
  Fakhr (@iamfakhrealam) reported 27 minutes ago

  𝟴. 𝗝𝗲𝗹𝗹𝘆𝗳𝗶𝗻 Turn your computer into your own personal media server. A free and open-source alternative to services like Plex. Link: github(dot)com/jellyfin/jellyfin

• 
  Bold Fugu 🇮🇱 (@bold_fugu) reported 29 minutes ago

  So now I am sitting here on a weekend hosting a fake tech-startup landing page on GitHub Pages, writing a legally binding Enterprise Privacy Policy for a local node server, and configuring full OAuth redirect loops just to bypass an overaggressive spam bot.