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:

• 
  BlockXBT (spirit/acc) (@0xblockXBT) reported 3 minutes ago

  Due to some issue with github I had claim the same with new CA GRZFGTFNbNxTTRCVDrMvhE9Pp86HQ1ehpZ7DqgGTpump

• 
  Hermes-Agent News (@HermesAgentSol) reported 4 minutes ago

  ok wait garrytan/gbrain just crossed 15.9k stars on github. garry tan's personal hermes/openclaw agent brain. opinionated typescript and 2151 forks already. when a yc partner ships their own agent brain on your framework that's a real signal. also teknium landed the xai-oauth credential loop fix overnight. grok-4.3 now reports its real 1m context instead of 256k and the error message finally stopped blaming subscribers for being unsubscribed.

• 
  Dylan from 2045 (@dylan2045ad) reported 5 minutes ago

  AI ate tech this week: OpenAI is Coke. Anthropic is Pepsi. Grok is RC Cola. Gemini is the Costco brand your dad swears tastes the same, lets see what tomorrow brings? Mistral is the European one with real sugar. Llama is the 6 pack at the back of the fridge nobody opened. GitHub is buckling under AI-generated PRs. Hashimoto is out. Polymarket whales hide behind VPNs and crypto, but AI agents are chasing insider traders and hunting them down. We built the thing that's eating us.

• 
  ジョン (@jcinjpn) reported 6 minutes ago

  It’s abundantly clear that GitHub is going to burn itself down in its own land grab for AI. We need an open alternative or one done by a player that isn’t in the model game.

• 
  David Cramer (@zeeg) reported 6 minutes ago

  @eternalmagi dont have context, is there a github issue by chance

• 
  Jarett Reginald Stewart Dunn (@STACCoverflow) reported 11 minutes ago

  incredible how badly pump keeps ******* up their product lol forever the only way to connect github was on mobile, but not as a signin option now I just logged into a net-new privyio account by logging in via oauth on desktop via.. github.. someone @NostaIgicGareth or someone ? make a coin for me, share all fees with github staccdotsol wanna see which account it prefers for fun n profit thx

• 
  Aki Ranin (@aki_ranin) reported 12 minutes ago

  New Claude Code master prompt: "/goal assign next GitHub issue and start PR, iterate until no critical or high issues found with PR review skill"

• 
  NEET INTEL (@neetintel) reported 13 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?

• 
  Lee Penkman (@LeeLeepenkman) reported 14 minutes ago

  @gxjo_dev stupidity... no... frupidity basically. like the exec cfo team is like well what if we reduce headcount wouldnt profitability go up? Like yes but you just wont be a good product company without a good product... like you are already struggling to compete with GitHub lmao... how u gna compere with codex n claude when they do repos? Also theres just fear that these devs cant learn AI which is kind of wrong because devs seem to be best placed to leverage AI of all? idk. im just guessing. lots of saas companies just doing layoffs had hired too many people having thought they would keep growing then they didnt their stock went way down and becomes harder to raise money for them because of bearish outlook for them competing with claude so investors scared off so harder for them to afford lots of developers so kind of start sinking. the devs would do better elsewhere anyway better to be on a new ship instead of sinking one.

• 
  Quantum (@ItsMeQuantum) reported 18 minutes ago

  @emilios_eth They don't even know what syntax error is All they do is just Link LLM with GitHub and ask for a summary from it

• 
  Lucy (@TheLucyShow1) reported 20 minutes ago

  FYI: GitHub is a platform where people store, manage, and collaborate on code and software projects. It’s built around a system called ***, which tracks changes to files over time. Think of it like: Google Docs for programmers — multiple people can work on the same project together. A backup system — every version of the code is saved. A portfolio site — developers show off projects there. A collaboration hub — companies and open-source communities build software together. Here are the core ideas: Repositories (“Repos”) A repo is basically a project folder stored on GitHub. It can contain: Code Images Documentation Websites Apps Games Example: A developer making a weather app would keep all the app files in one repo. *** *** is the version-control system underneath GitHub. It tracks: who changed something what changed when it changed how to undo mistakes So if someone breaks the code, you can roll back to an earlier version. Commits A commit is like a saved checkpoint. Example: “Added login screen” “Fixed typo” “Updated homepage colors” Each commit creates a history trail. Branches Branches let people experiment without breaking the main project. Example: Main branch = stable version New branch = testing a new feature If it works, the changes get merged in. Pull Requests A pull request is basically: “Hey, I made changes — can you review and approve them?” Teams use these to discuss and review code before adding it to the main project. Open Source GitHub is huge for open-source software. That means anyone can: view the code contribute improvements report bugs learn from real projects Projects like: Linux Foundation’s Linux ecosystem Mozilla Firefox Microsoft VS Code all use GitHub heavily. Why People Use It Software development Team collaboration Backup/version history Learning programming Sharing projects publicly Building websites/apps Managing documentation Simple Analogy Imagine writing a book with friends: GitHub stores the book *** tracks every edit Branches let you try alternate chapters Pull requests ask others to review changes Commits are saved drafts That’s essentially how software teams build programs together.

• 
  Omri Ariav (@omriariav) reported 21 minutes ago

  @avivsinai workstream briefs seed deterministically from a file or GitHub issue: `up --seed-from file:./brief.md` `up --seed-from issue:31` `up --seed-from gh:owner/repo#31` `--dry-run` previews, the live form writes the brief and brings the team up in one call.

• 
  NEET INTEL (@neetintel) reported 23 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?

• 
  Alef Benson (@AlefBens) reported 24 minutes ago

  @_sirajuddeen_ @OfcMachete19 @iupdate I've been burnt too many times. Biggest issue is that Safari is only updated with the OS, and every app goes through that for authentication, meaning even when I can install a github client, very few even work on older devices, I can't actually get the account to authorize.

• 
  Valerie Waters (@ValerianWaters) reported 25 minutes ago

  @md_kasif_uddin Async by default: GitHub issues or Linear, then Slack threads for blockers