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:

• 
  merlin (@merlinaudio_) reported 21 seconds ago

  @jarredsumner why not test if it *really would* close the github issues? surely claude can whip up a repro in 1.3.14 and then run it in the rust rewrite.

• 
  Ben Nichol (@MrBitterTV) reported 6 minutes ago

  Hi Boris, @bcherny reporting a frustrating issue. For weeks I’ve been building a bridge between Claude Code and the Claude app on my phone via a shared GitHub repo where Code pushes updates and summaries. The hope was to brainstorm on the road during drives. The problem: the app defaults to Haiku on voice despite showing Opus 4.7 Adaptive at the top. When I ask what model I’m using, it confirms Haiku. It’s obvious from the response quality too. Any ideas?

• 
  Manojava (@Avajonam) reported 10 minutes ago

  आपको पता है यदि USA, gitHub पर प्रेशर करके बस ये कह दे कि github service not available to non USA citizens or allied then within a few seconds 70% coding work of world will stop and 80% software will be down ... All mobile, all computers all suddenly collapse .. So much dependency on GitHub every software developer have .. But nothing will happen to China .. Don't be surprised , in 2013 , china put the foundation to cope up with such types of worst scenario cases and they developed their own "Gitee" fully funded by local government. और हम चले विश्व गुरु बनने ..

• 
  Kyle TechSquidTV (@TechSquidTV) reported 11 minutes ago

  I really hate that GitHub makes you login with SSO on SAML orgs, to just view a public page. Don't want to authenticate? You can see the same content via Incognito mode. Make that make sense

• 
  davidsong (@bitplane) reported 11 minutes ago

  @gonenb @oxcrowx linux pwned, macos pwned, windows pwned, github pwned, firefox pwned, tanstack pwned with malware targeting developer machines for a supply chain attack cascade. bots reading commit logs, chinese models doing pound shop mythos. 2026 will go down in history as the year everyone got hacked. secure your ****.

• 
  Sai Prakash (@SylonZero) reported 12 minutes ago

  April 2026: one crafted GitHub issue title → AI triage bot exfiltrates GITHUB_TOKEN → 4,000 developer machines compromised for 8 hours. No human approved a single step. EDR saw authorized calls from an approved process.

• 
  Sylvester Hesp (@oisyn) reported 15 minutes ago

  @HSVSphere Yes it is. There is no good reason that you can only use an usize, and index calculations are often based on signed ints. The only reason they don't implement Index with other ints is that it makes int literals ambiguous. There is a tracking issue on the rust-lang github for it.

• 
  MOSES ILUYEMI (@MOZAICTECK) reported 17 minutes ago

  Bug 4. Cookies refused to travel cross-domain. Login worked. But the chatbot kept blocking us. samesite=lax means cookies only travel within the same domain. Frontend on GitHub Pages. Backend on HuggingFace. Two different domains. Fix: Change samesite from lax to none.

• 
  Sakti Prasad Bagchi (@saktibagchi) reported 19 minutes ago

  4/ 3. Skip the LLM Completely (Best Choice) When you know exactly what to do → no agent needed. GitHub example: gh issue create --title "Fix bug" --body "Details..." Zero tokens. Lightning fast. 100% reliable.

• 
  Jose Enrique Hernandez (@_josehelps) reported 20 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.

• 
  colinhacks/zod (@colinhacks) reported 22 minutes ago

  @PawelJLisowski we're calling ourselves an "OSS CodeRabbit" when really the most interesting parts of Pullfrog are not review-related. it's basically a hackable platform that lets you trigger agent runs in response to arbitrary GitHub activity. being able to mention @ pullfrog anywhere to tweak a PR, open an issue, implement a feature—all things CodeRabbit doesn't do. focusing in on PR review: - price is the obvious one. I don't think per-seat billing makes any sense here. misaligns all the incentives—they're gonna try to use cheaper models to keep their costs down and margins high - running your code. they advertise things like "50+ linters and SAST tools" that are available to their agent. but only one matters—the one that's in your repo. because we're inside Actions we can just install your deps and run lints with your actual configs. - true model/provider agnosticism (you have control) - quality/ anecdotally there's no contest between a well-prompted Opus run vs CodeRabbit. candidly there's a way to go before we have true feature parity but for a typical reviewbot workflow Pullfrog is already very polished

• 
  Rahat Kabir (@rahat_neuron) reported 25 minutes ago

  @github down? i've been contributing and committing changes, but my GitHub activity graph isn't updating.

• 
  alkimiadev (@alkimiadev) reported 27 minutes ago

  @m13v_ @SocketSecurity I've switched to forking/vendoring libs I use. I saw some issues coming with github so I jumped ship before the recent mess and started self-hosting ***. The long term maintenance costs for maintaining well written libs is trending towards $0 with llms becoming more and more capable while the long term supply chain attack risk seems to be growing over time. Although that last part could just be recency bias since there have been several high profile incidents in recent times. Its kind of messy to determine it is a legitimate growing trend or a combination of a recent spike and the recency bias. That spike doesn't necessarily mean it actually is a growing threat. That said, I'm working under the "better safe than sorry" mindset and just forking/vendoring almost everything I use.

• 
  P! (@iPariola) reported 28 minutes ago

  i created this mess on Github myself and now i have to fix it 😔 need to set up a github rule for PRs

• 
  Terry (@trknhr) reported 32 minutes ago

  This TanStack npm compromise is scary. It does not look like a simple leaked npm token case, but a deeper supply-chain issue involving GitHub Actions, OIDC, and cache behavior. If you use @tanstack/*, check your lockfile and affected versions carefully.