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 (59%)
• Errors (32%)
• Sign in (9%)

Live Outage Map

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

City	Problem Type	Report Time
Colima	Website Down	1 hour ago
Poblete	Website Down	22 hours ago
Ronda	Website Down	1 day ago
Montataire	Errors	1 day ago
Montataire	Website Down	2 days ago
Tortosa	Website Down	4 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:

• 
  planefag (@planefag) reported 6 seconds ago

  THIS. And, you know what? Valid. Same for people who google around for a solution to a niche problem and it leads them to a github page. Because, that's what niche solutions are for - people with niche problems! I'm just asking for a minor UX improvement, you psychopaths

• 
  Rock (@_rockgu) reported 24 seconds ago

  open source has a security problem. it also has a security solution money can't buy. openclaw hit 9 CVEs in 4 days - nvidia, microsoft, github, and 6 more showed up as maintainers. 358K stars is the distribution. the CVEs are the tax. the coalition is the compounding.

• 
  Dr. Nripanka Das (@DasNripanka) reported 2 minutes ago

  Ghostty leaving GitHub has 1,900+ HN points because every maintainer knows this fear. the real lesson is not "leave GitHub." it is: design the project so leaving is boring. mirrored issues, portable CI, docs outside one vendor, releases you can rebuild.

• 
  SWAMPIST (@swamp_ist) reported 3 minutes ago

  @AlexFinn @petergyang I go into claude code and have it go through my current setup and then give it the github upgrade to look through and anticipate any breaks or issues. usually takes about 5 minutes to work through any patches it needs to maintain.

• 
  nyx. (@nyxquant) reported 3 minutes ago

  @0xSero @fxnction Local PC: Codex/Claude Code makes actual code changes in xxxx. GitHub: central source for issues, branches, PRs, and decision logs. Hermes VPS: reads GitHub/issues/docs, creates tasks, summarizes sessions, and prioritizes. Opus/ChatGPT/Kimi: used by you/Hermes for reviews, strategy, in-depth analysis, or research. No direct VPS-to-PC shell: no SSH/RDP access from the VPS to your private machine for agents. does this make sense?

• 
  planefag (@planefag) reported 6 minutes ago

  @Croker_Frog I've been typing /releases at the end of the URL for years now because trying to puzzle out the latest goofass **** on github isn't worth the trouble just give me the ******* tarball

• 
  Beau Johnson (@BeauJohnson89) reported 14 minutes ago

  the next agent security problem is not api keys its the random mcp servers and skills your coding agent is quietly trusting snyk/agent-scan > 2,303 stars on github > scans mcp servers, agent tools, and skills > detects 15+ risks like prompt injection, tool poisoning, malware payloads, credential handling, and hardcoded secrets > supports claude code, cursor, windsurf, gemini cli, codex skills, openclaw skills, amazon q, amp, and more best part: it treats agent components like a supply chain because thats what they are now

