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:

• 
  Mind Prison (@M1ndPrison) reported 1 minute 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.

• 
  Kunal Yeola (@yeolakunal) reported 1 minute ago

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

• 
  Tony Junkes (@tonyjunkes) reported 3 minutes ago

  Not having a “to top of page” button on a GitHub PR’s Files Changed tab when going well down a list of changed files is painful. Yes the home key does the thing, but hand on mouse, mouse yearns to click.

• 
  Kendall Zettlmeier (@KZettlmeier) reported 3 minutes ago

  @davidfowl @github I would love agent mode to handle code review comments and issues but leaving the merging to the code writer (we have QA validate after an approval)

• 
  Yashas (@YashasGunderia) reported 8 minutes ago

  Most AI-native startups will not lose because they ship too slowly. They’ll lose because they ship fast without knowing what actually worked. Coding agents gave every team more velocity. Cleo gives them product memory. Customer feedback, GitHub issues, Slack threads, metrics, tickets, specs, launches, agent traces, all connected into one loop that tells your team and your dev agents what to build next. We’re opening the Cleo waitlist today. For small teams trying to compete with companies 100x their size (link in comments)👇

• 
  verrsane (@verrsane) reported 10 minutes ago

  github down again, noice

• 
  Deven (@whodeven) reported 11 minutes ago

  GitHub Copilot's suggestions feel generic and slow. i still rewrite code by hand because the output is often too generic for niche logic. what's your go-to fix?

• 
  Fatima (@Fatima7223) reported 17 minutes ago

  @cb_doge 𝕏 open sourced its recommendation algorithm on GitHub. Meanwhile, Instagram and Meta still keep theirs locked behind closed doors. No public code. No independent audits. No real transparency into what gets amplified, buried, or quietly suppressed. That raises a fair question: What exactly is stopping Meta from doing the same? Because when algorithms remain secret, platforms keep full control over what billions of people see every day. • Users can’t verify claims about bias or shadowbanning. • Researchers can’t properly audit ranking systems. • Harmful amplification patterns stay hidden behind “trust us.” • Public narratives can be shaped without visible accountability. Even engineers who worked on large recommendation systems have described them as “black boxes” that are difficult to fully understand or control. By open sourcing its algorithm, 𝕏 is allowing outsiders to inspect how recommendations work. Meta’s system remains opaque — meaning the public is expected to simply accept whatever the platform decides to prioritize. Transparency doesn’t solve every problem. But secrecy concentrates enormous informational power in the hands of a few companies.

• 
  C. ₿utt 📵 (@ctbutt114) reported 22 minutes ago

  @zquestz Reports are an issue with GG20, which was identified last month and set to be addressed. However, being open source, the bug was revealed via GitHub, & someone took advantage. Single bad actor on a new node. DLKS has been on the roadmap. Needed faster now.

• 
  Your Friend Myk (@mykola) reported 22 minutes ago

  @joelhooks is this just static content? so like a github pages alterntaive? can't run a server etc?

• 
  Benjamin Woodruff (@_bgwoodruff) reported 23 minutes ago

  @Zackary_Chapple I'm not excited about this either, and a dunk on GitHub is easy, but it's a huge company and different people can work on different things. It does seem like they are legitimately trying to fix some of the major issues in GitHub.

• 
  Erik Goins (@erikgoinsHQ) reported 23 minutes ago

  I built a financial forecasting app for our real estate business. Some take aways: 1. It's incredible what you can do with AI. This took me ~3 days part time. 2. If you're not a dev, good luck... Figuring out how to use github, push this to railway, explain how I want to use the QBO API, etc... there's still a big learning curve here. 3. Domain expertise is still very real. The first version of this was terrible. I had to help the AI create forecasting rules. 4. Businesses (enterprises) are going to need a lot of AI governance. Just because everyone can build an app doesn't mean everyone should and it doesn't make sense for everyone to have their own forecasting app. You really want one well done app, not 100 bad ones. 5. We're not replacing QBO. Too ingrained- it gets to stay the system of record. Looks like there's still a very real moat for the right SaaS products. Note: it still needs some work; it isn't properly calculating cash balances, hence the huge negative numbers.

• 
  Shadow (@4shadowed) reported 25 minutes ago

  @alex_marples @openclaw Have you filed any GitHub issues? Helped test the betas? Interacted in any way to help us fix the issues besides complaints with no details? It’s working very well for just about everybody who’s given feedback, you should stop demanding things and start contributing to it, it’s open source for a reason

• 
  Emil Privér (@emil_priver) reported 25 minutes ago

  github actions is broken today

• 
  J Filipe (@jrmromao) reported 28 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