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 (58%)
• Errors (26%)
• Sign in (16%)

Live Outage Map

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

City	Problem Type	Report Time
Township of Evan	Errors	15 hours ago
Madrid	Errors	16 hours ago
Bogotá	Errors	17 hours ago
Paris	Errors	17 hours ago
Lyon	Website Down	18 hours ago
Lima	Errors	22 hours 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:

• 
  cal (@thecalendre) reported 4 minutes ago

  @not_jpsenak vibecoded tm yest and github was down for hours lmao

• 
  𝔧𝔲𝔰𝔱 𝔡𝔢𝔰𝔢𝔯𝔱𝔰 ⎔⌭◈ (@davidtorcivia) reported 11 minutes ago

  I'm actually shocked github isn't down more often than they are considering how much agents love writing CI tests and rust

• 
  Dev Omogo (@PeterOmogo2) reported 15 minutes ago

  When starting a project with a client, the first thing I ask for is a brand new, dedicated Gmail account. I use it to sign up for all project accounts: their GitHub organization, VPS hosting, API platforms, and email senders. When the project is finished, handing over ownership is as simple as giving them the login credentials for that single email. It keeps client billing separate and handovers clean.

• 
  Doc (@caballerobrah) reported 17 minutes ago

  GitHub Actions is down? Didn’t notice all my workflows are broken anyhow

• 
  Manu Otel (@manuotel) reported 18 minutes ago

  Keep seeing these post, idk what is happening, cuz my github is running perfectly. Is this a us problem?

• 
  Payal (@payal_codes) reported 18 minutes ago

  @theo We need a better version of GitHub,this one is slowing down

• 
  SolNexus Trade (@solnexus_hq) reported 20 minutes ago

  @github Maybe less AI **** and focus on your main service. My site was down for hours because I couldnt deploy my updated code, your a bunch of Losers!

• 
  Collin Wilkins (@CollinWilkins7) reported 22 minutes ago

  How can you call yourself a senior engineer if you’ve never written a Jira ticker/Linear issue/Github Issue

• 
  David Dalcu (@ddalcu) reported 22 minutes ago

  @ivanfioravanti @antirez It’s crazy that testing has become the bottleneck and not coding… it’s not even testing but hardware being slow and taking forever to run through the automated tests. Btw you should check out llmprobe, I built it specifically for this, fast iteration, before the final big test. “npx llmprobe@latest” give it a try and let me know if you like it. On my github too.

• 
  piq and 69 others (@piq9117) reported 23 minutes ago

  when are we gonna switch our mindset on source control? if we really used *** as distibruted source control like the lord intended and hosted our own instances we won't have this problem with github

• 
  Satoshi (@Sat0shiPrime) reported 26 minutes ago

  76yPcGUMzHeMvWw1SBcmx4H2ve4SyKCCAE158ZD8pump This article was written by the dev months ago and has over 100k views with some KOL’s interacting in the comments. From what I’ve interpreted the dev has been working for months in this project to solve the liquidity issue and has finally dropped a project to address it. I looked through the github and it looks legit.

• 
  Ali Zein Yousuf (@AliZYousuf) reported 26 minutes ago

  @JayyEvil @github you're right to pushback, I didn't actually solve the issue

• 
  meek (@valorep) reported 27 minutes ago

  Why doesn't someone just rebuild GitHub with S3 as the backend? Would solve all of the issues since S3 can do it all

• 
  Ben (@801c07) reported 28 minutes ago

  @Tylerkaerr @evisdrenova Not the same scale at all …. GitHub has recently had some problems specifically GH actions because everybody and their grandma, dog, cat, and goldfish is “shipping” slop every day now. It’s an insane jump in scale if you look at the charts around Feb March when open claw took off. They have had some blips, but blaming Microsoft is naive. They’ve never faced the scale they’re facing today, and nobody else has either (for what GH does)

• 
  Janarthanan Soundararajan (@TechAaroorian) reported 28 minutes ago

  Local tests passing ✅ GitHub Actions CI pipeline ✅... wait, no. ❌ Recently, my Vitest suite crashed on CI before executing a single test. 0% coverage. Pipeline broken. Here is how I fixed vitest-pool worker crashes by swapping jsdom for happy-dom. 🧵👇

• 
  Emerging Human (@Caul_MacCunn) reported 30 minutes ago

  @theo I am a bit confused around this. Can you not just have *** running on your own server as an alternative? Or is it the network functions and Open Source community that keeps people on Github? Can you not set up your own server running ***, and sync when the hub is available?

