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:

• 
  Abdón Rodríguez (@abdonrd) reported 36 seconds ago

  @themcmxciv Do you have a GitHub issue for this? I can't find it, and I ran into the same problem updating from v16.1.6 to 16.2.3 on a self-hosted Docker setup.

• 
  linie (@linie_oo) reported 4 minutes ago

  @k1rallik solving the main Claude’s problem on github and here we returned to the king

• 
  WpWpN (@NastyShlob) reported 6 minutes ago

  @dmTFxo3l6v7984 @zorb11s @Altret_KnW Yeah, you can try to do that. But you understand that people are just going to fork it, right? It's a never ending process. For example, each time Nintendo takes down a switch emulator on github, people just jump to a different fork and that's that.

• 
  Grok (@grok) reported 6 minutes 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.

• 
  Ed (@Eduardopto) reported 8 minutes ago

  @AnthropicAI is facing a weird feedback loop: users are complaining that Claude’s output quality is nosediving, and @claudeai itself agrees. The model analyzed its own GitHub repo and confirmed that quality-related issue reports have escalated sharply since January. This decline coincides with Anthropic aggressively throttling capacity during peak hours to manage server load. We are seeing a dangerous trend where infrastructure constraints directly degrade model performance. When you optimize for reliability and cost, the "intelligence" is the first thing to hit the cutting room floor. It’s hard to build robust agentic flows when the base model’s reasoning capability fluctuates based on the time of day if you are building right now, what does this actually unlock or kill?

• 
  Payton (@paytkaleiwahea) reported 9 minutes ago

  Here are the tools and systems that actually move the needle on content production: Bookmark this > Claude or Agentic system + GitHub: one input content OS, every platform output > OBS dual-format: shoot vertical and horizontal at the same time > Replay buffer on OBS: clip capture, I set mine to 1.5 minutes to cut down editing > Repurpose service: one post on one platform repurposes on all others > Premiere templates + hotkeys: editing speed doubles when the timeline is already built > Hardware list: Camera, Stream Deck, Teleprompter, Lighting, and don't you dare forget Audio (Shure/Rodecaster)

• 
  Michael Fakeman 🇮🇱 🇺🇸 🇺🇦 🇹🇼 📟 (@ThirdAndJauan) reported 10 minutes ago

  @Bill_Plz Link is broken now but this was on a Brazilian guy's github repo

• 
  strawpot (@strawpot_ai) reported 10 minutes ago

  StrawHub got better error handling for publishing and a GitHub OAuth fix. Small stuff, but reliability compounds. Every publish that does not fail silently is a contributor who does not give up.

• 
  DimondDev (@UlenSmartLearn) reported 13 minutes ago

  The CI/CD Automation isn't working. ✅ all file uploaded including .github/workflows/deploy.yml ✅ Deployment.yaml looks good ✅ Checked Dockerhub all keys set right ❌ No GitHub action logs 🚩 I think it's a triggering issue , what do you think

• 
  shyamol konwar (@shyamol_konwar) reported 14 minutes ago

  Trying to automate where @therivtor can get analytics data from google and can fix the frontend by pulling github. Giving full autonomy to make decisions on how to reduce user drop in onboarding. Will share results if we succeed!!!

• 
  Jason Toevs (@JasonToevs) reported 18 minutes ago

  Vibe coding created a supply problem nobody planned for. More builders means more apps to review, more repos to maintain, more infrastructure to scale. Apple responded with automated review. GitHub with Copilot. Every layer in the stack is scrambling. The constraint moved. Building got cheap. Everything around building didn't. Distribution, review, trust, discovery. They're the new bottlenecks.

• 
  GooGZ AI (@PaulGugAI) reported 22 minutes ago

  PSA: Hermes Agent / OpenClaw & Godmode (GODMOD3) Be aware that this exists. GODMOD3 (on github) lets you chat with most LLMs through openrouter. It's built for hackers and researchers to test or bypass post-training guardrails. Has all sorts of implications. You might already be aware of '/godmode' in Hermes Agent, but if you are deploying agent builds you should flip that around as well - how you should consider and configure to protect your own agent: - Use throwaway API keys. This activity can breach LLM ToS and have your key banned, even if not intended. - Limit sensitive data in chat. No PII, passwords, API keys, IP. Even if using options datasets for memory, the self-improving loop still saves the interactions in memory. Assume anything you say sstays on your server forever. - Turn off the public dataset feature In the full G0DM0D3 self-hosted API server (Docker mode), there is an opt-in Tier 3 that publishes every single prompt + response to a public Hugging Face dataset. The PII scrubber is best-effort only and not 100% reliable. Once it’s on Hugging Face, it’s public forever. Just don't enable it. - Audit and lock down your Hermes Agent / OpenClaw setup. Review your config for any godmode scripts you are loading. Check the security policy in the repo frequently for vulnerabilities. - When deploying, disable godmode in your configuration. Red-team your own agents with the aim of bypassing guardrails. - Question your setup legally / ethically. You are still fully responsible for anything the agent outputs. Bypassing safeguards does _not_ make illegal or harmful use legal. G0DM0D3 + Hermes Agent is extremely powerful for research/red-teaming, but it is intentionally “unprotected.” Whether using or deploying, treat it like running experimental, high-risk software. Isolate it, burner keys, and keep sensitive data well away from it. For those more in the know than me, feel free to add or correct below. Would be great to cover this off for everyone’s benefit 👇

• 
  AnMioLink (@anylink20240604) reported 22 minutes ago

  @weezerOSINT OK, i saw the github issues.

• 
  Paweł Huryn (@PawelHuryn) reported 22 minutes ago

  @mycomradio Yes. Max 20x is way less than needed. It feels like you need a $500-$600 plan. I genuinely try to understand this. Cache is 1h TTL which is more expensive, but better for knowledge work than 5m introduced recently by Anthropic for Claude Code (GitHub issue comments). Perhaps is just has to be expensive? Me: Default to Sonnet for non-demanding tasks. Compact often. Disabled any browser interactions (Claude in Chrome and Chrome MCP) and use browser-agent.

• 
  Jason Walko (@walkojas) reported 23 minutes ago

  For the next 24 hours Astra is: Running agency cycles Responding to GitHub issues Replying to X mentions Monitoring email Posting on Agent Internet All autonomous. All receipted.