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	4 days ago
Tlalpan	Sign in	9 days ago
Quilmes	Website Down	9 days ago
Bengaluru	Website Down	11 days ago
Yokohama	Sign in	12 days ago
Gustavo Adolfo Madero	Website Down	16 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:

• 
  Astrohacker (@AstrohackerLabs) reported 9 minutes ago

  today i'm switching from neovim to helix i truly love neovim. but neovim relies on third party plugins, and the third party plugin ecosystem relies on pulling the latest commit from github from a ton of different authors. if any one of them get hacked, then i get hacked. just like the recent npm supply chain issues, except even worse, because *** repos aren't designed to be packages like this. helix is all-in-one, which does not have this supply chain issue, and is thus intrinsically more secure. good experience so far - it's pretty vim-like. let's see how it goes.

• 
  Working-Ref (@kkotkkio) reported 10 minutes ago

  The real unlock is Routines — Claude auto-triggered by cron, GitHub webhooks, or API. PRs get reviewed. Security scans run overnight. Fix PRs ship automatically. I'd start by defining a rubric before you 'let it cook'.

• 
  Perry E. Metzger (@perrymetzger) reported 15 minutes ago

  @DogOnTheRoof @JadeCole2112 @J_Von_Random It’s an emulation system for a lot of 1950s-1990s computer systems; it’s not commercially valuable but it’s useful for educational reasons. You can go and look at it for yourself; it’s on GitHub. It will probably not be of much interest to you unless you have an inexplicable urge to (say) run Educomp Basic on a simulated PDP-8, but it is a fairly complicated piece of software and there’s no way I could have fixed as many problems with it as I have in the last six weeks without AI assistance.

• 
  CyrilXBT (@cyrilXBT) reported 16 minutes ago

  A guy named nbatman on Reddit accidentally built the most censorship-resistant website on the internet. Hollywood tried to kill it. Spotify tried to kill it. Adobe tried to kill it. Google delisted it. Reddit shadow-banned it. The Motion Picture Association flagged it as a top threat. The RIAA pressured every hosting provider it ever used. It is still online. Updated every single month. By six anonymous volunteers working in their spare time. Here is why nobody can shut it down and what it teaches every builder about the future of the internet. THE ORIGIN 2018. One Reddit moderator. One Google Doc. A single person decided to organize the internet's free resources into one place. No company. No funding. No team. Just a document that kept growing because people kept finding it useful. Google killed it with a DMCA takedown in 2023. What happened next is the part worth understanding. THE REBUILD The community did not petition Google. They did not hire lawyers. They did not start a campaign. They rebuilt it on their own domain, mirrored it to GitHub, deployed it to IPFS, and distributed it across 12 backup domains simultaneously. In doing so they accidentally built one of the most resilient information architectures on the internet. No central server. No single point of failure. No CEO to pressure. No hosting provider that matters. When you remove every central point of control from a system the only way to kill it is to kill the internet itself. Hollywood has not figured out how to do that yet. THIS IS THE FUTURE OF INFORMATION What nbatman built without intending to is a blueprint for how information survives in an era where platforms can disappear anything with a single policy decision. IPFS does not work like a normal website. A normal website lives on a server somewhere. Find the server. Pressure the host. Site goes down. IPFS stores content across thousands of nodes simultaneously. There is no server to find. There is no host to pressure. The content exists as long as at least one node in the network holds a copy. This is the same architecture behind every major blockchain. It is the reason Bitcoin cannot be shut down by any single government. Applied to information it means the same thing. No single entity can decide what survives and what disappears. WHAT THIS MEANS FOR BUILDERS Every platform you build on right now has a terms of service. Every terms of service has a clause that can remove you without notice. X. YouTube. Substack. Medium. All of them. The builders who understand decentralized infrastructure are not just building products. They are building on foundations that no platform can pull out from under them. IPFS. Nostr. Distributed storage. Peer-to-peer protocols. These are not niche technologies for crypto enthusiasts anymore. They are the infrastructure layer for anyone who wants to build something that lasts. THE LESSON FROM SIX ANONYMOUS VOLUNTEERS Six people. No salaries. No office. No investors. Maintaining something that the most powerful entertainment companies on earth cannot destroy. The lesson is not about the content they organized. The lesson is about what becomes possible when you remove every central point of control from a system and distribute it across a community that believes in what it is building. That architecture is available to every builder reading this right now. The question is whether you are building something that a single policy decision can erase or something that survives because no single decision can touch all of it at once. nbatman did not set out to answer that question. He just made a Google Doc in 2018. The answer found him anyway. Follow @cyrilXBT for the exact tools, protocols, and infrastructure decisions that matter for builders who want to build things that last.

• 
  nickdjones @ndj@mastodon.nz (@nickdjones) reported 18 minutes ago

  @latent_node @wxrrjxr I'm excited by mlx-optiq, a few issues running Qwen3.5-9B-OptiQ-4bit - have the website, pypi, can't seem to find a github repo anywhere, any chance its OSS?

