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:

• 
  Rodger Dodger (@Sewattube) reported 1 minute ago

  @OrdinaryGamers If I was in charge of GitHub I would be updating my résumé. Constant stream of problems.

• 
  Jason Nunnelley (@jnun) reported 1 minute ago

  I’ve never met a security first investor. Capital drives risk, not safety. GitHub failed to maintain a basic corporate tool approval chain. This is IT security 101. It’s a culture problem. Now, keep this in mind. That same attitude prevails at AI companies.

• 
  DRUMEE (@DrumeeOS) reported 2 minutes ago

  @julianor Another day, another big tech breach. GitHub internal repos stolen and listed for sale. Your IP, keys and secrets aren’t safe on someone else’s server. Self-hosting isn’t optional anymore.

• 
  Satoshi Club (@esatoshiclub) reported 4 minutes ago

  🚨 BREAKING: GitHub has confirmed a breach of its internal repositories. The attacker compromised an employee device through a poisoned Visual Studio Code extension. From that single endpoint, they pivoted into internal GitHub repos, dumped secrets, and walked out with what they claim is around 4,000 private repositories of source code and internal organization data. The threat actor, TeamPCP, listed everything for sale on the Breached forum yesterday with a floor of 50,000 dollars. Their stated terms are blunt. One buyer, no negotiation, and if no one pays the entire dataset gets leaked for free. GitHub says it removed the malicious extension version, isolated the device, rotated critical secrets, and activated incident response. The company maintains there is currently no evidence of impact to customer repositories, enterprises, or organizations stored outside its own internal infrastructure. The attack vector is the part worth sitting with. This was not a flaw in GitHub the platform. It was a poisoned extension in the VS Code marketplace, executed on a developer laptop, used to reach everything that laptop could reach. The same week, two popular GitHub Actions workflows (actions-cool/issues-helper and actions-cool/maintain-one-comment) were compromised through tag manipulation to exfiltrate CI/CD credentials, and a critical RCE vulnerability in GitHub itself, CVE-2026-3854, was patched after researchers showed it could be triggered with a single *** push. Three separate incidents, one consistent message. The platform is hardened. The supply chain around it is the soft target. For anyone building on GitHub right now, the immediate checklist is simple. Audit installed VS Code extensions. Pin GitHub Actions to commit SHAs rather than tags. Rotate any tokens, deploy keys, or secrets that could have touched a compromised environment in the last two weeks.

• 
  Anotida Msiiwa (@anomsiiwa) reported 5 minutes ago

  @github A Microsoft text editor extension taking down internal Microsoft code repositories is a brutal supply chain loop.

• 
  Dwayne (@CtrlAltDwayne) reported 7 minutes ago

  There's a lot of focus on Npm being a supply chain exploit risk and all of the problems it has had. If hackers got access to GitHub source code, this could possibly open the door for supply chain attacks even more damaging than the Npm ones we've seen.

• 
  David Jennings (@ChilliDoor) reported 9 minutes ago

  I just remembered that MS owns GitHub and by extension NPM, so basically all of these issues ultimately stem from MS incompetence.

• 
  Majid (@majid_ishag) reported 11 minutes ago

  @github What happened to GitHub?! Every month a major issue.

• 
  Fate (@alltheputs) reported 12 minutes ago

  @github 🔥 Replay Window Density The dangerous part of this breach is not the stolen code count; it is how much working authority remains inside the stolen snapshot after the defenders start rotating secrets. A poisoned editor extension does not need to beat GitHub’s servers directly if it lands on a machine that already carries internal trust. The surprising threshold is reached when stolen repositories contain more still-valid credentials than the response team can invalidate before an attacker can test them. That means a smaller code theft with slow secret rotation can be more dangerous than a larger code theft with near-instant credential invalidation. The pattern to expect is follow-on activity clustering around credentials that sit in boring internal tooling, build scripts, environment examples, and automation glue rather than around the most famous repositories. A useful test is to rank exposed repositories by how many live credentials they contain and how long those credentials survive after containment. If follow-on attacker activity tracks that survival-ranked list better than repository importance or repository count, the real breach unit is the replay window, not the repo.

• 
  faizco. (@PhaResearcher) reported 13 minutes ago

  🚨BREAKING: GITHUB JUST DISCLOSED AN ACTIVE SECURITY BREACH. Someone got into GitHub's internal repositories without authorization. GitHub hosts the source code for millions of companies, governments, and developers worldwide. Internal repositories are where the walls are supposed to be thickest, where GitHub stores its own code, its own infrastructure, and potentially the keys to everything built on top of it. They say customer data appears unaffected for now. But the investigation is still live and they are actively monitoring for follow-on activity, which means whoever got in may still be moving. This is not a small incident. GitHub is the backbone of global software development. A breach of its internal infrastructure is not just a GitHub problem, it is a problem for every company whose code lives there, every developer who trusts it with their work, and every product built on top of it. The most dangerous part of any breach is not what they took on the way in. It is what they planted while they were inside. Watch this one very closely.

• 
  tcpdump (@dump_tcp) reported 17 minutes ago

  @IntCyberDigest should we take the forum down where there advertising it at? #github #teampcp #hacked

• 
  Wurt.app 🍄 (@WurtApp) reported 17 minutes ago

  @github Not a good look when your entire site has been breached, data copied in its entirety top to bottom, and already being sold on the dark web and you can’t still can’t figure out how they did it, no logs of any kind, so you have no way to fix it. Perhaps this is karma for training your secret model on private repository code

• 
  irshit (@irshit0) reported 19 minutes ago

  @nirajxdev See github having so much trouble

• 
  🏆🇧🇷💎Jack Hunter 💎 🇧🇷Ⓜ️⚛️🎖️🥇💫 (@GemsHunting_8) reported 24 minutes ago

  @Srikanthh998 @github No problem if we use @gitlawb

• 
  Craig (@CraigChaotic) reported 24 minutes ago

  @2600Hz_ @github I’m the same, I keep getting pinged for codes to login