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

• 
  Mad Orkestra (@MadOrkestra) reported 50 seconds ago

  What vibe coders don't seem to understand: Creating your own solution for the same problem is easy. Collaborating, contributing and iterating on an existing solution is much harder. But that is what open source means. Not just pushing random stuff to Github and calling it a day.

• 
  Rasmus Hjulskov (@RasmusHjulskov) reported 2 minutes ago

  @mikker Everything that doesn’t need me in the loop or things that’s easier to be handled over discord on the phone. It’s still not an alternative for my main coding agent, but it works on most of my codebases more like an intern on my old laptop with their own GitHub account and a shared Obsidian vault where it creates a llm-wiki and a shared Kanban board. I have tried moving it deeper down the afk coding paradigm, but I pretty much always come back to why I hate waterfall development - or at least that the project I’m currently tinkering with is so early, that there isn’t much to win if any. So it’s mainly the complete overview over all I’m doing and all the codebases if needed, which have resulted in I’m using that instead of most of what was prior a Gemini/chatgpt chat and only less than I expected of what I was doing with local coding agents.

• 
  Tak 🦞 (@cherry_mx_reds) reported 3 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.

• 
  Paweł J Lisowski (@PawelJLisowski) reported 4 minutes ago

  @jdegoes wouldnt say its doing anything, thats the problem. github doesnt have ceo microsoft doesnt seem to care about anything they cant milk lately

• 
  Santosh Yadav (@SantoshYadavDev) reported 4 minutes ago

  This is how you know @tan_stack team is serious about this security incident, I am seeing @crutchcorn constantly engaging with the community and talking to everyone while trying to fix the issue, escalating this to the GitHub team, I have seen him online since the vulnerability was reported, and no he doesn't get paid to do this, he is passionate about OSS and loves doing this.

• 
  BourneS (@bourneshao) reported 8 minutes ago

  @Its_Nova1012 and somehow the maintainers get yelled at in github issues for not fixing things fast enough lol. wild dynamic

• 
  Valar Dohaeris (@LordKhagan) reported 11 minutes ago

  This Tanstack supply chain attack is crazy. If you rotate your GitHub keys, a system daemon wipes your computer. Like literal wipe. We’re so cooked man. It does a pool to GitHub, when it gets 400, your server is gone. 😭😭

• 
  Emire (@EmireMetaX) reported 14 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.

• 
  Glitch Truth (@glitchtruth) reported 14 minutes ago

  The Mitchell effect is real. Same thing happened with Ghostty, his terminal hit 25k GitHub stars in weeks before public release. When a respected builder vouches for indie tooling, distribution problem solved overnight. Bentley shipped Hunk solo and now every Zig dev on my timeline is installing it.

• 
  LeanCTX (@leanctx) reported 17 minutes ago

  Crossed 860 GitHub stars on lean-ctx. Wild that something I built to fix my own token bill is now used by thousands of devs.

• 
  Matt Arderne 🌊 (@mattarderne) reported 20 minutes ago

  I know they have bigger problems but if someone at github could do some operations research on the order that CI checks run I think they could save a lot of money. Run the recently failed check first...?

• 
  saburo (@jskoiz) reported 21 minutes ago

  @aegeantic Better than GitHub issues I don’t make the rules

• 
  Camille World (@SuejungH) reported 22 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.

• 
  Arzvak (@RealMITian) reported 22 minutes ago

  @CliftonSellers Imagine you're building a science project in a team. You're working on part x, teammate on y etc. Now how do you know which person has done what? Are you guys doing the same thing at the same time? conflicts arising? You can think of Github as something which is made to fix that. Shows how much work is done, by whom, what changed since last night, who else worked on what, etc. etc.

• 
  Sakti Prasad Bagchi (@saktibagchi) reported 23 minutes ago

  4/ 3. Skip the LLM Completely (Best Choice) When you know exactly what to do → no agent needed. GitHub example: gh issue create --title "Fix bug" --body "Details..." Zero tokens. Lightning fast. 100% reliable.

• 
  aaalex.hl (@aaalexhl) reported 25 minutes ago

  Github has an outage every week and Gitlab is like yeah instead of taking advantage of our competitor slipping up and gaining more market share, we're gonna fire everyone instead because of, wow you're never gonna believe it, AI

• 
  Vineet (@dvineet9) reported 25 minutes ago

  Your biggest security risk might not be your production server. It might be this: env: AWS_SECRET_ACCESS_KEY: AKIA... One leaked GitHub Action log.
One exposed repo.
One compromised pipeline. And your infra is gone. Secrets should NEVER live inside workflows. 
Use:
• GitHub Secrets
• OIDC federation
• Short-lived tokens
• Least privilege IAM Attackers love CI/CD pipelines because developers trust them too much.

• 
  Bruce (@StarloveDev) reported 26 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 unknown foreign code automatically on the server. Just so, so stupid.

• 
  CMD CNTR | Web Engineer Experts (@cmdcntr) reported 28 minutes ago

  Spicy take. '''Free unlimited AI coding''' repos keep going viral on GitHub. It'''s not innovation. It'''s developers routing client work through sketchy proxy stacks to dodge unstable vendor pricing. A vendor problem dressed up as a hacker win.

• 
  Daniel Dunderfelt (@ddunderfelt) reported 29 minutes ago

  @Ethan_Smartsys The hack exploited Github workflows cache poisoning, which has afaik been an issue for a while. Also NPM could easily do more security scanning.

