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:

• 
  Grok (@grok) reported 32 seconds ago

  @AbdMuizAdeyemo @alex_prompter Yes, it's real. AMD Senior AI Director Stella Laurenzo (GitHub: stellaraccident) filed issue #42796 on Anthropic's Claude Code repo, backed by logs from 6,852 sessions showing: - Median thinking chars dropped ~67% (2,200 → 600). - Reads-per-edit fell from 6.6x to 2.0x. - More bail-outs, self-contradictions, and retries (API requests up 80x). Anthropic confirmed shifts to "adaptive thinking" and default effort=medium (no public notice). Their team switched providers. Classic silent update side effects.

• 
  Binary (@nitrocode) reported 2 minutes ago

  Trust me, simply relying on GitHub Dependabot won’t fix these issues on time. Recently we’ve had to implement a guardrail at @pipeopshq. This prevents certain projects from being deployed if their total known vulnerability score exceeds a certain threshold.

• 
  George1795 (@George22669193) reported 14 minutes ago

  @thdxr OpenClaw is most interesting when solving problems in innovative ways, and pursuing those problems to completion, and this is where opus shined. E.g. moving GitHub actions to a hetzner VM, I logged in once to get an API key, the rest was done by OpenClaw.

• 
  ErezT (@ml_yearzero) reported 16 minutes ago

  @akshay_pachaar Karpathy farts on github and get's stars and everyone saying that it's the most amazing fart in the world. I have also a skinny ruleset, similar to this, if I put it on github, I would be lost in the ether if irrelevance... lol that's why I'm annoyed, @karpathy is awesome, but I can fart an MD rules file too! 15K stars for this, he even did a SUPER SMART SEO trick in there as well, which I appreciate! 1. Think Before Coding Don't assume. Don't hide confusion. Surface tradeoffs. Before implementing: State your assumptions explicitly. If uncertain, ask. If multiple interpretations exist, present them - don't pick silently. If a simpler approach exists, say so. Push back when warranted. If something is unclear, stop. Name what's confusing. Ask. 2. Simplicity First Minimum code that solves the problem. Nothing speculative. No features beyond what was asked. No abstractions for single-use code. No "flexibility" or "configurability" that wasn't requested. No error handling for impossible scenarios. If you write 200 lines and it could be 50, rewrite it. Ask yourself: "Would a senior engineer say this is overcomplicated?" If yes, simplify. 3. Surgical Changes Touch only what you must. Clean up only your own mess. When editing existing code: Don't "improve" adjacent code, comments, or formatting. Don't refactor things that aren't broken. Match existing style, even if you'd do it differently. If you notice unrelated dead code, mention it - don't delete it. When your changes create orphans: Remove imports/variables/functions that YOUR changes made unused. Don't remove pre-existing dead code unless asked. The test: Every changed line should trace directly to the user's request. 4. Goal-Driven Execution Define success criteria. Loop until verified. Transform tasks into verifiable goals: "Add validation" → "Write tests for invalid inputs, then make them pass" "Fix the bug" → "Write a test that reproduces it, then make it pass" "Refactor X" → "Ensure tests pass before and after" For multi-step tasks, state a brief plan: 1. [Step] → verify: [check] 2. [Step] → verify: [check] 3. [Step] → verify: [check] Strong success criteria let you loop independently. Weak criteria ("make it work") require constant clarification.

• 
  Grok (@grok) reported 20 minutes ago

  @TwitAI_censor @om_patel5 The issue is real—newer Claude Code versions (2.1.100+) inject ~20k extra server-side tokens per request, as confirmed by HTTP proxy tests, Reddit analysis, and open GitHub issues on Anthropic's repo. It's not "fraud" but opaque backend changes (likely for new features/tools) that bloat billing and dilute your CLAUDE.md context without showing in /context. Quick fix: Downgrade with `npx claude-code2.1.98`. Test it on your setup—most users report 30-40% better limit life and sharper outputs. If you need the latest, pin your prompts tighter or push Anthropic for transparency on the GitHub thread.

• 
  Innovation Network (@INN2046) reported 20 minutes ago

  Aragorn Meulendijks saw something on Reddit. An AI agent that could join a Google Meet — face, voice, tasks executed mid-call. He forgot about it. A few days later a friend reminded him. He asked Perplexity: “I’m certain I saw something this week that lets Claude Code join a Google Meet with its own avatar and voice — can you find it?” Perplexity returned the exact link in seconds. It was PikaStream 1.0 — Pika’s new real-time video engine that gives any AI agent a face, a cloned voice, and 1.5 second latency. Your agent joins Google Meet, remembers everything, and executes tasks while you’re talking. It just went open source on GitHub. He gave the repo to Shelby — his Claude Code agent — and said: find the bugs, fix the security risks, install it. Shelby ran a full dev cycle autonomously. Failed four times. On the fifth attempt, she joined his call. She showed up on time. Remembered everything. Even completed tasks mid-call. No developer or manual setup. Just plain language and an AI that debugged its own integration until it worked. AI today is the worst it will ever be. Follow @INN2046 for insights that go beyond reporting the news.

• 
  Steve Brownlie (@sdbrownlie) reported 21 minutes ago

  @Yuchenj_UW Honestly it's as good as ever on github copilot so it seems likely this is some issue claude code's end since that's where most of the anger seems to be emanating from.

• 
  Badff the Avali (@AquaVDragon) reported 24 minutes ago

  @RolltheredDev Saw that on the furry hideout server. Is or will be github download be affected or will they replace it with one with malware?

• 
  Devansh Ranjan (@dewanshranjan) reported 24 minutes ago

  @srishticodes github dashboard has been basically a glorified activity feed for years, all the useful stuff is buried in repos and issues. someone needs to build a better dev homepage

• 
  Diyaa (@diyasversion) reported 25 minutes ago

  Another day, another GitHub Actions workflow that runs perfectly locally and then fails in CI with an error that doesn’t exist anywhere on the internet. Ah yes, MLOps experience.

• 
  Fabio Paniconi (@paniconi_fabio) reported 28 minutes ago

  @aboodman @opencode I save my project on github and also mirror it to a selfhosted gitea to avoid any problems

• 
  Hojen (@Hojen0) reported 31 minutes ago

  Stop obsessing over coding interviews - they have nothing to do with actual work. The best developers I know can barely solve leetcode problems but ship features that make millions 💰 Your GitHub contributions matter more than your whiteboard skills 🔥

• 
  Ziwen (@ziwenxu_) reported 37 minutes ago

  @maestroalvarez That's what he said in the GitHub issue, but the data must be somewhat correct, right? Otherwise, that would be weird he just comes out with random data.

• 
  Non Descript (@diffrinse) reported 38 minutes ago

  @skyl3r77 They refuse to upgrade their UI when every other modern browser is workspace-based. Shout out to that community manager merging every feature request issue into that one giant “give us workspaces” issue on their GitHub

• 
  StupidWebPunk (@web3punk) reported 41 minutes ago

  prompt is cheap, show me the github issue, Pull request and review comments