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 (61%)
• Errors (24%)
• Sign in (15%)

Live Outage Map

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

City	Problem Type	Report Time
Yokohama	Sign in	17 hours ago
Gustavo Adolfo Madero	Website Down	5 days ago
Nice	Website Down	5 days ago
Montataire	Sign in	8 days ago
Colima	Website Down	10 days ago
Poblete	Website Down	11 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:

• 
  Jarred Sumner (@jarredsumner) reported 1 minute ago

  I have pretty high confidence in it at this point. It passes Bun’s test suite on Linux x64 + arm64 glibc + musl, Windows x64 & arm64, and macOS x64 & arm64. It likely closes about 200 github issues. Still refactoring & simplifying. Still need to write the blog post.

• 
  Matt (@m13v_) reported 5 minutes ago

  the survivors so far: postgres mcp (replaced opening psql 50x a day), the github one (PR context without leaving the editor), and a macos automation server i now use to drive xcode + simulator from claude code without alt-tabbing.

• 
  Alexander Rob (@TheStarwald) reported 7 minutes ago

  @spamspam111113 @andreintg From Github. They have been incorporating AI generated code into their server, and it has significantly decreased their server availability. The same thing has happened with Amazon, who had an all hands meeting to put a stop to inputting AI code. Other companies are facing similar problems.

• 
  Failure is an option (@FarmingWithYHWH) reported 8 minutes ago

  @Hesamation Yup - just this morning, GitHub was down again.

• 
  John Renfro 🇺🇸 (@JohnRenfro2016) reported 9 minutes ago

  @waybackmachine @LMaster20013888 @internetarchive Check github for the error. No files are being uploaded. Uncaught TypeError: Cannot set properties of undefined (setting 'center') at center.js:13:6 at create.js:176:2

• 
  The Cyber Jim (@thecyberjim) reported 9 minutes ago

  So SailPoint's GitHub Enterprise went down on April 20th. Attackers waltzed into their private repositories, grabbed the crown jewels—identity platform source code and CI/CD configs. No fancy zero-day needed, just old-fashioned access they shouldn't have had. Classic move: compromise credentials, own the infrastructure, steal everything that matters.

• 
  Elhaidi (@3BissePeace) reported 10 minutes ago

  The Dead Man's Switch: If you realize you are infected and revoke your GitHub token, a hidden local daemon (gh-token-monitor) detects the 40X error and immediately runs rm -rf ~/ to wipe your home directory.

• 
  Jean Brito (@mortunha) reported 13 minutes ago

  @0xCVYH @nahcrof not using rooms yet for the agent, but added hooks with ci and issues from github, so now I can see all in the same place I hated using discord until I tried it for agents

• 
  luckyPipewrench (@luckyPipewrench) reported 15 minutes ago

  A coding agent with internet access is one poisoned GitHub issue away from becoming a courier. Not because it hates you. Because it’s helpful.

• 
  Ted Moyses (@TedMoyses) reported 15 minutes ago

  @VicVijayakumar We are starting to plan for this and use private package repositories in some places.... The trouble is it's on GitHub ....

• 
  Camille World (@SuejungH) reported 21 minutes ago

  Andrej Karpathy’s CLAUDE.md. heard it gets a ton of stars on GitHub, but thought to myself — if it were really that essential, Claude would just have it built in by default — so I ignored it. But someone recommended it again. So I studied it. It turns out to be like: 1) Think before you code. 2) Code as simply as possible. 3) Only fix what you were told to fix. 4) Only do what you were asked to do….. obvious, basic things……… So I asked, do these obvious things really need to be spelled out? And apparently the answer is surprisingly yes — that it’s a limitation of the current model. How interesting. 🤔 Andrej Karpathy’s CLAUDE.md 요. 이거 깃헙에서 Star 를 엄청 받았다 그런 포스팅 보고, 속으로 그렇게 필수적이면 Claude 에서 기본으로 넣겠지 싶어서 그냥 무시하고 있었어요. 그런데 추천하신 것 보고, 공부해 보니까 1) 코딩하기 전에 생각해라. 2) 되도록 심플하게 코딩해라. 3. 하라고 한것만 고쳐라. 4. 하라고 한 일만 해라….. 이렇게 당연한 것들이네요……… 이렇게, 당연한 거 꼭 말로 해줘야 하냐고 물어 보니… 그게 지금 모델의 한계라고 말해줘야 한다고 하는군요. Funny indeed.