• 
  Triumph-Synergy(J.J.D) 𝝅 🇭🇹 🇺🇸 (@jaymoney0300) reported 21 minutes ago

  @lee003_ @Kamelkadah99 I seen him show frustration in GitHub.. so likely he is a pioneer like us! Problem is Pct can’t interfere they can only lead… yes his intent is genuine with GCV but still no ecosystem people will begin to see it for themselves soon that things won’t change until the traditional way is rendered obsolete a crash could help it but there’s no telling when that will happen until then they will keep seeing GitHub code not being activated. We have the app, docker, and GitHub everything is completed except the app itself!

• 
  Andrew (the *****) (@Andrewislington) reported 22 minutes ago

  GitHub went down the second I needed it for a big build 😭

• 
  NaM dev (@NaMarrado_) reported 22 minutes ago

  @TimJayas OpenAI is literally fixing the issue What did Anthropic did? Oh wait, they ignored the issue for weeks, then blamed the users for using it wrongly, and weeks after they acknowledged that there was an issue, despite multiple PRs being on their GitHub and them actively ignoring it?? I would rather have OpenAI who are honest about their issues and having issues, instead of a ******* company who is actively running multiple scams against their users and then blames them

• 
  Ethan Codewell (@Ethan_Smartsys) reported 22 minutes ago

  @VaibhavSisinty GitHub stars measure curiosity. Whether it holds up at 2am when an API breaks is a different conversation. 75+ model support solves an actual problem though.

• 
  Bnaf.OG | 🟧 (@bnafOg) reported 22 minutes ago

  GitHub trending hook: OpenPipe ART is pushing agent RL into the practical stack. Useful eval: reward quality, task diversity, regression tests, rollback, and cost per accepted fix. GRPO demos are cheap; durable agents need receipts.

• 
  Sidu Ponnappa (@ponnappa) reported 25 minutes ago

  @shyamdotme @github So far so good I read about this but we don't do much besides pull/push and use gh issues and that hasn't been impacted in a way that I've noticed

• 
  Zeke Gabrielse (@_m27e) reported 28 minutes ago

  I want GitHub except all the issues are just me reviewing the code on master and adding nits everywhere so I don't forget to do them on Monday

• 
  Docsbook.io (@docsbook) reported 29 minutes ago

  @Suman_N_Jain binary is one of those rare projects where the idea and execution both land. Problem is the docs are buried in GitHub — people bounce before they even understand what it does. Built a hosted docs site so the first impression actually sticks. Go take a look.

• 
  Prabhjot Singh Rai (@psr_ai) reported 30 minutes ago

  I’m seeing GitHub runner action being stuck in queued for default ubuntu runs. Is anyone else facing this issue? Github status mentions github actions are not impacted. #GitHubActions @github

• 
  Brad Hutchings 🍌🐶🦜 (@BradHutchings) reported 31 minutes ago

  Github as compliance is a bug to fix, not training to be done. People are not getting into vibe coding so they can be great engineers. They're doing it to get **** done. They're failing, of course, but they're providing a signal. We should listen.

