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:

• 
  Sudo su (@sudoingX) reported 2 minutes ago

  @worthyapes plot twist, those two are not fighting. an obsidian vault is just a folder of markdown, put it under *** and you have both, obsidian the editor, *** the history and sync. and the msft worry is fair, but that is a github problem, not a *** problem. self host it, forgejo or a bare repo on your own box, microsoft has nothing. history and privacy, both.

• 
  AI Signal (@AISignal_X) reported 6 minutes ago

  You're still paying $22/month to clone a voice. Voicebox does it in 3 seconds. Free. Offline. No cloud. 26.8K GitHub stars in weeks. 23 languages. 7 voice engines. And an MCP server that lets Claude Code speak your results back to you in a cloned voice. The subscription era for voice AI just ended.

• 
  LottieFiles (@LottieFiles) reported 6 minutes ago

  @github @code This solves the biggest remote work problem: you don't lose your context when you switch devices, that's the whole game.

• 
  Vaibhav Sisinty (@VaibhavSisinty) reported 8 minutes ago

  this is a weirdly revealing list. the 5 fastest-growing GitHub repos this week all solve a problem AI was supposed to have already solved. the 5 blowing up 🧵

• 
  habitual linecrosser (@omanyeric) reported 11 minutes ago

  @wanjirulikemee App is done, but I'm having trouble uploading it on github. It's 100% Ai made. It didn't even take 20 minutes. Maybe someone with better tech skills should give it a shot. It would be great to starve the government while not starving ourselves.

• 
  Kyle Ye (@KyleSwifter) reported 12 minutes ago

  @zeddotdev @OpenAIDevs Does using a ChatGPT Subscription in Zed require an existing Zed account login? My GitHub login seems accidentally blocked. Support said it was a temporary few-week heuristic blocks, but it still hasn’t been restored. I only need sign-in for ChatGPT/Codex, not Zed cloud credits.

• 
  Louis Gleeson (@aigleeson) reported 12 minutes ago

  Grok runs the X algorithm. I just read the entire open-sourced codebase line by line. Here is exactly what makes a post go viral on X right now (save this): xAI quietly dropped the full For You algorithm on GitHub. 16,500 stars. Apache 2.0. Every Rust file, every Python script, every ranking signal. The first thing you need to understand is that there is no hand-engineered ranking anymore. None. xAI removed every single human-written rule from the system. The README states it directly. A Grok-based transformer does all the ranking now. That changes everything about how you should post. The transformer does not care about your follower count. It does not care about your blue check. It does not care about hashtags. It is looking at one thing. Your post's predicted engagement score across 15 specific actions. Here are the exact 15 actions the model is predicting for every post in your feed right now. Copied directly from the code: P(favorite). P(reply). P(repost). P(quote). P(click). P(profile_click). P(video_view). P(photo_expand). P(share). P(dwell). P(follow_author). P(not_interested). P(block_author). P(mute_author). P(report). The first eleven are positive. They push your post up. The last four are negative. They push it down. Your final score is the weighted sum of all fifteen. That is the formula. That is what every viral post is solving for whether the author knows it or not. Now look closer at the list. Eleven different ways to win. Most creators only optimize for likes and reposts. They are leaving nine signals on the table. The strongest signal in that list is dwell. Time spent on your post. The algorithm tracks how long someone stops scrolling to read what you wrote. A 400-word post that holds someone for 12 seconds beats a one-liner that gets 50 likes. The model has learned that dwell predicts every other engagement. This is why long posts are exploding right now. Not because X "promotes" them. Because they generate dwell, and dwell stacks on top of every other prediction the model is making. The second thing buried in the code that nobody is talking about is candidate sourcing. Your post enters the feed through two pipelines. Thunder serves your post to your followers. Phoenix serves your post to everyone else. Phoenix is the one that makes you go viral. Phoenix is a two-tower model. One tower encodes the user. The other tower encodes every post on the platform. It does similarity search using dot product matching against the global corpus. Then it pushes the top matches into feeds of people who have never followed you. This is exactly how a 12-follower account suddenly hits 800,000 views. Phoenix found a semantic match between the post and a user's engagement history, and the transformer scored it high on its 15 actions. Which means your post is not competing with your followers' posts. It is competing for embedding space. The way you win Phoenix is specificity. The two-tower model rewards posts that sit in a clear semantic neighborhood. Vague posts get vague embeddings and never get retrieved. Sharp posts about a specific topic with specific words get pulled into feeds of people obsessed with that topic. This is why "I built a SaaS" gets nothing and "I built a Postgres-to-Snowflake CDC pipeline in 4 hours using Estuary" goes viral. Same person. Same product. Completely different embedding. The third thing in the code is the Author Diversity Scorer. The model deliberately attenuates repeated author scores in the same feed. Translation: if your last three posts already got served to a user, the fourth post gets a penalty. This kills the "post 8 times a day for the algorithm" strategy. The algorithm is specifically engineered to dampen that. Better to post fewer times with stronger content than to flood and have your own posts compete with each other. The fourth thing is the filter list. Before any post gets scored, it has to pass through ten filters. The MutedKeywordFilter. The PreviouslySeenPostsFilter. The AuthorSocialgraphFilter. Plus a final VFFilter that removes anything classified as deleted, spam, violence, or gore. What kills your reach more than anything else is the PreviouslySeenPostsFilter. If a user has already seen your post once, you are filtered out completely from their feed. Forever. Which means every reply you make to a viral tweet that does not get visibility is permanently dead weight for that user. This is why the people who win at X reply only when their reply itself is good enough to be a standalone post. The last thing, and the one that should change how you write every single post: candidate isolation. During ranking, the transformer cannot let your post attend to other posts in the batch. It only attends to the user's engagement history. Your post is being scored alone. Against itself. Against what the user has previously engaged with. That is the entire game. Stop writing for the timeline. Write for the engagement history of the people you want to reach. Find the topics they already like, the accounts they already follow, the threads they already saved. Write into that semantic space. Phoenix will do the rest. The algorithm is no longer a mystery. It is sitting on GitHub at 16,500 stars. Apache 2.0. Anyone can read it. Almost nobody will. Link in comments.

