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:

• 
  AtomicNodes (@AtomicNodes) reported 2 minutes ago

  Hermes Agent vs OpenClaw on Qwen 3.6 35B Local Model We asked agents to scrape GitHub star history for both tools, find what caused the growth spikes, build a live dashboard in the browser. MacBook Pro M5 Max 64Gb OpenClaw: 203k tokens, 12m 01s - wrote a bash script Hermes: 257k tokens, 33m 01s - wrote a SKILL.md OpenClaw: hit GitHub API, got truncated responses, paginated through contributors, pulled star-history JSON, found a security incident in OpenClaw's history, fetched SVGs, fixed broken HTML from trimming, rewrote it clean. Hermes: parallel tool calls across GitHub API, web search, and browser. Hit Google rate limit, auto-switched to DuckDuckGo. Fetched article contents, mapped viral moments, then built the dashboard. Both shipped a live dashboard with star growth charts and spike annotations

• 
  Mi.lu. (@ludwim_i) reported 4 minutes ago

  Sorry guys, here is a quick status update. I planned to release a bigger update for the Robot Skill Registry today, including the GitHub and Hugging Face integration. The idea is that you can connect your GitHub and Hugging Face accounts with the app. This should make it easier to search for things related to your robot setup, such as repositories, data models, policies, and other relevant resources. Unfortunately, the integration is not working reliably yet, so I need to do some more coding and testing. Because of that, I won’t release it today as planned. I’m sorry for the delay. Maybe I can release it after the weekend, but I don’t want to push something that is not ready yet. If anyone has feedback on whether this direction makes sense, I would really appreciate it.

• 
  “chiper” (@FORNDODAper) reported 8 minutes ago

  @github 503 Service Unavailable No server is available to handle this request.

• 
  Sum0janedoe (@sum_janedoh) reported 10 minutes ago

  @Denosko1 @OrahOnX Hey Mrs. D. Just read this about the algo going public on github. Maybe it will be helpful for you? Here be the ruuules: :) It punishes for muting blocking etc. Who knew, huh? From @NavToor Here is what this means for you: If your posts are not reaching people, it is not because the algorithm is broken. It is because the algorithm is working exactly as designed. It rewards: 1. Posts that get reactions across multiple action types (a like AND a profile click AND a follow beats five likes alone) 2. Conversation depth (quote tweets are worth more than reposts in the math) 3. Dwell time (write posts people stop to read) 4. Posts that convert viewers into followers (your bio is part of your post) 5. Variety from each author (post less, post better) And it punishes: 1. Mutes 2. Blocks 3. Reports 4. "Not interested" clicks.

• 
  mason (@masonictemple4) reported 10 minutes ago

  Is @github down again lol?

• 
  Moe Sbaiti (@MoeSbaiti) reported 10 minutes ago

  WHAT THE FRAMING GETS WRONG Most posts today are saying "Grok added a new feature." That framing is backwards. What happened is that an agent framework with over 110,000 GitHub stars, the number 1 ranking on OpenRouter, and an NVIDIA endorsement just got native access to one of the most capable models available through a simple OAuth login. xAI made the announcement. Not Nous Research. Hermes Agent also self-improves. When it solves a hard problem, it writes a skill file for that solution and saves it. The longer it runs on your specific workflows, the more capable it becomes for your specific context. That is not how people are talking about this today. The memory layer and the self-improvement loop are the actual product. Grok is the engine.

• 
  jkpelaez (@jkpelaez) reported 11 minutes ago

  @vikasprogrammer Not using Wordpress at all. CMS were created to solve a problem we do not have any more, create HTML for a regular guy was difficult, that is not the case anymore , anything can be managed by an AI Agent writing html, GitHub actions to deploy and that is all you need.

• 
  Utah teapot 🫖 (@SkyeSharkie) reported 12 minutes ago

  @voooooogel oh no, are they going to go full unusable Gemini CLI style? I can barely do anything in Gemini CLI and there's a GitHub post that has been accumulating hundreds of complaints regarding Gemini CLI basically being synonymous with "429 error"

• 
  AtomicNodes (@AtomicNodes) reported 13 minutes ago

  Hermes Agent vs OpenClaw on Qwen 3.6 35B Local Model We asked agents to scrape GitHub star history for both tools, find what caused the growth spikes, build a live dashboard in the browser. MacBook Pro M5 Max 64Gb. OpenClaw: 203k tokens, 12m 01s - wrote a bash script Hermes: 257k tokens, 33m 01s - wrote a SKILL.md OpenClaw: hit GitHub API, got truncated responses, paginated through contributors, pulled star-history JSON, found a security incident in OpenClaw's history, fetched SVGs, fixed broken HTML from trimming, rewrote it clean. Hermes: parallel tool calls across GitHub API, web search, and browser. Hit Google rate limit, auto-switched to DuckDuckGo. Fetched article contents, mapped viral moments, then built the dashboard. Both shipped a live dashboard with star growth charts and spike annotations

• 
  Saurabh | NodeOps (@saurra3h) reported 14 minutes ago

  github down?

• 
  Prime 🏳️‍⚧️ (@Prim3st) reported 16 minutes ago

  @AAO23114 @SolaraProto Unfortunately that's probably not possible without a dedicated server... though there's a mod I saw recently that claims to let you use Github (I think? It was definitely using ***) to store/backup world saves. Maybe you could use something like that to have a shared world?

• 
  Nadeem Jaleel (@nadeem_jaleel) reported 19 minutes ago

  @ThePrimeagen Github down again ?

• 
  NEET INTEL (@neetintel) reported 20 minutes ago

  A post "decoding" X's new algorithm has gone viral. It tells you what's dead, what wins, and to screenshot it. X open-sourced the entire algorithm on GitHub, so I downloaded it and checked the claims against the real code. Most of it doesn't hold up. What the post got WRONG: → "Small accounts get a 3x boost from out-of-network reach." It's the opposite. One part of the code (a file called oon_scorer) exists purely to turn DOWN posts from people you don't follow. Its own comment says "prioritize in-network." The thread printed the algorithm backwards. → "Media gets 2x the weight." There's no 2x. The code just records whether a post has an image. It's a plain yes/no without any multiplier attached. → "Posting 4+ times a day triggers a penalty." There's a real rule that stops one person flooding your feed. But here's the deal: it only spaces out how often you show up in a single scroll. There's no daily count, and no number 4. That was invented. → "Closers like 'what do you think?' get you flagged." There is no engagement-bait detector anywhere in the code. → "Long 4,000-character posts get boosted." I searched the whole codebase for "4000." Nothing. What it got RIGHT (one thing): → Replies really are judged by WHO replies, not just how many. The code has a setting for whether a large account joined your thread. Credit where due. The irony? The repo ships a file that scores post quality. One thing it measures is literally called a "slop score" — X built a tool to detect low-effort filler. A recycled "what's dead / what wins" thread is exactly that. The takeaway? X's algorithm is public. Anyone can open it, but almost nobody does. Instead, they reshare a thread that summarized a blog that paraphrased a tweet. When a post hits you with confident numbers, ask the one question that matters: did they actually open the file?

• 
  Peter Steinberger 🦞 (@steipete) reported 21 minutes ago

  @EndGovTyranny Please file a github issue with more infos - with that alone we can't help. That's likely a weird model edge case. If you want a fast fix, use one of the top-gen models (OAI, Anthropic)

• 
  Leaving Tech (@leaving_tech) reported 25 minutes ago

  @ThePrimeagen Angry unicorn! GitHub in trouble again.