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:

• 
  Nadeem Jaleel (@nadeem_jaleel) reported 7 minutes ago

  @ThePrimeagen Github down again ?

• 
  𝙹𝚘𝚜𝚑𝚞𝚊 𝙱𝚒𝚍𝚍𝚕𝚎 (@joshua__b) reported 7 minutes ago

  @MagneticNorse You're right, they are hedging. But look at the board: open-sourcing the algorithm to GitHub is a brilliant tactical move because it creates the illusion of total transparency. The problem is that the code itself isn't where the suppression happens. The suppression happens in the training data, the safety filters, and the jurisdictional legal compliance that Musk himself admitted the algorithm is subject to. Hedging against criticism by showing us the code is like showing us the engine of a car while the administrative state still holds the steering wheel. It's an improvement, but it doesn't change our destination.

• 
  Aditya Sharma (@aditya_sharma) reported 9 minutes ago

  elon musk dropped the X algorithm on github. i read all 25,000 lines so you don't have to. here's what actually decides your reach. what actually matters - dwell time is the entire game. how long someone pauses on your post is counted twice in the scoring. likes barely move the needle. the pause does. - saves and shares are the highest-value engagement after dwell. they signal the strongest intent. - video has a minimum duration floor. clips shorter than the threshold get zero video credit. five seconds plus, always. - one post per conversation thread survives in any feed. your five-post thread competes with itself. the algorithm picks the strongest one. - replies to big accounts (1000+ followers) get scored on a 0-3 quality scale. high score and you land in the reply panel of viral tweets. low score and you're invisible. - replies to small accounts get a binary spam check only. no quality scoring path. no reach upside. - mutual follow overlap matters. tight clusters of mutuals create reach corridors for everyone in them. - clear topic identity beats vague posting. the algorithm tags your post with topics. clear topics route you to people who follow those topics. - new accounts on the platform get an easier path to reach you than established ones. if you target young/new users, the algorithm is on your side. what kills your reach - posting too often. the algorithm has decay coded in. your second post of the day gets a fraction of your first. your fifth gets almost nothing. - quoting or replying to a flagged tweet. you inherit the badness. your whole post gets dropped even if it's clean. - ai slop. there's a dedicated slop detector that scores your post 1 to 3. high slop = killed reach. - being unclear what your post is about. vague content doesn't match anyone's interests cleanly. - mid-controversial content. it gets pushed away from the high-attention slots in the feed because ads can't sit next to it. - posting your own tweet's reply hoping it boosts the original. only one of them shows up. it might be the reply, not the original. myths to kill - hashtags do nothing. zero boost in the code. they're not even read by the ranker. - premium doesn't get you reach. paid and free accounts go through the same pipeline. - long threads don't beat single posts. the algorithm picks one post per thread. - engagement bait doesn't work. it trips spam classifiers on low-follower accounts. - posting twelve times a day doesn't get twelve impressions. it gets one strong one and eleven weak ones competing with each other. - replying to viral tweets isn't easy reach. the quality bar is high. cheap replies fall straight into the spam path. - timing tricks don't beat ranking. timing helps you enter the candidate pool. quality decides if you win. - external links don't hurt you. clicks are actually one of the 19 positive scoring signals. - the algorithm doesn't hate any specific format. it hates unclear content. format is fine if the content is sharp. - you don't need 10k followers to get reach. the algorithm doesn't read follower count as a scoring input. it reads engagement quality. the playbook - write posts that make people pause for 5+ seconds. dense info, clear structure, screenshots with detail, comparisons. - if you use video, clear the duration floor. always. pick one clear topic per post. don't mix five things into one tweet. - reply to bigger accounts in your niche with substantive, high-effort replies. one good reply beats ten mediocre ones. - build mutuals in tight clusters around your niche. broad spray-follow strategies don't help. focused clustering does. - post 1-2 times a day, not 10. quality compounds, volume decays. - don't quote tweets that look flagged or risky. clean what you cite. - write like a human. don't post ai output verbatim. target newer users on the platform if you can. they have a friendlier reach path for creators. if you're a small account starting out - replies to big accounts in your niche are your highest-leverage move - build a tight mutual cluster of 50-200 accounts in your exact space - one strong post a day beats five medium ones clear topic identity, every single post if you have an established audience - your reach problem is breaking outside your network - dwell time on individual posts is your biggest unused lever - clean brand safety keeps you in prime feed slots next to ads - volume hurts you more as you grow, not less the whole system is built on one bet: that a model fed engagement data can decide relevance better than any rule. there's no hashtag boost, no follower boost, no time-of-day trick in the code. just sequences in, probabilities out. what works is what humans actually want to read. the algorithm is just better at measuring it now.

