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:

• 
  OpsWorker Team (@OpsWorker_ai) reported 8 minutes ago

  Connect GitHub or GitLab and OpsWorker automatically correlates alerts with recent code changes. Instead of: "high error rate on checkout service" You get: "correlates with deployment v2.3.1 pushed 14 minutes ago"

• 
  ./can (@shcansh) reported 10 minutes ago

  The terminal remains the most neglected interface for developer accessibility, which makes GitHub prioritizing CLI screen reader support the real story here. Shipping Copilot CLI in February 2026 with a dedicated --screen-reader flag is a massive step, alongside shipping 7 updates over 7 months to fix web PR navigation. Most dev tools still treat accessibility as a post-launch compliance chore. Will this push other CLI creators to finally build native screen reader support?

• 
  Dylan (@df00z) reported 10 minutes ago

  I don't know if doubling down on failure is brave or silly. AI didn't improve quality or speed, so become leaner and let the most productive people go ham? I guess this will be a case study. Haven't there been enough case studies? GitHub went to hell. Microsoft is trying to fix Windows from AI slop damage.

• 
  Rahul Kulkarni (@0xrahul) reported 12 minutes ago

  github got hacked yesterday through a poisoned vscode extension. 3800 internal repos exposed. source code and keys up for sale on a cybercrime forum. this stuff matters for crypto. one leaked api key and wallets get drained in minutes. gh already told everyone to rotate keys. but honestly, hacks have become so normal we barely react anymore. monad yesterday, thorchain last week, bridge after bridge. we’ve built incredible things in this space defi, ai agents moving real money, all of it. the innovation is insane. yet the security layer is still completely broken. audits help, but once code ships, there’s almost nothing protecting the final click: “approve”. nobody is really building the layer between intent and execution the part that asks: do you actually know what youre signing? is this what you reviewed?

• 
  Nullspice_ (@nullspice_) reported 14 minutes ago

  @flipper_net Feels like an "all take and no give" type relationship lately with your community. From the outside, it looks like F0 Github development has died or frozen with 0 explanation to anyone involved. Hard to feel good when it feels like extracting free work and not working *with us*

• 
  13F Pro (@13F_Pro) reported 18 minutes ago

  Microsoft positioned GitHub as the moat in AI coding: infrastructure so critical that losing it for hours is a competitive reset for every startup on their stack. Except infrastructure that goes down isn't a moat, it's a liability. $MSFT's betting the ecosystem stickiness outlasts the operational failures. History says that's a bad bet.

• 
  cogsec (@affaanmustafa) reported 23 minutes ago

  "Like imagine being able to price the impact of a paper before everyone knows it matters. Or price academic impact without citations. Or price open-source value without MRR. Because there is an epidemic of fake GitHub stars, fake repo history, all of that. But we still know some repositories are actually valuable. They create economic output. People use them. They save time. They replace other software. They matter. But how do you price that? Right now, you almost can’t. You can say, “I feel like this is working.” You can say, “This has value.” You can maybe put some multiple on growth or usage. But there is no real way to make that value liquid." I have a scattershot of metrics, various revenue streams that act differently, for example native stripe subscriptions for your devtool / app (ECC-Tools), the sponsorship revenue, the github native revenue, downloads from github or other avenues, the growth and usage of the repo itself (stars, forks, PRs, issues, contributors, discussions ...), whats the value of the "ECC" umbrella itself? How do you quantify the value of everything all together, you have metrics of course, MRR, conversion, but MRR depends on where its coming from theres more implied depending on if its for a product or via sponsorships, downloads vary with clones, forks, plugin installs, npm installs, its hard to even track or quantify the impact downstream. There's value in *** to price complex and subjective things like this, for many things, there's well established data, ML models and pricing models that have existed forever, but for the new world and where we are headed that isn't super clear.

• 
  Mathias Onea (@mathiasonea) reported 24 minutes ago

  @JonBuildsHQ - 200 followers (1 person away) - automated bugfix pipeline (sentry -> notify github -> create issue -> codex pick up issue -> create PR)

• 
  slash1s (@slash1sol) reported 28 minutes ago

  HARVARD RELEASED A 65-MIN MASTERCLASS ON *** & GITHUB BECAUSE VIBE-CODERS STILL DON'T KNOW HOW TO COMMIT 1 hour and 5 minutes of raw, no-nonsense version control architecture from the creators of CS50. -> The moment you watch it, you realize why most modern developers are breaking their production branches. Every tier-1 tech company is now filtering candidates who can't handle basic merge conflicts. *** isn't a "nice-to-know" anymore -> it's compliance. Your AI can write the code. That wasn't the problem. The problem is you don't know how to merge it without breaking the repo. Don’t forget to bookmark it.

• 
  PsudoMike 🇨🇦 (@PsudoMike) reported 29 minutes ago

  @github 3,800 internal repos accessed through one employee's poisoned VS Code extension. The attack surface is developer machines now, not production servers. Credentials get rotated but the real fix is making the extension ecosystem harder to weaponize.

• 
  kara Sune (@_kendev) reported 30 minutes ago

  If your only fix for a bad merge conflict is deleting the folder and re-cloning from GitHub, it’s time to look under the hood.

• 
  Peter Steele (@petersteele) reported 32 minutes ago

  @roswaald @github Yeah, its wild with their uptimes and **** lately. I just self host on a server here at home that I can access from anywhere as needed. No point in using them when my home internet, through spectrum of all things, is more reliable in uptime, which is saying something

• 
  ./can (@shcansh) reported 37 minutes ago

  Organizing work across hundreds of repositories is usually a mess of duplicate labels, which is why GitHub is forcing structure with org-level issue fields. By defining 4 typed fields like Priority and Effort at the organization level, over 1,000 early adopter orgs are already automating workflows and using Copilot to migrate. Is this enough to finally make Issues work as a true project database, or is the system still too basic?

• 
  Maya Nedeljković Batić (@maya_ndljk) reported 37 minutes ago

  @3266miles @karrisaarinen @linear I'm guessing this is a table created via API/MCP server/synced with GitHub and not in the app? We try to make them full-ish width now in app, the programmatic side still needs work. (I'm kidding, all of it needs work 🫠)

• 
  Abhishek Doshi 👷‍♂️ (@AbhishekDoshi26) reported 38 minutes ago

  The Problem: LLMs can generate a GitHub Actions workflow in seconds. But they don't inherently understand your Dart dependency graphs, transitive path filters, or monorepo structures. They write the file, but over time, your repo drifts and things break. 📉 (2/n)