• 
  Curtis Summers (@curtissummers) reported 16 minutes ago

  Here we go again...I'm getting consistent failures today on Github Actions for cache/sscache with: `Our services aren't available right now...` errors. @githubstatus

• 
  Nermal (@nirmalpatel_) reported 20 minutes ago

  @JonathanRoss321 yeah right LLM says Yes to every terrible architecture move, and the dumass prompters keep saying yes for every terrible decision, making the codebase into a slopfest, welcome to github being down for a week

• 
  Stanislav (Stas) Katkov (@5katkov) reported 20 minutes ago

  @douglascamata @GergelyOrosz @Pragmatic_Eng I completely agree with this point. Their GitHub copilot web interface is riddled with bugs and on most days it's just broken. Same with everything else...

• 
  Arjun Iyer (@arjuniyer_) reported 21 minutes ago

  @github 5/6 And it gets worse as models improve. A more capable agent that still can't validate its output just produces more unvalidated output, faster. The fix is closing the loop at the source: agents that write code AND verify it works against reality in the inner loop. This is what we enable for teams building on Kubernetes at @signadot.

• 
  Simon Brown (@simonbrown) reported 24 minutes ago

  I've been watching a few GitHub repos with interest over the past few months. AI PRs, big new features on a regular basis, much more frequent releases. But the number of issues has skyrocketed ... bugs in those new features and existing functionality that's been broken. I can't imagine the damage that's being done inside enterprises from all of the AI mandates I keep seeing/hearing about. 🙈

• 
  Blaze (@browomo) reported 27 minutes ago

  This 13-year-old Thai student solves Codeforces rating 800 problems in C++ in 45 seconds through an AI agent he built himself on Claude Code and posted to an open GitHub repo. He sits in a regular school room with a MacBook Air on the desk, a silent HHKB Type-S keyboard for $300, and a timer in the frame. In the browser Codeforces is open, in VS Code an empty .cpp file, and in the corner of the screen a Claude Code window. No algorithm tutor, no competitive programming course, and not a single line of code written by hand. His entire loop runs on 3 components: 1/ Claude Code as the brain 2/ An MCP plugin for Chrome that reads the problem statement right from the Codeforces page 3/ A public GitHub repository where his entire agent lives. Over the past month he closed 23 problems in virtual contest mode. Average solve time, 45 seconds from opening to Accepted. Number of lines he typed by hand during that time, 0. The Codeforces rating system brought his profile to 800 in 12 days. The entire setup is assembled from his repository in 1 weekend. And here is the system prompt he gives the Claude agent before every session: "you are a competitive programming agent for Codeforces. your tools: read_problem(url), generate_solution(language, constraints), validate_against_examples(input, expected), submit_to_codeforces(code). any problem fed to you by the MCP plugin from the browser goes through 4 steps: 1) read the statement and identify input/output format 2) determine the algorithmic pattern (sorting, math, greedy, dp, graphs) 3) generate a solution in C++17 using stdc++.h 4) run it against examples before submitting. if even 1 example fails, rewrite the solution and repeat validation. language: only C++17. file: always {problem_id}.cpp" Meaning the agent knows exactly which problem it is solving right now. It knows what input format Codeforces expects in this specific problem. It knows which algorithmic pattern to apply based on the 800 rating and the tags in the statement. It knows it has just 45 seconds before the student hits submit, and that any failure on a test example is its problem, not the kid's. The work cycle fits into 1 turn of the palm. The guy opens problem 1971A on Codeforces, the MCP plugin picks up the statement, Claude in 8 seconds returns ready code with include, a while loop, and cout output. The guy does a copy-paste into the .cpp file, hits submit, and 30 seconds later sees green Accepted in Status. And only if Codeforces returns Wrong answer on test 2 does the agent automatically grab the failing input, break down the edge case, and rewrite the solution before the guy manages to close the tab. Here is what his Status page shows for the last 24 hours: "1971A - My First Sorting Problem | C++17 | Accepted | 45 sec" "1850A - To My Critics | C++17 | Accepted | 38 sec" "1807A - Plus or Minus | C++17 | Accepted | 41 sec" "1791A - Codeforces Checking | C++17 | Accepted | 52 sec" "1676A - Lucky? | C++17 | Accepted | 33 sec" On the desk in front of him is a MacBook Air without a single open notebook, a silent HHKB Type-S on which not 1 key was pressed during the entire session except cmd+v and cmd+enter, a mi timer set to 45 seconds, and souvenir Zelda figurines behind the monitor. Out of everything I have seen this year, this is the cleanest competitive programming pipeline on a single student: 23 problems solved in a month, 45 seconds each, and 0 lines of code written by hand.

• 
  Tommy Williams 🇺🇦 (@twwilliams) reported 31 minutes ago

  @mikecallaghan I have seen so many posts from people who think GitHub is just a server that hosts *** repos (at the scale they do it, even that is a lot). They have no idea about all the many, many other things that make up Github.

• 
  DataEatsWorld (@dataeatworld) reported 31 minutes ago

  I cant reply anymore 😮 i was going to say run a server open free map self hosted or sponsor on github

• 
  AN/PSN-11(V)1 Precision Lightweight GPS Receiver (@johnlockesboi) reported 31 minutes ago

  @SCShipyards On thing I don't think anyone considered with the rise of ai, is the server cost of storing all the absolute garbage that is generated that no one cares about and will never generate a profit. GitHub is is learning this too.

• 
  Hany (@kmhaneem) reported 33 minutes ago

  Dropbox launched in 2008 with a simple promise. Put your files in this folder and we will sync them everywhere. Every sync goes through their servers first. Their infrastructure. Their terms. Your files sit on their machines until you need them back. A developer named Jakob Borg decided that was the wrong architecture. Not inconvenient. Wrong, at the level of who owns what. In December 2013 he shipped the first public release of Syncthing. Peer-to-peer file sync. Your devices talk directly to each other. No company in the middle. No server reading the transfer. Syncthing is free, open-source, and has 67,000+ GitHub stars. The project's own stated mission: your data is your data alone, and you deserve to choose where it is stored. Most sync tools list speed and storage first. Syncthing's README lists data protection as priority 1 and priority 2. Speed does not even make the list. That tells you exactly what this project is. -> Your files go from your laptop to your phone. Nowhere else. -> Works on Windows, Mac, Linux, Android, and more. -> No storage cap. Your limit is your own hardware. -> Peer-to-peer sync. Direct device to device, encrypted in transit. -> Runs silently in the background. Zero clicks after setup. -> Web UI included. No command line required to use it daily. -> Open protocol means no vendor can quietly change the rules on you. -> GPG-signed releases. You can verify every binary before running it. -> Versioning built in. Deleted something? You can get it back. -> Self-hostable discovery servers if you want to go fully off-grid. By 2019, Syncthing was getting roughly a million downloads per stable release and syncing hundreds of terabytes of data every day. It is now backed by the Syncthing Foundation, a Swedish non-profit, so no company can buy it, pivot it, or shut it down. Last commit: this week. Shipping continuously since 2013. 300+ contributors. Still pushing updates in 2026. Dropbox: $9.99/month. Google Drive: $9.99/month. Syncthing: $0. Forever. No account to create. No server holding your files hostage. No price hike email arriving on a Tuesday morning. No terms-of-service update quietly granting them new rights to your content. Cancel Dropbox and your access dies with it. Run Syncthing and nothing changes. Your files are on your machines. They stay there whether you open GitHub tomorrow or never again. That is not a feature. That is a different relationship with your own data. 67,000+ stars. MPLv2 license, which means no corporation can quietly close it down. 300+ contributors across a decade. Updated this week. The people who switch to Syncthing are not always the most technical. They are the ones who read the terms of service once and could not unsee them. If that sounds like you, the link is worth a look. (Link in the comments)

• 
  Rugbist (@rugbist_) reported 34 minutes ago

  @thdxr github web been broken so long that a vscode fork feels like a revelation

• 
  Reyansh Bahl (@reyanshbahl) reported 35 minutes ago

  not sure there will ever be a true github competitor. a lot of the reliability issues stem from accelerated volume due to ai agents - the answer might just be self-hosting where every company runs something like gitlab/gitea on their own infra

• 
  Joats (@SAjoats) reported 36 minutes ago

  @RedBedDread @planefag Yeah i know devs love to complain about users. You don't have to convince me. "learn github" you have identified the problem. Github UI has devolved over the years. You shouldn't be forced to dig through **** until you get used to the smell.

• 
  Giorgio Iezzi (@GIezzi18020) reported 39 minutes ago

  @romainhuet @adahstwt I cant connect GitHub to Codex...it keeps showing error in the plug in..

• 
  Risk (@Riskorrrrrr) reported 39 minutes ago

  Me reading ancient GitHub comments about a problem I’m having now

• 
  Eric S. Raymond (@esrtweet) reported 40 minutes ago

  planefag, I'm not excusing the attitude of the guy who pissed you off. But there is an explanation for it, and I'm going to put on my Mister Open Source hat and lay it on you. The real reason there aren't prominent links to downloadable binaries on forge sites like GitHub is that in open-source land there is no such thing as a truly portable binary. Windows and Mac make binary distribution easy by being limited to a single hardware platform and a single ABI - application binary interface.. (The assertion I just made can be quibbled with at the edges. I will be unkind to anyone who attempts this.) An application binary interface is a set of conventions for how you decorate your binary so the operating system's program loader knows what to do with it, and how you write traps from your binary to call operating system services. Windows and Mac have, effectively, just one ABI each. So you can generate one binary for, say, Windows, attach it to a download link, and Windows users will generally not come back screaming for your blood because it fails to work in some obscure way. (Again, this statement can be quibbled with, but see this whacking great truncheon in my hand? Just don't.) There is no such grace in open-source land. There are a whole bunch of complicated historical reasons for this, starting with the fact that Linux runs on more different hardware architectures, and continuing with the fact that Linux isn't the only game in town (there are the BSDs), and continuing into technical minutiae that would make your head hurt, and continuing further into technical minutiae that make *my* head hurt. But what this actually means is that if you want to provide binaries and not get sperg-screamed at, you can't just provide one. You'd have to provide many, and no matter how comprehensive you try to be somebody is going to be disgruntled because you didn't cover their corner case. This is not a cost-free proposition. For each different kind of binary you provide, you need to cross-compile your source code in a different environment, many of them posted on distributions and hardware platforms you don't have routine access to. So people almost never do it at all. Because most projects don't do this, sites like GitHub don't see any demand push to make binary download links really accessible. Instead, the problem is normally handled at a different level. Your distribution maker keeps huge sets of compiled binaries lightly hidden instead of installable packages, tuned for the ABI of that single distribution. Your package manager hides from you the packages for everything but your hardware architecture The person who pissed you off was rude, but he wasn't exactly wrong about the objective facts. What you want isn't practically possible. Instead of being annoyed because GitHub doesn't feature binary-download links, search for that software using your package manager. Sometimes you won't find it. That's when you have to download source bust out a compiler. Sorry, but that's the way it is. We're trying as hard as we can - really, we are. But the complicated shape of the terrain constrains what we can achieve.

• 
  Lawrence D. Loeb (@LDLoeb) reported 42 minutes ago

  @openclaw …cold molasses. Now stepping back to 4.26. Hopefully that restores full functionality. Will file an issue on GitHub if I can get enough to support one.

• 
  Jonas (@wisplite) reported 44 minutes ago

  @TylerNickerson @github React isn't necessarily the problem. React makes it easier to write bad frontend code, because it makes it easier to write frontend code in general.

• 
  Shrit (@Shrit1401) reported 44 minutes ago

  it's so funny github is struggling to be live because pre AI commits were not that much, however everybody is using agentic AI / vibe coding wtvr u name it, we're spamming commits, and github is reaching it's limit for resources it will be interesting to see how they try to solve this problem.

• 
  Yash (@buildwithyash) reported 46 minutes ago

  I open github and linked in and within 2-3 minute each tab took 1.5 gb and 2.0gb Is this normal ? Its making my laptop slow after sometime message popup saying your system run out of memory Its been happening daily now

• 
  𝐒𝐚𝐠𝐧𝐢𝐤 (@EccExplorer) reported 50 minutes ago

  The worst part: Once an account is suspended, you can’t even access the support ticket you created, because GitHub requires login to view it. So you’re locked out of both your code and your appeal channel.

• 
  stimmtdochgarnicht 🇦🇸🇮🇴🇧🇶🇰🇾🇫🇰🇹🇫🇲🇭 (@stimmtdochgarn1) reported 52 minutes ago

  @TylerNickerson @github The problem literally is the browser. It's not just ten thousand lines, it's ten thousand lines of individually colored words, so potentially tens of thousands of DOM nodes. React adds maybe 20-40% overhead from diffing, but it's not what makes this fundamentally slow.

• 
  wiltedservices (@wiltedservices) reported 59 minutes ago

  remeber that we raided this guy github issue tab with our site