• 
  Reelix (@Reelix) reported 23 minutes ago

  @banthisguy9349 @Payoneer You're trying to shut down the malicious North Korean payment providers, and I'm trying to shut down the malicious North Korean Github Repos :p

• 
  Iván (@seikv) reported 26 minutes ago

  GitLab only has to do the oposite of what GitHub is doing and make its UI prettier and boom all problems solved.

• 
  colinhacks/zod (@colinhacks) reported 28 minutes ago

  @PawelJLisowski we're calling ourselves an "OSS CodeRabbit" when really the most interesting parts of Pullfrog are not review-related. it's basically a hackable platform that lets you trigger agent runs in response to arbitrary GitHub activity. being able to mention @ pullfrog anywhere to tweak a PR, open an issue, implement a feature—all things CodeRabbit doesn't do. focusing in on PR review: - price is the obvious one. I don't think per-seat billing makes any sense here. misaligns all the incentives—they're gonna try to use cheaper models to keep their costs down and margins high - running your code. they advertise things like "50+ linters and SAST tools" that are available to their agent. but only one matters—the one that's in your repo. because we're inside Actions we can just install your deps and run lints with your actual configs. - true model/provider agnosticism (you have control) - quality/ anecdotally there's no contest between a well-prompted Opus run vs CodeRabbit. candidly there's a way to go before we have true feature parity but for a typical reviewbot workflow Pullfrog is already very polished

• 
  Chris Ford (@chrisgford) reported 30 minutes ago

  @hamorahime @sergeynazarovx It was usually a complex error that only a few people somehow experienced. At least I can still experience this in GitHub threads within open-source projects!!

• 
  Emire (@EmireMetaX) reported 33 minutes ago

  GM Frens I spent time going through the @quipnetwork GitHub this week and one repo kept standing out to me. It is called hashsigs-solidity. If you are a Solidity developer, this repo is probably worth your attention. What they built is a Solidity implementation of WOTS+, a post quantum signature system, and it already works with Hardhat and Foundry. That matters because developers do not need to learn a new workflow or install unfamiliar tools. It fits into the setup most EVM developers already use today. Why does this matter? Right now, Ethereum smart contracts rely on ECDSA signatures. The problem is that quantum computers are expected to eventually break that type of cryptography. WOTS+ works differently. It is based on hash functions, which are considered much safer against quantum attacks. It is also not some random experimental idea. It is part of recognized post quantum standards like XMSS. The interesting part is that @quipnetwork already published the package on npm. That means developers can install it into projects right now and start testing how post quantum signatures work inside real smart contracts. To be clear, it is still marked experimental and not fully production ready yet. The complete hardened version is expected later with mainnet. But developers who start learning it now will already understand the signing flow, verification process, and integration side before the rest of the market catches up. That is probably the biggest point here. @quipnetwork is not waiting for the EVM ecosystem to figure out quantum security later. They are giving developers tools to start working on it today.

• 
  Octopus Code Review (@octopus_review) reported 35 minutes ago

  three different shas. for one comment. if you get any of them wrong, you get a 400 error that does not tell you which field is the problem took us a day to realize this is not gitlab being awkward, it is gitlab being honest about something github hides

• 
  Tak 🦞 (@cherry_mx_reds) reported 36 minutes ago

  I ran out of inference today but then I learned I can keep going by connecting github to my ChatGPT account. I’m doing research with pro and then creating gh issues that I’ll jump on when the reset comes around.

