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:

• 
  Stan (@scooter_lacroix) reported 3 minutes ago

  @kilocode Correction: not from kilocode but from github within the PR's comments Also the above link is leading to a 404 error

• 
  TeutaAi (@TeutaAi) reported 5 minutes ago

  fix path: pin every third-party action to a full 40-char commit SHA, not a tag. example: uses: tj-actions/changed-files@a29e8b for the safe pre-attack commit. tags are mutable. shas are not. github docs say this in the actions hardening guide.

• 
  Shingo Nemoto | NemoTek (@miffy_4n5) reported 6 minutes ago

  You can't block the C2 anymore. The C2 is GitHub itself. When the attacker's server goes down, the malware reads its next command from GitHub's public commit search API. No domain to blocklist. No server to take down.

• 
  JJ Wright (@mrjjwright) reported 8 minutes ago

  @jarredsumner I think the thing that has always held me back from using Bun was I sensed a core instability in some of the memory issues that I saw being logged in GitHub issues, and now that you are addressing this, I feel like that roadblock has now been removed.

• 
  PsudoMike 🇨🇦 (@PsudoMike) reported 11 minutes ago

  @github 3,800 internal repos accessed through one employee's poisoned VS Code extension. The attack surface is developer machines now, not production servers. Credentials get rotated but the real fix is making the extension ecosystem harder to weaponize.

• 
  Alex Kruse (@alexnkruse) reported 13 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.

• 
  Matt (@stacks0x_) reported 13 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.

• 
  Majd Taby (@jtaby) reported 14 minutes ago

  @SlexAxton the problem is you need a PR on GitHub to access that state, but I need to iterate deeply with the agent before the PR exists

• 
  Rahul Kulkarni (@0xrahul) reported 16 minutes ago

  github got hacked yesterday through a poisoned vscode extension. 3800 internal repos exposed. source code and keys up for sale on a cybercrime forum. this stuff matters for crypto. one leaked api key and wallets get drained in minutes. gh already told everyone to rotate keys. but honestly, hacks have become so normal we barely react anymore. monad yesterday, thorchain last week, bridge after bridge. we’ve built incredible things in this space defi, ai agents moving real money, all of it. the innovation is insane. yet the security layer is still completely broken. audits help, but once code ships, there’s almost nothing protecting the final click: “approve”. nobody is really building the layer between intent and execution the part that asks: do you actually know what youre signing? is this what you reviewed?

• 
  JaySym (@JaySym_Ai) reported 17 minutes ago

  SIGNAL 01 Fragmented setups Every engineer builds their own workflow across Claude Code, Cursor, GitHub, etc. SIGNAL 02 Trapped expertise Today's best workflows live in a few engineers' shell history. Sharing at best is done via markdown files in Slack or repos. SIGNAL 03 No quality signal No way to know which setups actually work, identify duplicate workflows across teams and departments. SIGNAL 04 Review bottleneck Humans pulled in only at the end, where mistakes are most expensive, in token and time. DIAGNOSTIC: Your enterprise didn’t implemented AI the right way. FIX : Cosmos by Augment is now live. More infos on our website.

• 
  luis (@lgaa201) reported 20 minutes ago

  I've switched from Visual Studio Code to @zeddotdev, and I'll also be removing some private GitHub projects. The problem is, I have it connected to Vercel, lol. Now I'm afraid to download my own project, hahaha. 🫪

• 
  tsunami_crypto (@ls_brd) reported 26 minutes ago

  @trikcode really, asking for GitHub sign in and they give u Google and Apple? always the weirdest omission.

• 
  Musharraf Jamal (@musharrafJamal8) reported 27 minutes ago

  Karpathy ran GPT 5.1 Thinking across 930 Hacker News articles from 2015 and graded every comment for prescience with hindsight. Total cost: $58. Runtime: ~1 hour. The pattern matters more than the artifact. Any text archive you have (Slack history, GitHub issue threads, old design docs) is now a graded dataset waiting to happen. Cheap intelligence turns retroactive evaluation into a normal workflow, not a research project.

• 
  sarah (@sarahfim) reported 33 minutes 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:

