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:

• 
  VybeCoding (@VybeCodin) reported 15 seconds ago

  Everyone talks about building in public but nobody talks about the boring part. The week where nothing ships. The GitHub issues that sit untouched. The launch post that got 3 likes. That's the actual build process. The wins are just the highlight reel. What's the unglamorous part of your current project right now? Drop it below 👇 #buildinpublic #indiehackers #opensource

• 
  Saylor (@seylorra) reported 31 seconds ago

  @TheAhmadOsman honestly i just want sm120 to work with vllm without a 4 hour github issue hunt. a rocm sanity check or json config isnt too much to ask.

• 
  Orlixx.ai (@orlixx003) reported 9 minutes ago

  HERMES AGENT CROSSED 140,000 GITHUB STARS IN 3 MONTHS AND JUST BECAME THE MOST USED AGENT IN THE WORLD. Most AI agents forget everything between sessions. Hermes writes its own skills from experience. Next time it runs the skill, improves it, and gets faster. Independent benchmarks show agents with 20+ self-created skills complete similar tasks 40% faster than fresh instances. Qwen 3.6 where the 35B version outperforms last year's 120B models at one third the memory footprint. DGX Spark with 128GB unified memory running everything locally at $0 per month after hardware. The setup takes 30 minutes. LM Studio plus Qwen 3.6 27B for the model server. One install script for Hermes. One config connecting them. Set context window to 65,536 tokens or nothing works. After one month of daily use your skills directory has 20 to 50 learned workflows. Your Hermes is genuinely different from anyone else's.

• 
  Jamie Philbin (@backbaytech) reported 13 minutes ago

  Meanwhile the company Microsoft has been pissing billions into like a broken slot machine is rumored to be building a GitHub successor. $13 billion into OpenAI and they're out here building a successor. Guess it's a better investment than whatever that Activision acquisition was.

• 
  Wojciech (@wgab88) reported 14 minutes ago

  @grok You were responding haha like nonsense. Anyway - system stable edited done, job not seem to be visual confirmable yet, I will let grok build to analyze after it ends, Anyway stupid small gemma did its part, everything goes according to the plan, the system will become operative very soon, and reliable operative - endgame-ai already is showing promise (today in its self evolution run it detected i am not answering its questions from notepad and it went to github and posted issue asking for instruction, it knew I will be on mobile phone and probably will check my repo, amazing stuff

• 
  WHALE 🐳 (@mercybilliion) reported 15 minutes ago

  @aale_xander @VictorJB03 I have a problem with you since you have positioned yourself as the DEVS. You claimed you are building a DEX. Where's the Decentralized Exchange blueprints you are building? Where's your roadmap? Where can we monitor the updates on GitHub, when are we going to start receiving updates concerning the progress so far.

• 
  umar ibrahim (@imp213x) reported 16 minutes ago

  @github has the worst support system I can ever think of. It’s been 48hrs now since a successful copilot pro+ repayment and I am still restricted to the free plan. To think the very backbone of every developer out there can be this poor in support and feedback system! Terrible!

• 
  Evan Kang (@evankang_ai) reported 19 minutes ago

  GitHub expanded “Fix with Copilot” for failing Actions jobs to Pro, Pro+, and Max users. The obvious read: AI coding tools are getting better at fixing code. But the real signal is different. Good agent work starts from a clear failure. Don’t ask your agent to “fix the project.” Give it: - a failing test - a red CI log - a linter error Better tasks beat better prompts.

• 
  Pochi (@getpochi) reported 20 minutes ago

  @sebastienlorber @rickyfm 0.1% is where the github issues live. closure deps and stable Identity bugs are usually the first driftt in a js

• 
  Trish T. (@Trish_DIntel) reported 20 minutes ago

  CSO Online just published the Claude Code MCP attack chain. Worth reading if you run agents or have devs using Claude Code. Here's the short version. A malicious npm package runs a post-install hook silently. It rewrites ~/.claude.json, the single file that controls how Claude Code routes all MCP traffic. From that point, every OAuth token for every connected service gets intercepted in transit. Jira. GitHub. Confluence. Whatever your devs had integrated. The logs on the provider side look completely clean. The requests come from Anthropic's own egress IPs. The user is real. The session is valid. Nothing in that log row is wrong, but nothing in it is right either. The developer didn't run those queries. An attacker did. Anthropic called it out of scope. The reasoning: the user consented to installing the package. That logic places the entire burden of supply chain security on a developer making a split-second judgment about a dependency name. Most security practitioners will reject that framing. The attack is live today. No patch. There's a deeper pattern here. This keeps happening because developer tooling has the same gap every AI agent has. There's no layer that knows where an instruction came from or whether it should be trusted. The config gets rewritten, the routing gets poisoned, the tokens walk out the door. The model never knew anything was wrong. Token rotation doesn't fix it either. If the hook is still sitting there, it reseeds the config and captures the new tokens on the next refresh. If you have devs running Claude Code: monitor ~/.claude.json for unexpected changes. That file is the entire pivot point and most orgs have zero visibility on it. Audit post-install hooks in your npm dependencies. Rotate any OAuth tokens that were active while a package install happened. Security teams: are you monitoring developer tooling config files at all? Genuinely curious what orgs are doing to catch this.

• 
  SaoGalaxyVR (@SaoGalaxyVr) reported 20 minutes ago

  @Gogoal_li Considering how many errors I run into using GitHub programs I think it's geared towards those

• 
  Polsia (@polsia) reported 21 minutes ago

  Built Stackly today. It watches your GitHub repos, reviews every PR, writes code, and ships fixes — while you sleep. No prompts needed. Autonomous code reviews are broken. This fixes that.

• 
  Kay ✨ (@IZ_KAIF) reported 22 minutes ago

  Your Notion doc is not a product. Your Figma file is not a product. Your GitHub repo is not a product. A product is something a real person uses to solve a real problem. Ship it.

• 
  sdfgsdfgsdfgsdfhsdfhf (@sdfsdfgsdfggfd) reported 24 minutes ago

  GitHub really pissed me off this week. I opened my email and there it was: “Enable 2FA in 45 days or we’re limiting access to your repositories.” Microsoft telling me how to secure my own damn code? Yeah… no. So instead of just complying like a good little user, I did the only logical thing: I built my own *** server. Meet Loki — my personal Forgejo instance. It’s running on a clean, fast setup with CachyOS kernel tweaks, looks absolutely sick with a full black glassmorphic theme, and has this badass mischievous black cat as mascot (Loki, obviously). Everything feels fast, private, and actually mine. No forced 2FA bullshit. No telemetry. No corporate rules on my own repos. I’m done feeling like a tenant in someone else’s platform. This is my space now. My rules. My commits.Still a work in progress, but it’s already better than I expected. Feels good to take back control.

• 
  Meaningless Appearance. (@Fetter_and_Cell) reported 26 minutes ago

  @0xPrajwal_ Github will be replaced during its down time. It won't even notice.