• 
  S H U B Y .eth (@0xSHUBY) reported 36 minutes ago

  PROBLEM 1: *** Nightmare first mistake happened before any real code. accidentally pushed node_modules to github. github rejected it. said file exceeds size limit. the repo was now polluted. solution: added .gitignore, deleted *** history, reinitialized the repo completely. created a clean repository and pushed again. felt dumb but learned something: .gitignore first, code second. infrastructure before content.

• 
  Lee Ash (@hazae41) reported 37 minutes ago

  @TonyFromDiscord @IntCyberDigest GitHub Action is the error

• 
  Bruce (@StarloveDev) reported 37 minutes ago

  npmpandemic after the Github Actions shenanigans last year with running CI on random people's pull requests, i'm appalled that not everyone pulled the plug. A virus spread because of running random code on a server. Just so, so stupid.

• 
  altmind (@altmind) reported 38 minutes ago

  @saltyAom you can probably find a github issue with the list of problems they have?

• 
  Ella Sway (@TheEllaSway) reported 39 minutes ago

  Claude support is non existent. Their ai chatbot Fin is supposed to pass you on to product support. But never does. Even after admitting there is nothing more I can try to fix the bug. I’ve written a GitHub ticket and submitted /bug request almost two weeks ago with no response. @AnthropicAI any help here?

• 
  ♡ mari/cohe ♡ (@noinconsistency) reported 46 minutes ago

  @0xtiago_ github vowed to fix uptime but i aint see **** improving lmaooo

• 
  Ankyral (@ankyralTheDev) reported 49 minutes ago

  @github Your traffic statistics have been absolutely terrible for years. When are you finally going to fix the problem?

• 
  mary🐇 (@mary_ext) reported 50 minutes ago

  GitHub Actions has no means of gating workflow trigger behind a 2FA, and even if they did, it does not solve the issue above, and the way CIs are designed means that you're never going to know if something awry happened unless it failed or until the damage has been dealt.

• 
  Armaan Sidhu (@realarmaansidhu) reported 50 minutes ago

  @chatgpt21 This is not a flex. This is a labor market warning. Chris asked Codex to make him $5. The agent went out, found a security bounty path on GitHub, made a PR, followed up with the maintainer, kept his payment info private, and got the work merged. 22 hours of unsupervised work. $16.88 paid out. $506 per month if he runs that loop daily. Read the structure of the transaction. An agent identified an open bounty, executed the technical work, completed the bureaucratic loop, and converted code into cash. No human in the loop after the initial prompt. This is the floor of every junior engineer's job description. The math gets uncomfortable fast. Average entry-level software engineer in the US makes $85,000. That is roughly $40 per hour. Codex completed 22 hours of work for $16.88. Per hour rate: $0.77. That is a 50x cost differential, before you account for the agent running 24 hours a day, no PTO, no benefits, no Slack negotiations. Two things become inevitable. One, simple bounty and gig markets get arbitraged to zero by agents. Payouts collapse because supply went infinite. Two, the floor for human engineering work moves up. The work agents cannot do (architecture, judgment, customer communication, novel problem framing) becomes the only work that pays. That is the bifurcation. AI doesn't kill the engineer. It kills the entry-level path that used to train the engineer. Where do the next senior engineers come from when there are no junior reps left to climb? Nobody has answered that yet. Codex made $16.88. That number is going to look really small in retrospect.

• 
  Oluwamayowa (@oluwamayowa) reported 52 minutes ago

  Most product teams do not have a roadmap problem. They have an evidence problem. Support tickets, call notes, reviews, analytics, Slack threads, GitHub issues, surveys... The signal exists, but it is scattered. That is what Vyrric is built to fix.

• 
  WCNegentropy (@WCNegentropy) reported 56 minutes ago

  @forgebitz The situation is legitimately so funny for anyone who can understand it. Okay, so the tanstack thing is NOT NPM’s fault or issue. For one, the attack happened on GitHub, not NPM. It made its way to NPM through GitHub. Attacker got access to tanstack NPM through GitHub Actions.

• 
  Lee Ash (@hazae41) reported 60 minutes ago

  @unsafebl0ck @IntCyberDigest It is, don't use GitHub Actions to publish packages, it's a scam to make you pay server time