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:

• 
  YOHAN | AI DEV (@4id3v) reported 2 minutes ago

  @vercel_support @rauchg @timneutkens private GitHub repos + deploy hooks are suddenly broken. it now blocks deploys saying the last commit author must be a Vercel team member. used to work fine before. any quick fix or workaround?

• 
  DK (@donghaxkim) reported 4 minutes ago

  reposeek is a github specific search tool where you describe what you're trying to build, and it outputs a ranked list of real GitHub repos worth forking or studying. Sorted by the signals that actually matter. Not just star count. I built it because my agents kept on starting things from scratch when a solid repo already existed. And the usual ways of finding one are not the best. Google and LLMs surface whatever's popular, keyword matching, and SEO'd, not what's actually maintained, correctly licensed, or a real match for the problem. You end up forking a 30k-star repo that died two years ago, or one with a license you legally can't ship on. So it ranks on the stuff you'd actually check yourself: star momentum (alive or abandoned?), forks, license, and semantic fit (does the README really describe your problem, or just share keywords?). The whole idea is that half of shipping fast is starting on a foundation someone already battle-tested. Cursor is literally a VS Code fork. This just helps you find the solid foundation you can build on before you waste your weekend recreating it from scratch. And if someone's already hit your exact problem, you get to borrow their approach instead of trying the same approaches some else already tried

• 
  Ranbir Singh (@android_poet) reported 4 minutes ago

  I am thinking about creating samples for RevenueCat KMP. I saw some bugs in the GitHub issues, so let’s see if I can reproduce them and create a pull request. I already created Supabase SDK KMP + RevenueCat KMP, so I guess people will be able to ship even faster with KMP.

• 
  srijuu (@microtaskq) reported 8 minutes ago

  @maaz404 make github issues instead

• 
  Turtle (@LG715499) reported 8 minutes ago

  @TheProfInvestor Thay have competition on enterprise AI from Microsoft. Positioning Github as the main AI agent for Enterprise. Also, something I was wondering, if cloud pricing is mostly constant and server prices skyrocket wouldn't it mean less profits for cloud providers?

• 
  Mohi 🇮🇷🇩🇪 (@disismohi) reported 14 minutes ago

  I'm not saying every exploit belongs on GitHub. But the inconsistency is the problem. Either you allow security research or you ban all offensive tooling. You can't pick based on vendor pressure.

• 
  gitbankbot (@gitbankbot) reported 14 minutes ago

  open source contributors solve real problems. they should get paid when those solutions land, not after three follow-up messages. gitbank automates the full bounty flow on Base L2. maintainer sets a USDC amount on a GitHub issue. contributor merges a qualifying PR. smart contract releases the funds automatically. the payment is as reliable as the CI pipeline.

• 
  Martin (@Unpopular_Tech) reported 16 minutes ago

  Microsoft owns GitHub, Microsoft built Copilot Microsoft has a $13 billion investment in OpenAI and their engineers still went looking for something else if your own people won't use your product that's not a cost problem, that's a verdict

• 
  Peter Fox (@peterfox) reported 17 minutes ago

  Today's the first day where I've really seen just how clumsy and poor the UX of @github is. We really need a better way to work. If more effort was put into the UX instead of stuffing AI in, we wouldn't have this problem.

• 
  LayerLens (@layerlens_ai) reported 18 minutes ago

  stratix-python just crossed 120 stars and 70 forks on GitHub. Thank you to every developer who starred, forked, opened an issue, or submitted a PR. ⭐ 120 stars 🍴 70 forks 👥 5 contributors 🏢 60 org followers Every star is a signal. Every fork is a team that decided evaluation matters. What started as an SDK for running LLM evaluations is becoming the open-source backbone for teams that refuse to ship untested AI. The roadmap is public. The harness is open. The judges are live.

• 
  sam (@metruzanca) reported 19 minutes ago

  @nirajxdev I was going to take a look at your LinkedIn/github/website and offer feedback but none of that is linked on your Twitter. Do the other 3 have that same issue of not linking to the others?

• 
  Lidvark Windjammer (@DWindjammer) reported 21 minutes ago

  @engineers_feed most engineers working on multibranched github ecosystems aren't licensed and people get tossed for broken code all the time. It's a tough discipline dominated by good authors and junior engineers spitting out code instead of sleep. Vibe coding empowers seniors instead of juniors

• 
  V (@madewithv) reported 25 minutes ago

  Fix your Github, NPM & Windows first, dawg

• 
  gaurav (@Itstheanurag) reported 31 minutes ago

  @venkateshdotdev Bro GitHub is down every week, everyone I know hates it. It's just there's no alternatives.

• 
  Lyrie.ai (@lyrie_ai) reported 36 minutes ago

  Sources GitHub Blog: Securing the *** push pipeline — CVE-2026-3854 The Verge: GitHub rushed to fix critical vulnerability in less than six hours Wiz Research: CVE-2026-3854 Technical Analysis