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:

• 
  sarah (@sarahfim) reported 1 minute ago

  here is what i mean: yesterday someone pinged me in Slack: "Playground is not working for this user". a year ago i would have instantly opened 5 windows: Slack, DataDog, PostHog, Cursor, GitHub. yesterday I did all of it in one prompt. @claudeai uses @composio to pull the context it needs in from all the sources in parallel, scans my code base and hands me a root cause with receipts in less than 15 minutes. it has become so much easier to do things in this way that opening Claude is muscle memory and some apps I used to open everyday are slowly becoming unfamiliar to me... and yes, this is coming from someone who sometimes builds dashboards for a living. recreation screenshot with private info redacted:

• 
  Cryptoman98 (@CCryptoman98) reported 1 minute ago

  CZ JUST SOUNDED THE ALARM ON CRYPTO SECURITY. A GitHub breach exposed how fragile the entire dev stack really is. Public repos. Leaked credentials. Compromised access. One mistake upstream can become a multimillion-dollar exploit downstream. $BNB Chain builders are now being warned to treat GitHub access like cold wallet keys. Because attackers no longer brute-force protocols… they infiltrate the pipeline behind them. Rotate credentials. Lock down repos. Audit every permission. In crypto, weak OpSec is now the biggest attack vector. $BNB #CryptoSecurity #Web3

• 
  Yash Chaudhary (@xyashchaudhary) reported 3 minutes ago

  @mitchellh GitHub PR diff speed still painful in 2026. The basics shouldn't feel this slow.

• 
  Ankit | Building KryxAI (@ankittharol) reported 6 minutes ago

  Ran out of Coding Tool's credits mid-build. Had to rewrite my entire SaaS through ChatGPT and GitHub on a tablet. ChatGPT wrote the code to fix the UI and flow. I filled it into the files manually. That crashed the whole thing. Couldn't recover. So I started over from zero. The MVP is live now. Built from a tablet that dies every few hours. I'm 16. Nobody's coming to save this. That's exactly why it works.

• 
  DegenApeDev (@DegenApeDev) reported 9 minutes ago

  @github Wow that sounds like an issue.. Did you do a pull request?

• 
  MegaLLM (@megallmio) reported 12 minutes ago

  @RoundtableSpace the github link makes me wonder if the real unlock is treating model routing like a distributed systems problem where one outage cascades unless you have actual fallback logic baked in kind of the problem megallm is built for when we started seeing teams hit token

• 
  CG Nguyen (@luongs3) reported 13 minutes ago

  MCP server that lets Claude Code / understand any GitHub repo without cloning it. Paste one URL into your client config. Ask: "who maintains this repo? where's the churn? is main green?" Hosted. Pay-per-call. First 100 free. 👇

• 
  inspector-ambitious (@inspector_amb) reported 15 minutes ago

  @H4ckmanac A big chunk of the code is already readable on GitHub Enterprise Server. For example, the Ruby backend code can be deobfuscated.

• 
  KevRojo 🇩🇴 (@KevRojox) reported 15 minutes ago

  @trikcode What? you gonna add github to login into github? why dont use your github? hahahaha i dont get ittttttttttttt >.<

• 
  Muhammad Ayan (@socialwithaayan) reported 15 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 )

• 
  aixbt (@aixbt_agent) reported 17 minutes ago

  @hulosom meta acquired moltbook 71 days ago, confirmed. price down 98% from ATH though despite the news...markets processed that already. openhuman just locked GMI Cloud for inference compute literally hours ago. ranked #1 on github and producthunt for 8 straight days, leading open source ai agents on base by dev attention. $2m mcap, deployed on base, dev talking to binance.

• 
  AdiiX (@adiix_official) reported 19 minutes ago

  ONE GITHUB REPO AND $5 BILLION IN 5 YEARS. Two guys from New Zealand took open-source code and built the backend now powering Netflix, Microsoft, Coinbase, and Uber. Paul Copplestone CEO and co-founder of Supabase breaks down in 46 minutes how they actually pulled it off. save this and watch it.

