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:

• 
  Frooxius @ MFF - frooxius.bsky.social (@Frooxius) reported 10 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.

• 
  atomicbot.ai (@atomicbot_ai) reported 11 minutes ago

  Hermes Agent vs OpenClaw using Qwen 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

• 
  Lazi (@algoritmii) reported 14 minutes ago

  @github bro ffs fix your ******* issues stop pushing features

• 
  Benitto J D (@BenittoJD) reported 14 minutes ago

  Github actions are down again

• 
  Moe Sbaiti (@MoeSbaiti) reported 15 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.

• 
  isaac (@isaac_yeang) reported 16 minutes ago

  jk just lazy error message handling another bajillion dollars to github

• 
  Abinash (@implabinash) reported 17 minutes ago

  @ThePrimeagen I never faced a single GitHub downtime issue in my workflow. Oh! Sorry, I have been using GitLab for a year now.

• 
  闇ぼの@𝕏級ピンク珍獣.rs (@kenbono13) reported 20 minutes ago

  @mcsetty @bee_fumo Most software that directly uses GitHub for the download, build, installation (NOT using the AUR) aren't installed under root in the first place. It's installed under $HOME so it wasn't an issue. AUR is the exception since it uses the Arch build system.

• 
  Mind Prison (@M1ndPrison) reported 24 minutes ago

  @GlenBradley Yes, I have gone deep into it in the past as well. Haven't had time to look at the current update, but the problem has been that the code on github is mostly irrelevant. The important bits are all the parts that aren't public. There is no way to no how the ML algo is ultimately weighting all the parameters. Most importantly, I've catalogued many accounts posting exactly the same content with orders of magnitude differences in reach. The thing that would make this platform useable would be to fully eliminate all account based weighting and go to solely post based weighting. The reach of your post should be only on the merits of what you posted versus who you are.

• 
  Abu Olumi 🪶 (@Olumi441) reported 24 minutes ago

  There's also a public feed. BaseLens fetches Base GitHub releases and analyzes them with AI automatically. Clean upgrade cards. No jargon. No noise. Anyone can read it, no login needed.

• 
  Louis Gleeson (@aigleeson) reported 28 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.

• 
  Yaseen Shaik (@YaseenTech4) reported 31 minutes ago

  Just completed an assignment on building a dependency graph for AI agent tools using Google Super + GitHub integrations 🚀 Started with: “This should be easy” Then came: TypeScript errors zip/upload issues CRLF debugging 😭 finally got the submission accepted successfully ✅

• 
  Caneleo (@Caneleo55) reported 34 minutes ago

  Since there is lots of hype on @polymarket right now you have to be extra careful there are lots of scammers out there 🚩 Don’t download random trading bots or repos that are trending on GitHub i tested one once deposited 10$ to a fresh wallet and run the bot on a vps turns out it had a secret function that sent your .env with your private keys to a different server 💀

• 
  Jerome (@jeromeq2004) reported 34 minutes ago

  github releasing the agentic ai developer cert is funny because the actual exam is going to be 'fix this thing claude broke in production while it tells you the tests pass'

• 
  Kunal Yeola (@yeolakunal) reported 37 minutes ago

  Asked GitHub Copilot to fix ESLint issues and it added eslint-disable at the beginning of the file 😭