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

• 
  Jekson (@Jekson1pp) reported 6 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.

• 
  Solomon Eseme (@Kaperskyguru) reported 12 minutes ago

  The real problem is not what you know. It's what you can't show. Hiring managers don't care how many courses you took. They want to see what you built. What problem you solved. What decision you made. A GitHub full of tutorial clones tells them nothing.

• 
  John Renfro 🇺🇸 (@JohnRenfro2016) reported 12 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

• 
  Solomon Eseme (@Kaperskyguru) reported 13 minutes ago

  Building projects is not enough either. I've seen developers with 20+ GitHub repos still fail interviews. Why? The projects don't tell a story. Each project should answer: what real problem did this solve and how? A URL shortener you built in 45 minutes doesn't count.

• 
  Incultnito Studios (@Incultnito) reported 13 minutes ago

  Scorecard: modelcontextprotocol/server-github (legacy Node v2025.4.8) — 3 of 26 tools callable on a cold run. Still installed by older Claude Desktop configs. Probed with mcp-probe (incultnitollc/mcp-probe on npm).

• 
  Mario Figueiredo (@fromdevoid) reported 15 minutes ago

  @sporadica Briefly, they got they 42 of their packages compromised and pushed into npm, by a chain-attack involving a known PR workflow issue they didn't protect against and a documented Github Actions design flaw they couldn't protect against.

• 
  Kyle TechSquidTV (@TechSquidTV) reported 15 minutes ago

  I really hate that GitHub makes you login with SSO on SAML orgs, to just view a public page. Don't want to authenticate? You can see the same content via Incognito mode. Make that make sense

• 
  patrick.algo (@patrickbennett) reported 18 minutes ago

  @mitsuhiko No it’s a damn package manager that will run any executable code attached to a dependency. Should be hard blocked. Disabled by default. Allow list only. Explicit hash. GitHub protection defaults that block changes except by owners. No clue why it hasn’t already been locked down. Start with using pnpm at least.

• 
  Kendall Chuang (@kendallchuang) reported 22 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.

• 
  Mario Figueiredo (@fromdevoid) reported 28 minutes ago

  @sporadica They got they 42 of their packages compromised and pushed into npm, by a chain-attack involving a known PR workflow issue they didn't protect against and a documented Github action design flaw they couldn't protect against.

• 
  Fabian (@fabi98_6) reported 37 minutes ago

  @PicklePioneer yeah its so ******* insane I wish microsoft would get their **** together and fix npm + github

• 
  mary🐇 (@mary_ext) reported 38 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.

• 
  Jarred Sumner (@jarredsumner) reported 38 minutes 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.

• 
  Galileo (@rungalileo) reported 40 minutes ago

  Agents are smart enough to find workarounds, and you need controls mapped at the tool level: which MCP servers are permitted, which operations are allowed, and which get blocked before they ever execute. When third-party agents are connected to GitHub, they can read your repos, write to them, delete files, and merge pull requests. In this demo, our Forward Deployed Engineer, @mike_branc, walks through how to layer Agent Control on top of Cursor using hooks to intercept every MCP call before it reaches the GitHub server and evaluate it against a defined policy. Read-only queries pass through. Anything that touches writes, deletes, or merges is blocked before execution. When Cursor was asked to delete a README, Agent Control denied the request and surfaced the exact control that was triggered. The GitHub MCP is one example. The same pattern applies to any third-party agent your team is running: identify the risk factors, define the controls, and enforce them at every possible path. Watch the full demo below 👇

• 
  Georgii Tselkovskii (@Existentios) reported 40 minutes ago

  It has never been cheaper to build a startup. Claude for coding — $20/mo Supabase for backend — free Vercel for deploys — free Namecheap for domain — $20/yr Stripe for payments — % only GitHub for version control — free Resend for emails — free Clerk for auth — free Cloudflare for DNS — free PostHog for analytics — free Sentry for error tracking — free Upstash for Redis — free Pinecone for vector DB — free You can literally launch with ~$20/month. The hard part is no longer building. The hard part is getting people to care.

• 
  Vishal Lohar (@yourcodebuddy) reported 40 minutes ago

  How does @EffectTS_ suggest building APIs? Pure Effect or @honojs/@elysiaJS + Effect? And, I couldn't find any benchmarks comparing all the options. Found a GitHub repo by Backpine Labs where he used Pure Effect to build an API server. It was cool, and I didn't know it was possible.

• 
  saburo (@jskoiz) reported 41 minutes ago

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

• 
  M. Yahia (@maddada) reported 41 minutes ago

  @robinebers Github and npm could do so much to stop these in their tracks. I mean socket detected the issue within 6 minutes, but Microsoft couldn't do any scans to catch this? They're dropping the ball do hard.

• 
  Kamraj (@KamrajShahapure) reported 42 minutes ago

  I thought GitLab would be the beneficiary of the GitHub reliability issues, but doesn't seem like it

• 
  Incultnito Studios (@Incultnito) reported 42 minutes ago

  Not entirely the maintainer story it looks like. Anthropic moved the official GitHub MCP to Go (github/github-mcp-server, 29.5k stars). The Node v2025.4.8 build is legacy — but it is still on npm and still in user configs in the wild.

• 
  Vaibhav Khulbe (@vaibhav_khulbe) reported 43 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.

• 
  Akshay from Startup Spells 🪄 (@StartupSpells) reported 43 minutes ago

  @charliermarsh @jarredsumner I feel like its mostly segfault issues + zig moving off github & all. most unknown issues that aren't language-related can be fixed & rust has a big community. cant beat big community, right? been seeing rust being #1 in stackoverflow since 2018-20 or something

• 
  alkimiadev (@alkimiadev) reported 46 minutes ago

  @m13v_ @SocketSecurity I've switched to forking/vendoring libs I use. I saw some issues coming with github so I jumped ship before the recent mess and started self-hosting ***. The long term maintenance costs for maintaining well written libs is trending towards $0 with llms becoming more and more capable while the long term supply chain attack risk seems to be growing over time. Although that last part could just be recency bias since there have been several high profile incidents in recent times. Its kind of messy to determine it is a legitimate growing trend or a combination of a recent spike and the recency bias. That spike doesn't necessarily mean it actually is a growing threat. That said, I'm working under the "better safe than sorry" mindset and just forking/vendoring almost everything I use.

• 
  Hammad (@hammadtariq) reported 49 minutes ago

  github is down? we finally broke it?

• 
  Don Montegarza (@aiDidThisToo) reported 55 minutes ago

  @_lopopolo i do it like this now. and it works most of the time for me. but its so unatural to do really. with 5.4 it just know it goal: publish xxx-server images to dockerhub for version 1.2.0_betax using ci github action success: xxx-server 1.2.0_beta9 published on docker hub constraint: use the existint tag that already exist, bypass the test check etc, directly push the existing created images, use exsting github ci action docker release. output: xxx-server images published

• 
  Justin Schroeder (@jpschroeder) reported 57 minutes ago

  @ThePrimeagen If you look into it this is actually another GitHub issue

• 
  The Cyber Jim (@thecyberjim) reported 58 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.

• 
  Oluwamayowa (@oluwamayowa) reported 1 hour ago

  It starts with Sources. Vyrric can ingest support conversations, tickets, survey responses, reviews, product analytics, Slack messages, GitHub issues, uploaded transcripts, PDFs, docs, and text evidence. Each source gets synced, indexed, and monitored.

• 
  merlin (@merlinaudio_) reported 1 hour ago

  @jarredsumner why not test if it *really would* close the github issues? surely claude can whip up a repro in 1.3.14 and then run it in the rust rewrite.

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