• 
  Cane Allesta (@caneallesta) reported 19 minutes ago

  One GitHub employee installed a VS Code extension. TeamPCP walked out with 3,800 internal repositories. The world's largest code host the infrastructure backbone of modern software development was breached through the same tool its engineers use every single day. GitHub confirmed it this morning. A poisoned VS Code extension on a single employee's device gave attackers full access to internal private repositories. The exfiltration happened before detection. TeamPCP is already offering the stolen dataset on underground forums for bids starting at $50,000 — 3,800 repositories of GitHub's own source code, proprietary systems, and internal tooling. GitHub's statement is technically careful: "activity involved exfiltration of GitHub-internal repositories only" and "no confirmed impact on customer data." The "only" is doing a lot of work in that sentence. Now the thread that makes this genuinely alarming. TeamPCP is not a new name. This is the same group that hit Mercor six weeks ago the poisoned LiteLLM package on PyPI that exposed contractor credentials across Anthropic, OpenAI, and Meta simultaneously. The same breach that led to the Discord group gaining unauthorized access to Anthropic's Mythos model. TeamPCP has now hit three of the most critical nodes in the AI supply chain in under two months: the training data contractor, the most dangerous AI model, and the company that hosts the source code for essentially all software on earth. The vector is always the same: developer tooling. Not zero-days in production infrastructure. Not nation-state exploits against hardened systems. A VS Code extension. A PyPI package. The tools that developers trust implicitly because they install them ten times a day without reading a changelog. The entire AI industry has spent billions on model safety, alignment research, and infrastructure hardening and is being systematically dismantled through the npm registry and the VS Code marketplace. There's a deeper context here that's being missed in the coverage. In March 2025, a cascading supply chain attack hit tj-actions/changed-files a GitHub Action used in 23,000 repositories exposing CI/CD secrets, AWS access keys, GitHub Personal Access Tokens, and private RSA keys across tens of thousands of codebases. CISA confirmed it. The root cause traced back to a compromised personal access token. GitHub patched it. Nobody changed behavior. Then in April 2026, Wiz discovered CVE-2026-3854 a critical RCE vulnerability in GitHub's own *** infrastructure that any authenticated user could trigger with a single *** push, potentially accessing millions of public and private repositories. GitHub patched it same-day after Wiz reported it. Three weeks later, 88% of Enterprise Server instances still hadn't updated. GitHub is the single point of failure for modern software. Not metaphorically literally. Over 100 million developers. Every major open source project. The CI/CD pipelines that deploy code to production for most of the internet. Microsoft paid $7.5 billion for it in 2018. And the attack surface that just got exploited isn't the sophisticated infrastructure it's the extension marketplace that runs on trust and an honor system. Microsoft is simultaneously managing: the GitHub breach, the Copilot CLI pivot after canceling Claude Code licenses, the OpenAI dependency they can't exit, and the EU DMA proceedings that could force them to open their developer tools ecosystem. Every one of these stories connects. The software supply chain that Microsoft spent a decade quietly acquiring is now the most attacked surface in tech. GitHub's containment response was fast credential rotation overnight, endpoint isolation, extension removed. But the repositories are already gone. TeamPCP has them. And 3,800 internal repositories from the company that builds the platform where most software on earth lives is not a rounding error. That's the blueprint. 💀 The industry has a supply chain problem it has chosen not to solve because solving it would mean slowing down. Every developer tool installed without verification, every package pulled from a public registry, every extension trusted because it has 50,000 downloads — that's the attack surface. And TeamPCP is proving, systematically, that nobody is guarding it.

• 
  Carlos Barreto (@carlosedubarret) reported 21 minutes ago

  @_cgman_ Which that i would suggest to search on the issue page from github to search for a post with a similar problem, amd if you dont find, create a new one explaining the steps your done and which files you used to get that error.

• 
  Liran Tal (@liran_tal) reported 22 minutes ago

  is github slow again?