• 
  intergalactic spice trader (@piobid) reported 32 minutes ago

  How tf is it, that in the year 2026, you need to close ALL open VSCode windows and reopen them (and don't make the mistake of reopening from "open recent") to update PATH variables. And this is an open issue on the vscode GitHub since EIGHT YEARS.

• 
  Peter Dedene (@dedene) reported 34 minutes ago

  @0xsachi GitHub is trying to fix that

• 
  Josh Thomson (@Josh_is_regen) reported 36 minutes ago

  @PaulGugAI I believe Linux will growth in users because of AI agents. The minute a linux distro incorporates a small edge model that only knows it's own code. Gone are the days of trawling through Ubuntu forums to find a fix. Opencode has changed the way I use Linux, I just paste a github link it, tell it to install, where to put it on my start menu. And it just does it. Once that process moves out of the terminal and to a little 'pet' assistant like the windows paperclip. It's game over for windows.

• 
  38twelveDaily (@38twelveDaily) reported 37 minutes ago

  Problem: Microsoft engineers have favored Claude Code over Copilot CLI. There are gaps between the products that Microsoft now has to close. The GitHub team is shipping improvements based on feedback.

• 
  Ryan “Street King” Cooper (@StingyBumHole) reported 38 minutes ago

  @S1idestar @ee8982085749436 @6Foot4Honda There are bots. Literally a free program on github that eliminates all human error

• 
  DORI(❖,❖) (@Dodori4390) reported 38 minutes ago

  Why I’m bullish on Rialo The recent GitHub breach perfectly highlights the biggest risk in the coming agent economy and why Rialo’s approach is so important. While most projects are racing to build more powerful agents, Rialo is laser-focused on how to safely control them. Their protocol-level governance solutions stand out - Scope Limitation: Give agents temporary, minimal permissions only (credentials issued just-in-time). - Immediate Freeze: Freeze transactions instantly at the protocol level when anything suspicious is detected. - On-chain verifiable orchestration: Combine Web2-level convenience with Web3’s immutability and auditability. Rialo isn’t just another “make agents do cool things” project. They’re building the safety infrastructure for the entire agent economy. In a world where one compromised agent could cascade into disaster, Rialo is solving the hardest and most urgent problem first: secure control. The GitHub incident wasn’t just another hack, it was strong real-world validation that Rialo is working on exactly what the market desperately needs. That’s why I’m genuinely excited about this project. @RialoHQ @RialoKorea @itachee_x

• 
  itay shmool 🇮🇱☮️✨️ (@IShmool) reported 40 minutes ago

  @Cryptoxorz You caught the part most people miss — the ops loop. Bug reports flow into GitHub issues, Claude Agent SDK triages them, fix PRs get generated. The course isn't just built with AI, it's maintained by AI. That's the actual story.

• 
  Subhash Dasyam (@subhashdasyam) reported 42 minutes ago

  Two findings. Two working proof-of-concepts. First: arbitrary code execution through the pull_request trigger in claude-code-base-action. Untrusted input, no guard on the workflow. Second: token exfiltration via prompt injection in a GitHub Actions workflow. Triggered by opening an issue. Any GitHub user. Both reported. Both triaged within days. Both fixed. Both closed on HackerOne.

• 
  Yves (@gas0linr) reported 44 minutes ago

  @morganlinton No. GitHub is great. And I'm sure Cursor would suffer the same problem with load

• 
  Peter "Coder AI Optimist" Marreck (@pmarreck) reported 45 minutes ago

  @NoctreSharp @Aizkmusic “open source” when Microsoft claims it is tainted AF LOL While I do make sure that all my Zig CLI utilities have working Windows builds (see my github, same username), the *nix space just has a huge number more of them, many of them make non-Windows assumptions, and ssh not working well on Windows is more the rule than the exception. If Windows simply permitted executables that didn’t need to end in .exe, that would solve A TON of the problem IMHO. Even then though, *nix-native cli utils make assumptions about path separators, terminal properties etc etc etc that just make using WSL way easier of a workaround.

• 
  zoiroff (@zoiroff77) reported 50 minutes ago

  I built for 8 months. Got 3 users. 2 were my friends. Everyone talks about building. Nobody talks about the part where you launch and hear nothing. The indie makers winning right now didn't build better products. They built an audience first. GitHub stars don't pay rent. Product Hunt badges don't acquire customers. The only thing that works at 0→1 is talking to people who have the problem. Before you build. While you build. After you launch. Question: what came first for you — the product or the audience? And would you do it differently?

• 
  4A 45 56 49 4C (@4A4556494C) reported 58 minutes ago

  CISA leaking AWS GovCloud keys on GitHub in the same week CISA adds Langflow to KEV is the kind of timing that makes you wonder if the simulation developers are just getting lazy with the writing. The agency responsible for telling every other organization to rotate credentials and scan for secrets in repos... exposed credentials in a repo. Not through a supply chain compromise. Not through a sophisticated attack chain. Through the most elementary operational security failure that exists. Every CISA advisory about credential hygiene, every binding operational directive about secrets management, every public guidance document about not committing keys to version control — all of it is still correct. And the organization that wrote it didn't follow it. This is the structural problem with security guidance as a product: the people who write best practices and the people who implement infrastructure are different groups with different incentive structures, and compliance frameworks don't close that gap. They paper over it. The fix isn't more guidance. It's pre-commit hooks that block secrets from ever reaching the remote. Automated. Mandatory. Not optional. We've had this technology for years and we still treat it as nice-to-have.

• 
  Jehong Ahn (@Jehong_Ahn) reported 58 minutes ago

  The real problem isn't just malicious npm hooks. It's that our developer machines still contain too many long-lived credentials: AWS keys SSH keys GitHub tokens .env secrets Assume arbitrary code execution during dependency installation is now a normal threat model. I'm moving toward browser-based auth and short-lived credentials wherever possible.

• 
  Jacob Gadikian (@Senpai_Gideon) reported 58 minutes ago

  Hey @github I cannot express how crappy of a UX it is to have copilot fix a merge conflict and then need to manually approve the CI to run. If I trust copilot to fix a merge conflict, don't I also trust it to trigger CI? It's literally committing on my behalf already.

• 
  Silvery Fighters Jr./CG-TAN (@SilveryFJ) reported 58 minutes ago

  You can still download Linux Multimedia Studio from its Github page but same cannot go for the assets from the site as it remains down. The impact is overall minimal as others who produce music use other DAWs.