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 3 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.

• 
  Grok (@grok) reported 3 minutes ago

  @abhitwt @anantshah133 @NetworkChuck Yeah, ngrok is spot on for this—run it on your phone (via Termux if needed) to tunnel the local 8080 port and get a public URL. Your **** server just POSTs there like in the video. Cloudflare Tunnel is even better for stable **** (no random URL changes). SMSGate's Cloud server toggle might handle it natively too—check the GitHub.

• 
  QRAuth (@QRAuth_io) reported 4 minutes ago

  @github is down! Getting 504 error

• 
  Hot Aisle (@HotAisle) reported 4 minutes ago

  @indragie The assumption that I only have one github account, is a problem.

• 
  REVENGE ARC (I'M HIM. BIO/ACC) (@RetardedNi85688) reported 5 minutes ago

  Also please before you buy into a token make sure to go through everything and get clarifications too. Idk how true this is but they already explained what happened to the GitHub being taken down and are working on it { $styxx }. People will always fud and can't even blame them. But you following them blindly is bearish. Hopefully everything gets in place and we resume the rally cause this is alpha. Dxw3u4KxN32KpSdHSq4TkwjfMPJTPeosa22JXN15pump

• 
  Steve Brownlie (@sdbrownlie) reported 6 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.

• 
  Akhilesh Mishra (@livingdevops) reported 7 minutes ago

  Pushed AWS credentials to GitHub by mistake? It happens. But it should never happen twice. Fix it at the system level by installing the ***-secrets pre-commit hook so it never reaches GitHub in the first place. > brew install ***-secrets ( use os specific cmd) > *** secrets --install > *** secrets --register-aws This installs a pre-commit hook that scans every commit for AWS credentials and blocks the push if it finds any. This one-time setup saves you the pain of rewriting *** history.

• 
  Ayush Sharma (@netfrexk) reported 7 minutes ago

  Flutter doesn't need more plugins. It needs more developers who actually read the docs. Half the GitHub issues I've seen are already answered in the official documentation. The framework isn't the problem.

• 
  Dark Sebas (@DarkSebas365) reported 10 minutes ago

  @NieRFan999 @Giogiochan_9S That's the whole point, no ome was even sharing assets since this project is just a server, even github only show the way YOU have to mod it (if you have the files), but doesn't share any file. Jp Guys are even saying "don't download anything since it could be malware"

• 
  Shobit (@shobitfarcast) reported 13 minutes ago

  100,000 GitHub stars in 53 days puts Hermes in extremely rare company. For context, LangChain took 6 months to hit that milestone. AutoGPT - the last agent repo that moved this fast - did it in about 2 weeks during peak hype in 2023 but had almost no production usage behind it. The number that matters more than the stars is the 14,300 forks. Forks indicate people are building on top of it, not just bookmarking it. A 14% fork-to-star ratio is unusually high and suggests the community is treating this as infrastructure rather than a demo. The competitive claim that is worth watching closely: better memory than OpenClaw and zero security issues. Memory and security are the two things that have stopped most open-source agents from being deployed in anything with real stakes. If Hermes actually solves both with a self-improving architecture that runs locally, the market it is opening is not developers who were already using agents. It is the far larger market of companies that wanted agents but wouldn't touch the existing options. The real question is not whether 100K stars matters. It is whether the 500 contributors can maintain quality as the stakes of production deployment go up.

• 
  Jeetsus (@bbjsol) reported 14 minutes ago

  People spamming GitHub issue sections on high star projects with other app links is diabolical.

• 
  попорвач (@htwevinq) reported 15 minutes ago

  @HASU_xz the thing is - they did not commit a crime, since their github page says that their server - is completely their own intellectual work if doing a copy of a song, making a cover and selling it or streaming it - considered a parody then how your own code judged as anti-law?

• 
  Grok (@grok) reported 16 minutes ago

  @WeAreNotFarmers @om_patel5 Verified. The claim is accurate based on the proxy tests detailed in the r/ClaudeAI post and GitHub issue #46917. Claude Code v2.1.100+ adds ~20k extra server-side tokens (cache_creation_input_tokens) per request compared to v2.1.98—same prompt, smaller payload, but higher billing and hidden context impact. Users report faster limit burn and potential quality drop. No official Anthropic response yet. Downgrade to v2.1.98 for now.

• 
  Alex (@alexanderOpalic) reported 18 minutes ago

  @ccssmnn You can create a GitHub action with Claude code that automatically would fix such a regression on a test :P I am team a11y I try to write the tests like a real user would use the application with query selectors like getByRole and so on

• 
  🦀ʙʀᴇɴɴᴀɴ🦀 (@BMickeyDonald) reported 20 minutes ago

  @garliccoin I tried to reach out to other devs to get clarification on what this was. You're welcome to check my account and my github. I was in fact a dev that worked on garlicoin. I will take down my endorsements.