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

• 
  Renee Bad (@NegroLeagueChew) reported 6 minutes ago

  @github Hire some more Indians, that ought to fix the problem

• 
  Christoffer Bjelke (@chribjel) reported 12 minutes ago

  @0xRizzler they're using github issues at least

• 
  k4yaba (@k4yaba) reported 16 minutes ago

  Another thing worth mentioning is the developer. Most people look at the product. I look at the builder. The creator behind OpenReel (@python_xi ) has logged nearly 8,000 GitHub contributions in the last year alone, contributing across dozens of repositories while actively shipping updates to OpenReel. Based on the public activity, that's not someone experimenting with an idea on weekends. That's someone obsessed with execution. While many projects spend months talking about roadmaps, OpenReel has been pushing releases, features and improvements at a pace that's difficult to ignore. Its a strong signal that developer is paying attention. What stands out isn't just the consistency. It's the ambition. Building a browser-native alternative to traditional video editing software is not a simple CRUD app or AI wrapper. You're dealing with rendering pipelines, GPU acceleration, media encoding, timeline systems, audio engines, animations and real-time performance constraints. That's a difficult category to execute in. Yet the velocity coming from the repository suggests the dev isn't afraid of tackling hard engineering problems. OpenReel already includes things like multi-track editing, WebGPU acceleration, audio processing, effects, animations and AI-assisted features directly inside the browser. In crypto and startups people often talk about conviction. In open source, conviction is measurable. It's commits. It's releases. It's showing up every day and shipping. And when I see a builder with nearly 8,000 contributions in a year building in a category this ambitious, I pay attention. - Products can be copied. - Narratives can be copied. - Distribution can be bought. Relentless builders are much harder to replicate. That's one of the reasons I'm keeping OpenReel on my radar. 👀

• 
  The Dude (@dizznubzz) reported 18 minutes ago

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

• 
  Yash Patel (@yash_patel2003) reported 19 minutes ago

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

• 
  magusgenji (@MagusGenji) reported 20 minutes ago

  @anshuc @github The internal repos weren't hosted on GitHub, that way they can still fix it when they go down.

• 
  Meistar (@Meistar_TTV) reported 22 minutes ago

  @Hyperate_io Hi, the Window's Installer GitHub link is broken. Excited for this! Use Hyperate for my streams!

• 
  irshit (@irshit0) reported 23 minutes ago

  @nirajxdev See github having so much trouble

• 
  NamasteDev by Akshay Saini (@namastedev_) reported 25 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

• 
  Jacovia (@ItsJacovia) reported 30 minutes ago

  @joeychilson I just want to know what they’re going to do to prevent this from happening again. I am so tired of telling clients that the update is waiting on railway because railway is down and not syncing with GitHub, or they can’t access the the thing they pay me for for 6 hours because railway is down. @JustJake

• 
  Satoshi Club (@esatoshiclub) reported 30 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.

• 
  Adarsh 🦀 (@Adarsh_Web3) reported 32 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

• 
  Hiren F (@faldu_hiren) reported 32 minutes ago

  @github I hope someone can provide a PR for the fix. Unless that's compromised as well.

• 
  Crash Loop BackOff (@MLOpsCamp) reported 36 minutes ago

  Github continues to flail. At least they're copping to it, though it's not clear what steps they are taking at a more systemic level, given the plague of recent issues.

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

• 
  dalu (@dalu_hey) reported 40 minutes ago

  @grafana github is the issue I'm moving away from it

• 
  Joestar (@Joestar_sann) reported 42 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

• 
  Leon (@Leon_Defi) reported 42 minutes ago

  @LordOfAlts @github How many more "internal only" breaches before Microsoft actually locks this down?

• 
  Doc (@caballerobrah) reported 43 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

• 
  Mitchell Hashimoto (@mitchellh) reported 44 minutes ago

  This is why PR diff speed matters. This isn't a dunk on GitHub specifically, because GitLab, Forgejo, etc. are all equal or worse. But this is the kind of thing that drives me nuts, because this is a core workflow and its slow enough I literally take my hands off the keyboard. Btw, when my mouse jiggles on the left, its because the page is literally skipping frames and I'm instinctively shaking my mouse to see if it'll respond. And on the keyboard input you can literally here me finish typing before a letter even shows up. For someone like me who is an expert at these tools, my brain navigates the tool dramatically faster than it can keep up, and that is not good. The tool should not get in the way.

• 
  Jon Tucker (@JonTuckerUSA) reported 46 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.

• 
  Nobody (@jisoo_1995) reported 49 minutes ago

  @github You can fix the problem by hiring more indian

• 
  Origin (@orgn_official) reported 52 minutes ago

  GitHub was hacked through a malicious VS Code extension, and it wasn’t a sophisticated attack... It came down to trust in the IDE, and that detail matters more than you think if you are a developer. Here’s what you can learn from it:

• 
  Lina 🦅 (@XNXX_EN) reported 54 minutes ago

  @LordOfAlts @github microsoft really needs to lock this down fr

• 
  Gustavo Alessandri (@webgus) reported 55 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.

• 
  Willleebuilds (@willleebuilds) reported 58 minutes ago

  GitHub confirmed 3,800 repos breached via a malicious VSCode extension. Every coding agent that auto-installs extensions on a fresh workspace is now part of the attack surface. The supply chain isn't a humans-only problem. The agent installs whatever you'd install.

• 
  Clazz one (@klass_101) reported 59 minutes ago

  @teneo_protocol CLI in GitHub just in case you have to work on the same issue and the other ones

• 
  Roy (@__roycohen) reported 1 hour 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

• 
  Telbloggram (@Telbloggram) reported 1 hour ago

  access to internal repositories" issue, suspected to be caused by malicious VS Code/AI Coding plugins installed on GitHub employee devices. [ChainCatcher] - link

• 
  🦅 (@EagleEyesCrypto) reported 1 hour ago

  if you believe agents will install and run code on their own, you need a package layer that isn’t built for human devs. @Nipmod is exactly that. npm for agents, sitting on top of gitlawb (the github for agents). verified packages, DID-signed ownership, MCP server live. real product, not a deck. 28 verified packages, 388 claimable drafts, working CLI + MCP server for codex / claude code / opencode. gitlawb = github for agents nipmod = npm for agents