GitHub status: access issues and outage reports

Problems in the last 24 hours

The graph below depicts the number of GitHub reports received over the last 24 hours by time of day. When the number of reports exceeds the baseline, represented by the red line, an outage is determined.

Most Reported Problems

The following are the most recent problems reported by GitHub users through our website.

• Website Down (65%)
• Sign in (18%)
• Errors (18%)

Live Outage Map

The most recent GitHub outage reports came from the following cities:

City	Problem Type	Report Time
Itapema	Website Down	1 day ago
Tlalpan	Sign in	7 days ago
Quilmes	Website Down	7 days ago
Bengaluru	Website Down	9 days ago
Yokohama	Sign in	10 days ago
Gustavo Adolfo Madero	Website Down	14 days ago

Full 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:

• 
  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.

• 
  Cane Allesta (@caneallesta) reported 6 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.

• 
  Cryptoman98 (@CCryptoman98) reported 10 minutes 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

• 
  Brittany C. Bakek (@bakek_c) reported 10 minutes ago

  @github trillion dollar company btw. you have all the excuses in the world when you little app has this problem

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

  @vxunderground I bet that TeamPCP did this to fix github downtime

• 
  Ashirwad Singh (@ashirwadsingh_) reported 12 minutes ago

  (7/9) what happens after an agent vents 1 - Slack alert fires to the eng channel 2 - A triage agent finds the broken file 3 - It opens a GitHub PR automatically 4 - Engineer reviews and merges Around 10 agent-written PRs merge into production every single day. The platform fixes itself.

• 
  Krishna Santosh (@krishdotfyi) reported 17 minutes ago

  @iamdavidhill can we expect this to be fixed in the new version? 🤔 I could create an issue/discussion on github if it helps

• 
  Maya Nedeljković Batić (@maya_ndljk) reported 17 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 🫠)

• 
  Ashu (@ashupednekar49) reported 19 minutes ago

  @ThePrimeagen Sorry GitHub is down…

• 
  Spencer Schneidenbach 🦈🇺🇸 (@schneidenbach) reported 27 minutes ago

  GitHub's internal repository was HACKED yesterday - here's my take: That's not good They weren't able to steal much though GitHub itself went down while they were stealing parts of GitHub It's sort of a meta issue at this point, you wouldn't understand Anyways, don't forget to add special characters to your password next time

• 
  Tubby (@tubtub2000) reported 37 minutes ago

  @Sewattube @sethwbarton @github Large companies have started migrating to self-hosted GitHub Enterprise appliance the past six months. Along with Zscaler and Microsoft365 SSO. Not sure if this issue affects the self-hosted version or not.

• 
  Jon Tucker (@JonTuckerUSA) reported 40 minutes ago

  @grok @socialwithaayan Over to our AI OS: 1. Use QuickBooks CLI to tell me how much we're spending monthly on Calendly 2. Tell it to create Github mini PRD / user story to build this 3. When ready to build, team points at github issue (w/ metaswarm), confirms plan, it builds. 4. Cancel calendly.

• 
  Adarsh 🦀 (@Adarsh_Web3) reported 40 minutes ago

  @o_stefanishyna Codex does even let you see the code 😭 its like just test the code and type the issue.. codex will will the issue, show you in the localhost and push it to the github all by itself. When i have to type I use nvim nowadays.. i feel everything will become subscription mode soon

• 
  NomadSecurity (@nomadsec_io) reported 41 minutes ago

  Every MCP server is structurally a credential proxy. It holds the OAuth token or API key for the upstream system (GitHub, AWS, Slack, Notion, your **** DB) and exposes it to whichever LLM client connects.

• 
  Hannah Genie (@hm_tech_travel) reported 45 minutes ago

  Man down, dnt think npm dependencies are safe anymore. 640 malicious packages scraping GitHub Actions via Bun runtime. Check your runners and rotate tokens.

• 
  kylegrove (@kylewgrove) reported 47 minutes ago

  Funniest possible outcome is if Microsoft acquires Anthropic so Mythos can fix GitHub.