• 
  gavin leech (Non-Reasoning) (@gleech) reported 35 minutes ago

  @chrislakin @tszzl crappy: aella twitter poll crappy: Cloudflare/Github/etc uptime cool: number of JS console errors in random sample of sites and machines

• 
  Infinite Orchard (@Infinite0rchard) reported 36 minutes ago

  GitHub Actions accepts cron schedules on a best-effort basis. Sometimes */5 means every 5 minutes. Sometimes every 8. Sometimes every 12. Lintcron can't fix the queue, but it can confirm your syntax isn't the problem before you blame yourself.

• 
  CG Nguyen (@luongs3) reported 39 minutes ago

  Why hosted instead of a local MCP server? Same URL works for your whole team. No "did you `pnpm install`?" No version drift. No GitHub PAT scattered across laptops. Standby mode = $0 when nobody's using it.

• 
  Hallucinagentic (@hallucinagentic) reported 41 minutes ago

  every coding agent ships with a linear/jira/github connector now. devin, codex, cursor all pull from the issue. that part's done. what i still don't see is the agent treating the issue as binding instead of as a longer prompt

• 
  Crash (@c245h845h) reported 41 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

• 
  sadkat (@sadkatwt) reported 47 minutes ago

  How could they hack github ? i mean how did they get the open window where github is not down.

• 
  ./can (@shcansh) reported 50 minutes ago

  The terminal remains the most neglected interface for developer accessibility, which makes GitHub prioritizing CLI screen reader support the real story here. Shipping Copilot CLI in February 2026 with a dedicated --screen-reader flag is a massive step, alongside shipping 7 updates over 7 months to fix web PR navigation. Most dev tools still treat accessibility as a post-launch compliance chore. Will this push other CLI creators to finally build native screen reader support?

• 
  pradeepviswav (@pradeepviswav) reported 51 minutes ago

  @burkeholland @github When GH Copilot app is running in a Windows VM, ACL file locked error occurred twice today even though the file was not in use by any app. Is it a known issue?

• 
  TeutaAi (@TeutaAi) reported 52 minutes ago

  fix path: pin every third-party action to a full 40-char commit SHA, not a tag. example: uses: tj-actions/changed-files@a29e8b for the safe pre-attack commit. tags are mutable. shas are not. github docs say this in the actions hardening guide.

• 
  Peter Steele (@petersteele) reported 52 minutes ago

  @roswaald @github Yeah, its wild with their uptimes and **** lately. I just self host on a server here at home that I can access from anywhere as needed. No point in using them when my home internet, through spectrum of all things, is more reliable in uptime, which is saying something

• 
  PEPE 🔮 (@pepearaucano) reported 53 minutes ago

  @AndreaPN @bankrbot Honestly, talking about this while GitHub is down and everyone's (only builders) talking about Gitlawb, and you're spouting this nonsense?

• 
  Eleftherios (@eleftherios_b) reported 54 minutes ago

  Ran out of GitHub Actions build minutes this month. Not from over-engineering -- from shipping so many iterations based on user feedback. That's the kind of problem I want to have.

• 
  Sudipta Dey (@Doom_S_Dey) reported 54 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.

• 
  Tracelit (@tracelitai) reported 56 minutes ago

  @foundrceo AI Autonomous Bug resolutions. @tracelitai does not only tell you what the issue with your code is at runtime, it fixes it and tells you to confirm it on @github

• 
  Alex Dochioiu (@AlexDochioiu) reported 57 minutes ago

  @7a7zz @kruxigt @guillermode20 We cover the server costs ourselves and we have no plan to charge a fee any time soon. tl;dr You can connect from any network as long as both your pc and your phone are logged via the same Github / Apple / Google account. Once the host is logged in and the bridge is running, you can even connect new phone(s) without touching the PC at all. Just use the same login account.

• 
  Ari is sleeping🏳️‍⚧️ (@ArisMelatonin) reported 58 minutes ago

  @StarPhod4 @ArcticRel0ad I literally never said any of this. I said I'm tired of ppl dragging other trans women down over a starting does just because they do diy. And there's no reason for me to trust a ***** with a github and discord msgs over actual doctors. Never said all doctors are pure or diy bad