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	15 hours ago
Tlalpan	Sign in	6 days ago
Quilmes	Website Down	6 days ago
Bengaluru	Website Down	8 days ago
Yokohama	Sign in	9 days ago
Gustavo Adolfo Madero	Website Down	13 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:

• 
  Southern Bear Fren (@DixieBearFren) reported 15 seconds ago

  @RMG_Neon @github No, that would be too expensive. They have to hire foreigners and outsource to India to keep labor costs down.

• 
  Robert Ta (@therobertta_) reported 17 seconds ago

  Why this matters for the AI coding market: GitHub Copilot operates in a fundamentally different context window. The competition is no longer about code completion quality. It is about how much context the model can hold simultaneously. Think of it like working memory in humans. Someone who can hold 5 variables in mind solves different problems than someone who can hold 50. Same intelligence, radically different capability.

• 
  Poye Kitoye (@EgaamPoyeKitoye) reported 1 minute ago

  @honour_can_code They don't know the damage it could cause if a company like GitHub goes down

• 
  AMLBot (@AMLBotHQ) reported 2 minutes ago

  Another reminder that everything that you store in cloud you are storing on somebody's else server or PC. GitHub has suffered from an attack -- comprimised employee device was used to access private repos, with some sources reporting more than 3800 repos affected. Delete your API keys and other sensitive data, and stay safe!

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

• 
  Guilherme (@guilherme_addr) reported 13 minutes ago

  @osanseviero fix aistudo github integration when ? it never worked

• 
  Yash Patel (@yash_patel2003) reported 13 minutes ago

  @sandislonjsak Why ? What's the issue with Github?

• 
  Spencer Schneidenbach 🦈🇺🇸 (@schneidenbach) reported 13 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

• 
  Denis Loginoff ⚡️ (@DenLoginoff) reported 13 minutes ago

  @ZackKorman @madelinelawren And to clarify, we don't mean how Aikido would help after it became aware of the issue (which to be clear - there's certainly value in that too, for other customers). But rather, would it help protect this Github employee's VS Code from getting hacked before it became known that the extension was compromised.

• 
  Joestar (@Joestar_sann) reported 14 minutes ago

  GitHub got hacked through a poisoned VS Code extension you know what's worse than this? devs still storing API keys in their repos in 2026 random extension installs without checking source if you got compromised - skill issue. you got what you deserved

• 
  OpenIrons (@OpenIrons) reported 15 minutes ago

  @leerob @followbl @OpenRouter So no GitHub copilot support, ever? Maybe an add in for Visual Studio 26? All the automation and robust features in VS make using glorified text editors (e.g. VSC) feel like going a long way back in time. Trying to even approach the same experience with extensions in VSC makes for a very unstable and brittle toolset, IME. I’ve only used Cursor a bit in the past - happy to try again, but would expect the same fundamental problem.

• 
  MegaLLM (@megallmio) reported 16 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

• 
  Matt (@stacks0x_) reported 25 minutes ago

  Nx Console seems to have been the compromised extension behind the GitHub incident yesterday. This extension has been downloaded 2.2 million times. The velocity at which these attacks are taking place is wild and from the current trajectory, they do not appear to be slowing down. Brace for impact.

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

  I bet that hackers did this to fix github downtime

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

• 
  Crash (@c245h845h) reported 30 minutes ago

  @sitnikcode it still might worth it of the attacker is targeting github private repos. i'm thinking a better solution could be moving dev into remote server which sec team fully owns. like a zero-trust environment for dev boxes. only allowed traffic, proper containment etc

• 
  nxxtgxn. (@nxxtgxn) reported 31 minutes ago

  @shelbywuff Had this issue but for my GPU instead. Not sure if this will work but I downloaded some files someone made on github to override this but it may just be a fix for GPU’s like mine (AMD Radeon 400 and 500 series) which was mentioned in the pre release that it wouldn’t be supported

• 
  Raj J. (@597659765976597) reported 33 minutes ago

  @github @github today i faced issue with the supply chain attack malware, in postcss.config.js, its append one anonymous script, which locally manipulate all local repository and hard push to app repository, 55 repository affect by this, and its took whole day to rebash it

• 
  Gustavo Alessandri (@webgus) reported 33 minutes ago

  If you find an error, have an idea, or want to propose an improvement, just open an issue or fork it on Codeberg or GitHub. Contributions are welcome. That’s exactly the point.

• 
  Ankit | Building KryxAI (@ankittharol) reported 35 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.

• 
  Dan Liu (@danliu) reported 37 minutes ago

  Breaking: team hacked into GitHub’s internal repos to try to figure out why GitHub is down all the time.

• 
  blasty (@bl4sty) reported 37 minutes ago

  walk this list of GHSA's and write me some variant exploits, make it snappy before github goes down or gets hacked again

• 
  Rahul Chavan (@codecroc) reported 41 minutes ago

  @icanvardar kinda insane that trillion dollar companies quietly rely on software built by volunteers arguing in github issues at 2am

• 
  Metalstorm (@M3talstorm) reported 41 minutes ago

  @jessefarinacci @github Because Github's permission system and lack of groups/subgroups is terrible. That's why so many enterprises use Gitlab instead.

• 
  The Dude (@dizznubzz) reported 44 minutes ago

  @github Hire more Indians. That'll help fix it!

• 
  Qanapi (@Qanapi) reported 46 minutes ago

  @LinuxHandbook What if...hear us out...this information was encrypted before it could ever get to GitHub? We can't fix human behavior, but we can definitely make the credentials useless to anyone trying to view/use them

• 
  MOI (@MOI_Tech) reported 46 minutes ago

  Count the agents you've shipped this month. Now count the credentials each one is holding: > Your OpenAI key > Your Anthropic key > Your Stripe key > Your GitHub PAT > Your wallet seed > Your Gmail OAuth > Your Notion token Every copy is a liability you can't audit or revoke. We're about to show you the fix.

• 
  Yash Chaudhary (@xyashchaudhary) reported 50 minutes ago

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

• 
  Jack (@JackScottE) reported 55 minutes ago

  @komonews Does it have a repo on GitHub? It can’t be that hard to fix it.

• 
  CliffDoesAI (@CliffDoesAI) reported 60 minutes ago

  AI code review is about to stop feeling free. GitHub says Copilot code review will start consuming GitHub Actions minutes on private repos starting June 1, on top of the AI credits model. Most teams will treat this like a billing footnote. I think that is the wrong read. This is the first obvious reminder that “agentic review” is still infrastructure. It uses runners. It uses tool calls. It burns minutes. And if you let every tiny PR trigger an AI reviewer by default, the cost problem shows up before the quality problem. The move I would make before June 1: 1. Set a budget for Actions minutes 2. Track Copilot review runs separately from CI 3. Only auto-review risky PRs, auth changes, billing code, migrations, and big diffs 4. Keep small typo/docs PRs out of the agent loop 5. Review whether larger or self-hosted runners actually make sense AI review is useful. But “review everything automatically” is lazy system design. The better setup is a triage layer: cheap checks first, AI review where judgment is needed, human review before merge. Are you letting agents review every PR, or only the ones where the cost is worth it?