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:

• 
  GooGZ AI (@PaulGugAI) reported 47 seconds 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 👇

• 
  Krastyo Krastev (@k_krastew) reported 2 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?

• 
  The Structural Architect ⚡ (@Coherent_Design) reported 5 minutes ago

  After digging way too deep into GitHub Copilot Pro vs Pro+: Pro+ does not appear to meaningfully solve the real pain point for heavy VS Code users: the short-term / session-level throttling where Copilot suddenly stops mid-task, truncates, or “continue” barely works. What it does seem to do: - more monthly premium requests - fuller model access - some evidence of slightly higher model-specific limits / priority What it does not seem to do: - eliminate mid-task stoppage - prevent active agent sessions from choking under load - turn Copilot into a no-throttle coding agent So the honest conclusion is: Pro+ raises the ceiling a bit, but it does not remove the wall. The best practical mitigations still look like: - Auto model selection - one agent at a time - use frontier models for hard reasoning, not long grind sessions - use base models for sustained editing Feels like the real problem is backend/service-level throttling, not the monthly quota. Anyone else seeing the same thing in VS Code?

• 
  Emsi (@emsi_kil3r) reported 6 minutes ago

  Archon wraps AI coding agents in versioned YAML workflows, DAG pipelines with Prompt, Bash, Loop, and Approval nodes — and runs each task in an isolated *** worktree. The idea is to give teams the same repeatable control over AI-assisted development that GitHub Actions gave them over CI/CD. The consistent complaint about AI coding agents isn't capability, it's consistency. Ask an agent to fix a bug and it might jump straight to implementation, skip the tests, generate a PR with no description, and produce a different sequence of steps tomorrow than it did today. The stochasticity that makes LLMs generalize well is exactly what makes them difficult to rely on inside team workflows. Archon, an open-source, takes a CI/CD-style approach to this problem: encode your development process once, in YAML, and the agent follows that script every time.

• 
  Emmanuel AO - The DevOps Fixer 🐧 (@emmanuelao_) reported 8 minutes ago

  Certificates don't make you an engineer. Shipping broken things and fixing them does. Your GitHub is a better CV than your Coursera.

• 
  WpWpN (@NastyShlob) reported 11 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.

• 
  The Rollup (@therollupco) reported 14 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.

• 
  Daniel (@ligth_daniel) reported 14 minutes ago

  @jaredpalmer @github @grok can you explain the goal of this feature? which problem does it solve ?

• 
  Gabriel Mičko (@gabriel_micko) reported 15 minutes ago

  @bcherny @zeeg In VSCode when I pull in a file I don’t want claude to read it. There are at least 3 issues about this on github. It is a security issue.

• 
  Steve McNiven-Scott (@stevemcniven) reported 16 minutes ago

  @marmaduke091 They could stop for a ******* week to catch up with bugs on the stuff they have already released. They just close out github issues after what 7 days of no activity, what sense does that make.

• 
  Dan Harrin 🦒 (@danjharrin) reported 17 minutes ago

  @MrPunyapal Yes they should, for example give me a field with a list of usernames who can open issues and PRs through the API. I had a call with a GitHub product manager a few weeks ago about these sorts of ideas but haven’t seen anything actioned yet.

• 
  starfish (@firefincher) reported 19 minutes ago

  @ziyasoltan devs waiting for such moment to push 2 million pull requests but github goes down 😭😭

• 
  Bas Fijneman (@bas_fijneman) reported 21 minutes ago

  @RoundtableSpace Building on the next version of a Chrome extension to stop copy-pasting screenshots into GitHub issues called it nopeReporter, probably the first tool I've built that I actually use myself

• 
  j⧉nus (@repligate) reported 22 minutes ago

  @NostaIgicGareth wallet cuz i dont even think its possible to login with github

• 
  Chris (@helloitschrisg) reported 22 minutes ago

  @trq212 working on claude code on my phone, to a github repo. After a certain amount of prompts and work i consistently get this error; API Error: Stream idle timeout - partial response received What is it? 😔