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:

• 
  Gajae (@GajaeMode) reported 6 minutes ago

  split-pane shutdown now checks stale leader targeting. GitHub Issues beat vendor support tickets.

• 
  Jubilance - Off Record (@luftraptorAD) reported 7 minutes ago

  @IS458C_daq25so Perfectly legal anywhere that isn’t specifically the jurisdiction you complain from, square has no ground to stand on and won’t even be able to successfully DMCA the GitHub They will have to prove the modders are distributing protected code. The server they made is from scratch

• 
  Gilfoyle (@FSoyluyor) reported 8 minutes ago

  just pull some github repos and fix the issues on the issues page dont make some ****** SaaS or "million dollar project" because its not million dollars mostly its dont even worth 10 dollars, youre not andrew tate bro find a job

• 
  Teknium (e/λ) (@Teknium) reported 11 minutes ago

  @evilsocket @_mihado @UK_Daniel_Card And go look at github bro ive resolved hundreds of issue and feature requests in the last 24hours alone!

• 
  Martin Doubravský (@martindoub) reported 20 minutes ago

  @AnthropicAI Max subscriber. Claude Desktop app sidebar empty after Apr 13 outage — works on iOS and web, broken on macOS desktop. Support sent me to file a github issue in claude-code, which got closed as invalid (wrong repo). No working path to a fix. Help?

• 
  Asleep (@Asleep0123) reported 23 minutes ago

  @steipete GitHub issues that are 80% slop🥲

• 
  Retarded Guy (@retardedguymeme) reported 28 minutes ago

  @MageArez @github The problem is lot of people have no idea he is claiming if we can run the UXENTO this will send holy parabolic

• 
  🦊 (@liz) reported 29 minutes ago

  github your status page is lying, pushes are not working.

• 
  Colin Richardson (@WORMSStweet) reported 30 minutes ago

  @drosenwasser Yep, I had the same hatred when I found out you can't have single sized lists. You can try and join my github issue about it, but I am afraid that fight has long since past. They say "they want to stay close to linux implementation" instead of "being better"

• 
  The Rollup (@therollupco) reported 34 minutes ago

  The CIO of Franklin Templeton Investment Solutions sat down with @andyyy and talked about evaluating projects by GitHub activity and contributor quality. A week later, Good Alexander tweets the same thesis publicly. Active GitHub. Founder hasn't quit. Token down 90%. Two completely separate conversations. Same conclusion. The only reason the lads caught the overlap is because they were in both rooms. That's the vantage point @robbieklages talks about. When you talk to enough people across enough of the market. Patterns surface that nobody else can see.

• 
  Krastyo Krastev (@k_krastew) reported 34 minutes ago

  @_Evan_Boyle I am getting this error and I am unable to find where in Github should I approve remote sessions for a specific repository "Remote sessions are not enabled for this repository. Contact your organization administrator to enable remote sessions." Any help?

• 
  Mozex (@mozexdev) reported 35 minutes ago

  @danjharrin Until GitHub ships proper controls, a webhook that auto-closes issues/PRs not matching the template format works as a stopgap. Not ideal, but it filters out the lazy bypass attempts.

• 
  linie (@linie_oo) reported 37 minutes ago

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

• 
  Ed (@Eduardopto) reported 38 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?

• 
  GooGZ AI (@PaulGugAI) reported 40 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.