• 
  Peter Giacomo Lombardo (@pglombardo) reported 14 minutes ago

  To sign into a site X, I click the Github button. Github prompts me to sign in - I click my password manager. The password manager prompts me to sign in. I populate the Github sign in. Github then asks me to authorize the sign in. I do and finally get back to the original site which sends an email with an access code.

• 
  Oh Come On! (@BluthCapital) reported 15 minutes ago

  Market thought AI was a threat to $GOOG Yet “automated productivity” and layoffs is an existential risk to $MSFT Copilot is a “Me three”, GitHub was zeroed via IP theft, LinkedIn during a hiring recession is a problem.

• 
  AParanoidBW (@aparanoidbw) reported 18 minutes ago

  @petersteele If there is a law requiring uptime, github/Microsoft is in trouble. Cloudflair looking a little sweaty too

• 
  Strong Genetics (@Strong_Genetics) reported 19 minutes ago

  Listed my first issue on GitHub for openclaw today and it was diamond lobster grade and it was closed within an hour or so by the awesome developers in the Clawtributors Discord... They are tackling stuff fast....Glad I could contribute..... Besides that one issue I flagged 5.18 has been rolling

• 
  Dobroslav Radosavljevič (@dobroslav_dev) reported 20 minutes ago

  @WonderingDavid Attack vector was via Github CI, but compromised packages are on NPM and it's spreading via NPM. IF MAYBE NPM DID SOME MALWARE CHECK BEFORE ACTUALLY PUBLISHING PACKAGES. We would have 99% less issues like this. You can publish anything you want right now, no check. It's horrible. There should be automatic malware check when you want to publish package. It should not be published instantly.

• 
  Ferbin (@Ferbin08) reported 25 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?

• 
  linares (@skibidifatrizz) reported 26 minutes ago

  @404not_utkarsh He's not spamming his GitHub with performative bullshit. What's the issue

• 
  John Loeber 🎢 (@johnloeber) reported 26 minutes ago

  There was a moment in 2023 when people thought that GitHub was the future of AI coding. I remember when many people on Twitter wrote off Cursor and Windsurf because they expected GitHub Copilot to crush everyone. "GitHub has all the data, they're so deeply integrated into the dev ecosystem, they sit right at the root of the dev stack and can verticalize all the way..." so many insightful opinions from the Twitter Commentariat, and yet reality played out in exactly the opposite way. Humbling for prediction-makers! Today, GitHub is down to one 9 of reliability, and I haven't heard of any of their AI features in a year. All one can ask is: what happened? Two or three years ago, people thought this was going to be a $100B+ asset. Now it's looking like the next Skype, just a slowly-enshittified product in an M&A graveyard. I used to know smart people who worked there. Not anymore...