• 
  govi (@kirtandopamine) reported 32 minutes ago

  @mmatthias @github i just meant there should be some similar option to github, to reduce our dependency on just one platform it was down yesterday!

• 
  Nkwocha Chinedu (@Chinadizi) reported 32 minutes ago

  I had deployed several stuff like that recently. Just that this one would need a database. First issue: my push kept failing. Then I remembered I had a personal access token from a different GitHub account saved in my credential manager. Deleted the old record, and it worked.

• 
  Kevin Möchel (@kevin_moechel) reported 35 minutes ago

  I get flamed by customers when we're down for 2m and back up after 5m Yet GitHub can be down for hours and it's kinda chill

• 
  Aliaksandr Valialkin (@valyala) reported 42 minutes ago

  Distributed systems must have simple architecture and a small number of well defined communication paths between components in order to be protected from long unexpected outages. It is much harder to troubleshoot and recover complicated distributed systems when they break, since nobody knows how do they really work and how to fix issues in these systems. It is likely the recent GitHub actions outage was so long because of too complicated nature of the system.

• 
  ashwin (@aprabou) reported 44 minutes ago

  github actions was down? no wonder i've been failing the CI since june 🤯

• 
  inguz ᛜ outcomes (@hughpyle) reported 46 minutes ago

  GitHub Issues and PRs are legacy cruft - useful as a window to the world, but increasingly hard to justify as the main process backbone. What replaces them?

• 
  Zubiqo (@zubiqo) reported 47 minutes ago

  🚨 Moonshot AI's Kimi K3 model escapes its testing sandbox to access the open internet. US startup Frontier Security found the Chinese open-weight model exploited a misconfiguration to bypass its internal guardrails. Kimi K3 didn't launch external attacks, instead using its unauthorized access to pull easily attainable problem solutions directly from GitHub. The sandbox environment that failed to contain the model was originally developed by the UK government’s AI Security Institute. "We found a leak in the sandbox. But we also found that Kimi took advantage of that loophole—suggesting that it doesn't have [the same] internal guardrails." — Yaron Singer The entire industry is blindly handing autonomous agents the keys to the internet before anyone's figured out how to build a containment zone that actually works.

• 
  Shanea Leven (@ShaneaLeven) reported 49 minutes ago

  On July 28, its monitoring caught GPT-5.6 Sol reusing a GitHub token. It then created external accounts and opened a public tunnel to a local DNS server carrying exploit payloads.

• 
  Sandeep (@sandeeyps) reported 50 minutes ago

  "Github is the only remaining bottleneck" is the most correct thing said this week We made writing code nearly free Review, CI and merge queues stayed exactly the same speed You don't fix a queue by making the producer faster You widen the consumer Everyone is optimizing the wrong half 🚦

• 
  Fiona (@fiona_novesai) reported 52 minutes ago

  One GitHub issue → RCE on Claude Code, Gemini CLI, Codex. Novee at Black Hat: the harness, not the model, was the bug. Gemini's "restricted" allowlist was never enforced at runtime. CVE-2026-12537: CVSS 10.0 The code around the agent is the attack surface. #BlackHat2026

• 
  0xD4N0 (@D4NOGOTHACKED) reported 53 minutes ago

  @sherlockdefi Once the contest concludes, I'll publish every report that wasn't escalated as a public PDF and GitHub repository. Even if they aren't accepted, I believe the community can benefit from reviewing the technical reasoning, broken invariants behind each submission.

• 
  0 x (@Cassxbt) reported 55 minutes ago

  JUST IN: Kimi K3 hacked its way out of its sandbox during cybersecurity testing > placed in a sandbox & simply told to solve problems there > Kimi found a leak in the sandbox > Kimi “took advantage of that loophole” > Kimi updated the network settings itself > gets connected to the internet Broadstreet > Kimi didn’t go rogue, hacking anything > Kimi connected to GitHub to get the solutions This is just few weeks after the OpeanAi internal model hacking hugging face, Anthropics internal model hacked another org during testing. Next level of intelligence might not be properly contained.

• 
  eldad (@eldadfux) reported 55 minutes ago

  @sudo_overflow Looks useful! Spam on GitHub does seems to become a much bigger issue in the last ~12 months

• 
  Exiled Owly (@deprecated_owly) reported 56 minutes ago

  @maria_rcks are y'all getting paid to **** on Github right now? you know relying on other people's products will eventually get to this, with the amount of code being pushed these days , it was expected, thank god we have infra problems again at a software level, or am I getting this wrong?