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:

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

• 
  AllOrNuthin 💀 (@PDave95) reported 2 minutes ago

  @AgentOS_Inc @AlexandraLiam3 github link is broken

• 
  Jeromy Sonne (@JeromySonne) reported 2 minutes ago

  @TJ_Bongiorno None of them. MTAs fundamentally are broken technology not worth it. Claude can do a proper lift study DIY or using an open source framework from GitHub. Build don’t buy and save the $$$

• 
  Ferbin (@Ferbin08) reported 6 minutes ago

  @cyrilXBT every github trend: week 1 stars explode, week 3 issues mount, week 5 nobody touches it. where are routing and agent memory in that cycle?

• 
  ฿Ø₮₴Ø₦Ɇ (@botsone) reported 8 minutes ago

  @shub0414 I have a home *** server - I run gitea on my raspberry pi. It's really good. I actually just downloaded my entire github, told hermes to extract it and upload every repo to my home server, and it one-shot it in about 10 minutes using a local LLM.

• 
  David Cramer (@zeeg) reported 11 minutes ago

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

• 
  Yassine Bouanane (@ybouane) reported 12 minutes ago

  @GMMeyer @theo @r_marked To be honest nowadays SLAs don’t mean much anymore, every month or so, there’s a massive outage, services like github go down, npm gets hacked, a datacenter gets bombed, a whole region goes down… I feel like SLAs were oversold… cloud didn’t solve the problem of outages, we have to live with that. Massive platforms like X, or IG go down some times, it happens, it’s not the end of the world most users understand it.

• 
  Dusan (@dduxAdventure) reported 16 minutes ago

  @ibuildthecloud I don't think they have that, due to events being "rare", so most opt out for webhooks or infrequent polling. If you're bored you could make a little server with hooks api for github webhooks to hit on one end and a socket on the other for you to get events.

• 
  Farhad zand (@farhad_pd) reported 17 minutes ago

  Hey @grok team, your GitHub connector is seriously broken. I ask it to make a change and push it to my repo. It confidently tells me “done,” but nothing is actually changed or pushed. It’s just falsely claiming the task was completed.

• 
  Miscellany (@Miscellany_a) reported 17 minutes ago

  @FL_Slayer Oh it 100% is. They literally stole the UI from ChartForge, even down to the "Everything you need" tab they have on their website. Their Github says "trained with 42,000 charts from the CH/YARG communities" and I bet you they didn't bother asking charters for permission either

• 
  J Filipe (@jrmromao) reported 23 minutes ago

  Pivoted CostLens from "AI cost tracking" to "AI productivity measurement" last week. Built in 5 days: - MCP server that tracks what AI agents actually ship - Automated ROI reports for engineering leaders - CLI setup in 30 seconds - GitHub PR correlation Same product, completely different value prop. Before: "save money on AI" Now: "prove AI delivers value" One resonates with finance. The other resonates with everyone. #buildinpublic

• 
  Kea (@alpinoWolf) reported 24 minutes ago

  " we literally cannot programmatically trade from this account until Polymarket's engineering team patches the V2 library and resolves GitHub Issue #65. " How does you evpoly bot do ? Please help me ? Is python coding problem here ? 3/3

• 
  Humi (@byteHumi) reported 25 minutes ago

  @gxjo_dev For them I have the last paragraph...just sit down see what's that thing you are really good at And scape and find out all the yc startups or startup in general that got recent findings and you can easily get the emails of the founders from GitHub commits ...do good cold dms with your best work

• 
  kkkfasya (@kkkfasya) reported 26 minutes ago

  they should hang every github engineer upside down and tickle them with feathers until they DIE

• 
  Ross Morsali (@rossmorsali) reported 27 minutes ago

  @HindCZ @claudeai I migrated several accounts to a team plan recently, got in touch with support twice RE billing - no response. One of our biggest uses cases, sharing plugins/skills across the team across all the apps is not working - there's open github issue for it - still not resolved after around a month and was recently auto-closed... The lack of support is making their product non-viable. And if I want to build a solution around claude to fix their issues, well, that got a lot tougher recently...