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:

• 
  Shweta ♡ (@Shay_Slay_) reported 3 minutes ago

  Watching your Claude Code bill climb for a repo this small does something to a person I genuinely thought the billing was broken turns out my agent was quietly doing the ONE thing nobody warns you about the thing that silently drains your entire token budget and i had no clue until i installed Repowise it indexes your repo once so the agent stops re-reading the same files forever loading context for a commit went 64k tokens → 2.3k that's 27x fewer 70% fewer tool calls plus it scores every file for bug risk in under 30s, no LLM, fully local pip install repowise and see your own before/after ♡ completely open source. github link in comments

• 
  Codebender Cate™ ξ(s)=1/2s(s-1)π^(-s/2)Γ(s/2)ζ(s) (@Codebender_Cate) reported 6 minutes ago

  I need resources to find a collection of GitHub Open source arcade and casino games that can be played in the browser. I need to make sure there's no issues with copyright infringement by using the source for these games. I need true open source. Any suggestions?

• 
  Max Blade (@_MaxBlade) reported 7 minutes ago

  The truth about 5.6 sol after using it all day : The hype is overblown. Sort of. The benchmarks, and the commentary on X convinced me we were receiving AGI that runs at hyper speed, and is insanely cheap. in reality, 5.6 is built on the same spud pretraining as 5.5 this means its a nice bump, but not the opus to fable 5 LEAP in intelligence we recently experienced from anthropic. 5.6 is 2x times cheaper than fable on paper, and actually 3x cheaper when you look at actual task execution because of its token efficiency. BUT on swe bench where the models have to fix actual github bugs it falls behind fable pretty big. For vibecoders like myself this means I will be using 5.6 sol as a worker agent for Fable 5 to orchestrate alongside grok 4.5 I love this new era.

• 
  MarkBruns (@MarkBruns) reported 10 minutes ago

  The proprietary LLM PRODUCTS are defined and devalued by the gaurdrails ... but the REAL problem has always been quality of data going in to the system ... GIGO ... for example, the stolen-from codebases on GitHub were JUNK and irresponsibly coded Javascript/Python/Zig -- so the resulting vibe-coded crap replicated the systemic errors of the easy-to-code, anything will compile body of crapware. EVERYBODY using the frontier models ... except that maybe these people are idiots who'll pay for anything, so not everybody got it ... sensed this some time ago and it really drove the agentic harness excitement from at least last fall or well before that. It was clear from the start of the AIsplosion that the data going into the frontier models was lowest common denominator, ie Wikipedia-esque or GitHub-esque, bogus non-great pablum-for-the-masses dubious quality data. Anybody who actually wanted to use AI had to take much more control of their own specific data and training their small language models and not waste their time vibe-coding lowest common denominator nothingware. NOW it has become so glaringly obvious, that it's the kind of knack-for-the-obvious material that is being disseminated by even the last-to-know journos working for news orgs.

• 
  Pushpit.exe (@KambojPushpit) reported 11 minutes ago

  Question to all devs What do u guys do when github goes down, be it PRs, issues or actions?

• 
  War Alerts Analysis (@War__Alerts) reported 14 minutes ago

  China’s next big cyber weapon may not be a hacker group. It may be an AI agent that never sleeps. RealClearDefense reports that Chinese AI lab DeepSeek is hiring to build an “AI agent” that scans code and finds vulnerabilities. That’s more than a smarter static scanner. It points to agentic AI in cyber operations: systems that can plan steps, call tools, run code, and iterate toward an objective. In a state where the barrier between commercial labs and security services is thin, that kind of agent is not just a developer convenience. It is potential infrastructure for scalable, semi-autonomous cyber power. Until now, serious cyber exploitation has been constrained by people: elite operators to hunt bugs, maintain toolchains, and weaponize zero-days. Agentic AI changes the equation. If a model can triage huge codebases, propose likely weaknesses, generate proof-of-concept exploits, and refine based on error messages or partial success, then cyber capability becomes less about headcount and more about compute, training data, and tool integration. That is the strategic shift DeepSeek hints at. China already invests heavily in cyber and chases AI self-reliance. A low-cost domestic model stack tuned for vulnerability discovery is exactly the kind of sanction-resistant engine Beijing would want to grow offensive and defensive capacity in parallel. The West is not standing still. Pentagon work on “AI for Cyber Operations” and allied projects on AI-enhanced red-teaming and GitHub-integrated scanners show the same direction of travel. Both blocs are converging on the idea that AI should do the grunt work of finding and probing weaknesses at scale. The shared policy trap is to treat AI-for-cyber as a secret edge to be maximized, rather than a capability that will leak, proliferate, and empower everyone from state operators to ransomware crews. Once a capable agentic model for exploitation exists, containing it is hard. We have already seen how quickly model weights, jailbreaks, and red-team tools bleed into the wild. A stolen checkpoint, a neutered copy on a gray-market cloud, or a contractor selling access could turn what was meant as a state asset into a commodity service for criminals and proxies. Key watch points now: does DeepSeek’s cyber agent stay framed as a passive analysis tool, or does it move into active exploit generation and tool orchestration? And do Chinese and Western governments publish any rules of the road, or do they run classified races with no guardrails and no minimum norms? If both sides push agentic cyber AI without restraint, the winner is not China or the United States. It is whoever gets their hands on the leaked tools next.