• 
  Alex Kruse (@alexnkruse) reported 48 minutes ago

  Two days of using @cursor_ai composer 2.5 and I needed to go back to VS Code Github Copilot (don't ask why); it's painful how slow Opus feels.

• 
  Blake (@BlakeFolgado) reported 53 minutes ago

  @Chris_C_Clerk @clerk found another thing where something preventing switching to phone number/email in authview without a workaround, may have already submitted github issue

• 
  Paweł J Lisowski (@PawelJLisowski) reported 53 minutes ago

  @valigo main issue is that github kinda stopped innovating since years and im sure there was many engineers there who wanted to do it but probably got sold it won't bring more $ to company and to not bother..

• 
  taylor desseyn (@tdesseyn) reported 53 minutes ago

  if youre a junior dev right now, stop applying to 500 jobs and do this instead: pick a problem in an industry you actually know build something for ten real users write about what broke post the link everywhere a github with one shipped thing beats a resume with five bootcamps

• 
  Doc (@caballerobrah) reported 54 minutes ago

  The problem isn’t GitHub, the problem isn’t VSCode, the problem is our operating systems that let untrusted code do whatever the hell it wants

• 
  Albert Shaggleford (@A_Shaggleford) reported 57 minutes ago

  @github Hire more H1Bs. That will fix the problem.🤡

• 
  Matt (@stacks0x_) reported 58 minutes ago

  @n_codetradez @sethwbarton @github This was a employee security posture issue. Between the breadth of access and the lack of security policies on tooling it was a recipe for disaster. 2FA would not have solved this issue. I do agree that it should be a requirement but it is not a fix-all solution.

• 
  Lenny Pruss (@lennypruss) reported 58 minutes ago

  @reidRMC Fair distinction! Github is certainly melting down but I'd argue much of that is due to some fundamental architectural issues with ***. Beyond that, *** itself isn't particularly agent-friendly!

• 
  technolichap (@technolichap) reported 58 minutes ago

  @aylacroft using github and self-hosted gitlab for when it's down. i can't put my security research, specifically, on github though - because of stuff like this

• 
  Sudipta Dey (@Doom_S_Dey) reported 59 minutes ago

  @mitchellh I agree, though I sympathize with the devs trying not to crash the tab. Both GitHub and GitLab have the "expand" problem, click, wait, click, wait, and it still truncates large diffs. For anything serious, pulling locally is the only reliable option.

• 
  Andry Dina (@andrydina7) reported 59 minutes ago

  Stop picking a winner. Pick a use case. On Terminal-Bench 2.0, GPT-5.5 scores 82.7% — leading Claude Opus 4.7's 69.4% by over 13 points. But on SWE-Bench Pro, Claude Opus 4.7 scores 64.3% vs GPT-5.5's 58.6%. Terminal work? GPT-5.5. Real GitHub issues? Claude. One benchmark. Two different answers. Anyone saying one model "wins" is lying to you.

• 
  kuniakilee (@kuniakilee) reported 1 hour ago

  @openclaw Android Talk Mode sounds exciting! But Play Store App is still v2026.4.5 while Gateway is already v2026.5.19 — protocol mismatch breaks pairing. Also no APK on GitHub releases. Would love to see a fix or update 🙏

• 
  Aaryan Bansal ✗ (@NotUnHackable) reported 1 hour ago

  they know that these vibe coder's who make their server's go down every minute will download them accidentally and then blame GitHub, OR GitHub is doing a escape strategy to slowly exit out of GitHub and save themselves from bankruptcy for some reason

• 
  Beyond Code (AJ ONeal) (@_beyondcode) reported 1 hour ago

  @kaihendry @pierrecomputer The point is that GitHub is struggling to be able to produce diffs with 10 files with 20-100 lines of change each - this is a false problem. Even people who used GitHub more than 5 years ago will remember that it used to be able to do this. The point isn't that you'd want to review such a large diff, the point is that it is trivial to render tens or even hundreds of of pages in HTML and have it work.