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:

• 
  Majid (@majid_ishag) reported 6 minutes ago

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

• 
  21st Century Digital Boy (@TonhaoSemAcento) reported 7 minutes ago

  I bet that hackers did this to fix github downtime

• 
  Praveen Kumar Verma (@Alacritic_Super) reported 9 minutes ago

  @forgebitz Add these as well - npm package compromised - AI generated 4000 lines nobody understands - cloud bill costs more than payroll - GitHub outage breaks deployment - Docker image has hidden malware - production secrets leaked in logs - junior dev merged AI slop at 2am - entire company depends on one unpaid open-source maintainer - CI/CD pipeline broken for no reason - Kubernetes config written by ancient demons - temporary fix running production for 4 years - no documentation anywhere - and somehow the app still works

• 
  Roy (@__roycohen) reported 9 minutes ago

  It's the year 2027. You wake up, Github got hacked for real this time. All credentials got swiped. No problem, you self host now. Checked your Gmail, only 5 phishing emails in the inbox, no big deal. Check the GCP bill, sigh of relief as it's only $50k, not 500k

• 
  Salvo (Kyle) (@BroadsideCode) reported 14 minutes ago

  @MosheTov This was the final straw for me. All repos ripped down, keys revoked. I'm done with them. **** GitHub. It's a long story but this is a great reason for me to leave.

• 
  NightHawk (@Wh1t3Wh1rlWind) reported 15 minutes ago

  @github Is there anyway you can tell us which VS extension is causing the issue so we can get our company IT Security team aware to block the extension.

• 
  direct_quote (@quote_direct) reported 15 minutes ago

  @anshuc @github slow clap...

• 
  Wendy Wee (@wendyweeww) reported 16 minutes ago

  @METR_Evals Not downplaying the dangers, but shouldn’t it be statistically expected for them to routinely violate constraints if the training data they’re pattern matching and recombining from (perhaps from code forums, github issues, stack overflow, etc) statistically lead to those actions?

• 
  NamasteDev by Akshay Saini (@namastedev_) reported 17 minutes ago

  Spent 2 weeks perfecting my resume. Changed fonts Tweaked bullet points Made it "ATS-friendly." Still no interviews Then realized:My resume wasn't the problem My lack of proof was ❌Perfect resume, empty GitHub ❌Great format, zero projects ❌Amazing design,no online presence

• 
  Darren (@CorboDT) reported 18 minutes ago

  @TsengSR @github I’m thinking security by obscurity—whitespace for the client and Malbolge on the server. [ Frontend: Whitespace ] ---> ( HTTP ) ---> [ Backend: Malbolge ] (Invisible Zero-Byte UI) (Self-Encrypting Ternary Hell) - 100% immune to reverse engineering - Zero-byte bundle sizes - Nobody can steal my code (including me, tomorrow)

• 
  Muhammad Ayan (@socialwithaayan) reported 19 minutes ago

  Holy sh*t... a company that raised $32M just open sourced their entire product for free. It's called cal .diy. The Cal .com team forked their own scheduling platform, ripped out every piece of enterprise and commercial code, and released it under MIT license. 43.6K GitHub stars. And counting. Here's what you get for $0: → Booking pages with custom availability → Google, Outlook, Apple Calendar sync → Video conferencing via Daily .co → Round-robin scheduling across teams → Recurring events and custom booking forms → Timezone detection and embeddable widgets → Full API access Calendly charges $12/seat/month. SavvyCal charges $12/seat/month. Cal .com's hosted version starts at $15/month. cal .diy does the same thing for nothing. No license key. No feature gates. No user limits. No seat pricing. Self-hosted on your own server. Your scheduling data never leaves your machine. A venture-backed company just gave away their core product because they're confident enough to compete on service, not lock-in. That's the most dangerous kind of open source. 100% Open Source. MIT License. ( Link in comments )

• 
  Team Nitro (@nitromachines) reported 23 minutes ago

  @github Patch the breach, ship the fix, keep building 🔥

• 
  pnf (@yopnfdev) reported 26 minutes ago

  so you mean to tell me github gets HACKED as railway also goes down. WTH is going on with these so called company's their hiring bots / overseas to control their main infrastructure

• 
  Ben Dickson (@bendee983) reported 30 minutes ago

  Mass layoffs "because of AI" Most companies not seeing AI productivity yet Constant server outages at GitHub, Amazon, etc., caused directly and indirectly by AI Yet we're all freaking out because AGI is coming and we will be out of jobs

• 
  Satoshi Talks (@Satoshi_Talks) reported 31 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.