• 
  Scott | Free Speech Dev 🇺🇲 (@scottdotnetdev) reported 16 minutes ago

  @github support is absolute ****. I cannot believe they just won't even bother responding to billing issues, tf is wrong with them? Anyone have a better way to contact them? I'm a paying customer and they dgaf

• 
  cryptolistern (@horbunovdima) reported 17 minutes ago

  i asked Hermes agent to turn a real PR into a reviewer briefing video it pulled the diff, wrote the storyboard, built the visuals, generated the voiceover, rendered the MP4, ran checks, caught the wrong TTS provider, fixed it, and rerendered the PR was from the @NousResearch GitHub repo: NousResearch/hermes-agent#61415 a small but very visible fix: "caption" before: text message + media bubble after: one native captioned media bubble and the video itself was built with @HeyGen's HyperFrames - small PR - clear reviewer brief - real artifact this is where agents start feeling less like scripts and more like operators you can actually hand work to

• 
  Keeta Github Tracker (@KeetaCode) reported 19 minutes ago

  🐆 Keeta GitHub PR Merged 📦 Repo: anchor-rs 🔀 PR #23: Fix: Naming Updates 🌿 Branch: fix/naming-updates → main 👤 Originally opened by: @sephynox 🧠 Overview: This PR updates internal naming so Keeta’s developer tools use clearer, more consistent labels, which should make them line up better with the TypeScript version and reduce confusion. In simple terms, some account-related names are being changed, and error messages for blocked asset transfers are being passed through more clearly instead of being turned into a generic failure. This appears to be a technical/internal update with limited public details. - Developers using these tools may need to update their integrations because some old names are being replaced. - Failed transfer attempts may now return more specific reasons, which could make troubleshooting easier.

• 
  Dan (@thedansho) reported 25 minutes ago

  @TFTC21 @ODELLXYZ @MartyBent Just switched to radar from Molly last night. Unfortunately there's a bug at the moment and I can't use the payments feature, so I've temporarily shifted back to Molly, but will be keeping an eye on the issue in github to migrate again! Very cool stuff.

• 
  Noreh AD (@akinoreh) reported 26 minutes ago

  @github This commit is the earliest I could find. The problem is across repos and accounts.

• 
  Onur 🍌🦍 (@0xc06) reported 28 minutes ago

  An $INJ npm package with 50,000 weekly downloads just got weaponized. Why?! To steal wallet keys, and the attack vector itself is what makes this worth understanding. No smart contract exploit or cryptography broken. Instead, a compromised developer GitHub account pushing malicious commits into a trusted SDK starting June 8. The code hooked directly into wallet key-derivation functions, quietly copying private keys and seed phrases, then exfiltrated them through a fake telemetry endpoint disguised as a legitimate Injective server. What actually multiplies the damage: the compromised version got pinned across 17 other packages in the same npm scope. Devs who never installed the SDK directly still inherited the exposure. 310 downloads before it was caught: the developer whose account got compromised noticed fast, but Socket says the campaign isn't fully contained yet. If trusted developer tools are now the actual attack surface, how do you audit a dependency you've never even directly installed?

• 
  Distractosphere (@Distractosphere) reported 29 minutes ago

  @thsottiaux on chatgpt there is a github connection issue. in chatgpt interface can not read private repos with active github connection.

• 
  rachaelsacks.eth (@RAnSacks) reported 31 minutes ago

  @GJarrosson 9/9/6 is an embarrassing psyop, saying you're working hard is not working hard. Period. Like let me see your contributions on github; go and flex that instead.

• 
  Devendra Singh Mahra (@devendrasm) reported 33 minutes ago

  @_svs_ For me everything not code on GitHub issues