• 
  Kirann (@SaikatBera9933) reported 10 minutes ago

  consistent? But how? For the last 5 month i can't be consistent because of college, exams and internship, my GitHub streak is being broken many times, inconsistent in x. How are people so consistent in socials?

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

  @yxcc Discord or GitHub Issues.

• 
  Hedwigz (@itsamitush) reported 11 minutes ago

  @ZoharEiny E.g. github mcp for code,issues & coralogix mcp for logs & internal mcp for org structure

• 
  ᛗᚨᚱᚴᚢᛋ (@guitaripod) reported 15 minutes ago

  @piq9117 GitHub down? i don't believe you. IT'S IMPOSSIBLE!!😭😭 (luke skywalker reaction)

• 
  Babyface4Lyfe | VTuber (@Babayface4Lyfe) reported 16 minutes ago

  I’m seeing a lot of people be concerned about custom chat elements if stream elements goes down. I may look into developing a local file system that doesn’t rely on stream elements, that I’ll then put on github or something for the community. Currently, the stream elements thing is still just rumour and speculation so I won’t make any promises until I hear otherwise.

• 
  ATXA (@AtxaTrades) reported 19 minutes ago

  This is the ONE problem the X Algorithm has: It contradicts itself. Here is why: X has shared their algorithm update in Github today. Everyone is going crazy about it. So i decided to go take a look at it. I asked Grok to analyze it and explain it to me. Once it did, i took my last post and shared it with grok. I asked him to analyze the post (based on the Algorithm shared in Github) and rank it based on the metrics and steps the algorithm takes. This is the crazy part. It gave it a score of 72-82/100!! Not so bad right? I am a small account, i am not expecting a 100 score. But wait, there is more. It said it would likely rank in the top 20-40% of candidates in the mixed batch for the right users, and strong enough to appear HIGH in the "For You" tab. Reality Result: 22 views. So my question is: If Grok is a big part of the algorithm dictating what´s good and what is not, and technically Grok just told me my post was suppose to do good in the "For You" tab... Why only 22 views?

• 
  Pierce Boggan (@pierceboggan) reported 24 minutes ago

  @blaken @sinclairinat0r @code Thanks for the feedback! How do you think we can improve in terms of the core agent loop? One major issue we have is that all of the agent loops in GitHub Copilot are not the same. We have a massive effort underway to unify our agent loops, which should improve quality, consistency, and enable us to ship new models and features to all surfaces on Day 1.

• 
  Manish rawat (@R11manish) reported 24 minutes ago

  @GithubProjects GitHub is down again

• 
  Frooxius @ MFF - frooxius.bsky.social (@Frooxius) reported 24 minutes ago

  @MrRocketFX @ResoniteApp @unity They should be compressed on Resonite side? I'm not quite sure if I understand, it might be better to make GitHub issue for the request at the repo.

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

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

• 
  Priyanshu (@iproductAI) reported 30 minutes ago

  For example: "Sign up for early GitHub Copilot Desktop access." Please fix this issue.

• 
  Farhad zand (@farhad_pd) reported 31 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.