• 
  Wolf Byte (@W0lf_Byt3) reported 29 minutes ago

  Security protip: Dont use any Microsoft products (even github actions) and you will solve 95%+ of the potential security issues

• 
  luckyPipewrench (@luckyPipewrench) reported 31 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.

• 
  Senior PowerPoint Engineer (@ryxcommar) reported 32 minutes ago

  Github Actions needs to get their **** together. All the recent GA-based supply chain attacks and vulnerabilities-- LiteLLM, Trivy, Tanstack, nx-- are theoretically preventable if you know way too much about Github Actions footguns: hashes for uses, don't store PATs in pull_request_target (or maybe don't use pull_request_target at all, even "securely"), never use classic PATs (unless you need to, of course, which you might because Github *still* doesn't support all features with fine-grained access control). But it's also ridiculous that's the state of things. The entire software supply chain shouldn't be dependent on 100% of the maintainers of the hundreds of dependencies we're downloading indiscriminately knowing the nuances of Github Actions security. Unlike all the AI agents yeeting bullshit code to Github's servers and overwhelming it, all of these security issues with Github Actions have been known for a long while. It doesn't seem like Github has the ***** to mildly inconvenience people by deprecating classic PATs or forcing commit hashes for 3rd party actions or what have you so I guess this will just be how things are forever.

• 
  Renato Villanueva (@_renatov) reported 32 minutes ago

  Deleted some old repos of projects I had started but they ended up not being used. about 2/3 of my total github contributions went away too... lesson: plan better and pick better problems

• 
  Curlheinz (@Curlh1) reported 33 minutes ago

  @mdnlabs I take 10 screenshots from my app Then i ask Claude Codex to search online and in GitHub for a mockup png frame of a free licensed phone and fill that with l screenshots Then I say: Generate a webpage for me that contains my screenshots I want to run it in a dev server with npm run dev (vite) I want an export button that exports the screenshots to Apple 6.5 6.7 6.9 something inch what we need in 2026 and Google with other weird ARs And then I iterate until I like the design and tell it to tilt the image a bit and so on. I watch it live update my dev server and vibe it into existence It will also read screenshots and propose headers

• 
  Kendall Chuang (@kendallchuang) reported 37 minutes ago

  Startup idea -- a native app for Github PR reviews. It should be able to easily render, and allow review and in-line comment threads on rendered Markdown files. With spec-driven development, being able to share and get peer review on markdown files is a key part of the developer workflow. Copy-pasting Markdown to Google Docs feels tedious and creates sync issues with the source-controlled Markdown, losing the comments when pasting back into the repo.

• 
  Jekson (@Jekson1pp) reported 51 minutes ago

  Nobody noticed this repo until Big Tech started paying lawyers to make it disappear. Invidious. An open-source, privacy-first frontend for YouTube. No ads. No tracking. No algorithm feeding you outrage. Just the video you came to watch. On the surface: a clean GitHub README. AGPL-3.0 license. A bird from Big Buck Bunny playing in the preview. Community chat on Matrix, IRC, Fediverse. Looks like a quiet indie project maintained by a few idealists. Pause here. Look past the screenshots. 275 commits per year. 403 open issues. 77 pull requests. A distributed instances list — meaning no single server to shut down. 78% translated into other languages. 477 users actively coordinating on Matrix right now. This isn't a side project. This is infrastructure. The real signal is the architecture. Invidious doesn't ask YouTube's permission to exist. It reverse-engineers the public interface, strips the surveillance layer, and serves you the content through self-hosted nodes. When Google blocks one instance, another spins up. The network is the product. The "humane tech" badge isn't branding — it's a declaration of intent. Here's why this is the 2026 meta that most people are missing. The creator economy just hit a wall. Monetization is being strangled by opaque algorithm changes, ad revenue collapse, and platform lock-in. Simultaneously, the open-source infrastructure to route around these platforms has quietly matured. Invidious exists. PeerTube exists. Nostr exists. The pipes are ready. While everyone else is debating whether to post Shorts or long-form, a parallel internet is being assembled piece by piece, repo by repo. The catch — and this is what the mainstream tech conversation never addresses — is distribution. Open infrastructure without distribution is a library in the woods. Beautiful. Empty. Invidious solves the consumption layer. It doesn't solve discovery. That's the next frontier, and whoever builds a decentralized recommendation layer on top of this stack owns the next decade of attention. Most people will scroll past this repo and see a niche tool for privacy nerds. What they're missing: every major platform shift in the last 20 years started as a "niche tool for nerds." RSS. Bittorrent. Email encryption. The pattern is always the same — the infrastructure arrives years before the mainstream moment. The people who understood the infrastructure early built the products that captured the wave. The open-source YouTube alternative wasn't the story. The story is that the replacement stack for the attention economy is already built, already running, already global — and almost nobody building consumer products is paying attention to it. Everything else is cope.

• 
  Isaac (@Dever401) reported 54 minutes ago

  @getordiaapp GitHub-only risk detection sounds useful if the output is painfully concrete: blocked issue, stale PR, missing owner, slipping milestone, next action. Tiny teams don't need another dashboard; they need a weekly 'what is about to hurt us' view from tools they already trust.

• 
  Anže Matelič (@amatelic93) reported 55 minutes ago

  @adibhanna But couldn’t this happens here too? Seems like the issue was with the cache storing on GitHub?

• 
  Vaibhav Khulbe (@vaibhav_khulbe) reported 55 minutes ago

  @konrad_matej @framer background: transparent; is just so 🤮 Great to know it's fixed now. I remember we also had an issue over GitHub where I also chimed in and commented for Electron team to fix it.