--- title: npm is having an outage and nobody can do anything about it description: npm is experiencing a widespread outage affecting package publishing and installation. New packages are taking up to 30 minutes to become available, downloads... canonical: https://daily.dev/posts/npm-is-having-an-outage-and-nobody-can-do-anything-about-it-mbsltgflx twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: npm is having an outage and nobody can do anything about it | daily.dev og:description: npm is experiencing a widespread outage affecting package publishing and installation. New packages are taking up to 30 minutes to become available, downloads... og:url: https://daily.dev/posts/npm-is-having-an-outage-and-nobody-can-do-anything-about-it-mbsltgflx og:image: https://api.daily.dev/og/posts/mBsLTgflx.png og:image:alt: npm is having an outage and nobody can do anything about it og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # npm is having an outage and nobody can do anything about it **[Trends](https://daily.dev/sources/trends)** · 2 min read · 6 upvotes · 2 comments ## Summary npm is experiencing a widespread outage affecting package publishing and installation. New packages are taking up to 30 minutes to become available, downloads of indexed packages are failing, and provenance data isn't updating correctly outside version-specific pages. One developer reported a package stuck in a 'Validating' state for over 25 minutes while dependent packages that reference it are already failing installs. A partial workaround using `npm i --no-audit` bypasses the timeout, suggesting the audit service may be the bottleneck. No official status update from npm has been issued, and publishers have no way to unpublish, retry, or communicate the issue to their users. ## Content npm is broken right now, and the frustrating part is there's nothing you can do. The symptoms are all over the place. Armin Ronacher (mitsuhiko) noticed new packages taking up to 30 minutes to become available after publishing, which is bad enough that he's seriously considering dropping npm as the distribution channel for pip. Theo reports that even packages that eventually get indexed are refusing to download, and provenance data isn't updating properly — only showing up on version-specific pages rather than the main listing. Devon Govett hit the sharpest edge of this: he published a package that's been stuck in "Validating" for 25+ minutes, other packages that depend on it have already published, and now their installs are failing on a dependency that technically exists but isn't reachable. No error message, no recourse, just a spinner. Mitsuhiko also found a partial workaround: `npm i --no-audit` gets installs through when the normal path times out. Which suggests the audit service is either the bottleneck or completely wedged. The broader frustration here isn't just the outage — it's the helplessness. When npm's validation pipeline stalls, publishers are stuck. You can't unpublish, you can't force a retry, you can't tell your users anything except "wait." For a piece of infrastructure this central to the JS ecosystem, that's a rough place to be. No official status update from npm at time of writing. ## Questions this post answers ### Why is npm install failing or hanging right now for packages that were just published? npm's validation pipeline was stalling, causing newly published packages to sit in a 'Validating' state for 25 minutes or more before becoming reachable, while dependent packages that already referenced them failed to install. Provenance data was also failing to update outside version-specific pages, and the audit service appeared to be a bottleneck, since installs would go through with the --no-audit flag. _developers hit by npm registry hiccups can follow real-time reports of outages like this on daily.dev._ ### Is there a workaround for npm installs timing out during a registry outage? Running npm install with the --no-audit flag has let installs complete when the normal path times out, suggesting the audit service is the bottleneck or is completely wedged during the outage. This does not fix broken provenance data or packages stuck in validation, but it can unblock installs that are otherwise hanging indefinitely. _teams debugging flaky CI installs can track community workarounds for npm issues via daily.dev._ ## Community discussion Top comments from developers on daily.dev. **@roberteisele** · 3 upvotes > Isn't this the price for centralization? The community silently agreed on this SPOF. **@5awtooth** · 1 upvotes > They are scanning packages now, from my understanding. Since all of the supply chain attacks recently; someone is actually doing something about this problem. > > Not sure about the bandwidth, but I think the system will even out soon once the cost tapers out. > > The price is to wait 30-60 minutes. I usually wait a day for any other submission(Epic Games, Apple..) so I prefer safer packages then on demand publishing considering all that has happened. ## Similar posts on daily.dev - [npm now freezes high-impact accounts after risky account changes](https://daily.dev/posts/npm-now-freezes-high-impact-accounts-after-risky-account-changes-k0mcnquls) · Aikido Security · 3 upvotes · 0 comments - [npm's Defaults Are Bad](https://daily.dev/posts/npm-s-defaults-are-bad-2fqdhx40i) · Andrew Nesbitt · 21 upvotes · 2 comments - [GitHub Hardens npm and Actions Defaults, Drawing Debate over Delays versus Signing](https://daily.dev/posts/github-hardens-npm-and-actions-defaults-drawing-debate-over-delays-versus-signing-velrggpfa) · InfoQ · 0 upvotes · 0 comments --- Tags: [#javascript](https://daily.dev/tags/javascript), [#cicd](https://daily.dev/tags/cicd), [#npm](https://daily.dev/tags/npm) [View this post on daily.dev](https://daily.dev/posts/npm-is-having-an-outage-and-nobody-can-do-anything-about-it-mbsltgflx) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"npm is having an outage and nobody can do anything about it","url":"https://daily.dev/posts/npm-is-having-an-outage-and-nobody-can-do-anything-about-it-mbsltgflx","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/npm-is-having-an-outage-and-nobody-can-do-anything-about-it-mbsltgflx"},"datePublished":"2026-09-07T01:00:43.376Z","dateModified":"2026-09-13T19:34:14.011Z","description":"npm is experiencing a widespread outage affecting package publishing and installation. New packages are taking up to 30 minutes to become available, downloads...","image":"https://pbs.twimg.com/media/HRk08AdaMAA9SRp.jpg","thumbnailUrl":"https://pbs.twimg.com/media/HRk08AdaMAA9SRp.jpg","isAccessibleForFree":true,"articleSection":"Trends","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Trends","logo":"https://media.daily.dev/image/upload/s--ZfSp3asX--/f_auto,q_auto/v1780996004/logos/trends?_a=BAMAMiWQ0","url":"https://daily.dev/sources/trends"},"commentCount":2,"discussionUrl":"https://daily.dev/posts/npm-is-having-an-outage-and-nobody-can-do-anything-about-it-mbsltgflx","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":6},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":2}],"keywords":"javascript,cicd,npm","timeRequired":"PT2M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Trends","item":"https://daily.dev/sources/trends"},{"@type":"ListItem","position":3,"name":"npm is having an outage and nobody can do anything about it"}]} {"@context":"https://schema.org","@type":"WebPage","@id":"https://daily.dev/posts/npm-is-having-an-outage-and-nobody-can-do-anything-about-it-mbsltgflx","comment":[{"@type":"Comment","text":"Isn’t this the price for centralization? The community silently agreed on this SPOF.","datePublished":"2026-09-07T06:36:56.428Z","url":"https://daily.dev/posts/mBsLTgflx#c-7FOzyZ3Tp","author":{"@type":"Person","name":"Robert Eisele","url":"https://daily.dev/roberteisele","image":"https://media.daily.dev/image/upload/s--dVMLlXHw--/f_auto/v1788168114/avatars/avatar_LIKrx7ljJ3y1uDVMT5qUX?_a=BAMAMicg0"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":3}},{"@type":"Comment","text":"They are scanning packages now, from my understanding. Since all of the supply chain attacks recently; someone is actually doing something about this problem.\nNot sure about the bandwidth, but I think the system will even out soon once the cost tapers out.\nThe price is to wait 30-60 minutes. I usually wait a day for any other submission(Epic Games, Apple…) so I prefer safer packages then on demand publishing considering all that has happened.","datePublished":"2026-09-12T23:54:10.332Z","url":"https://daily.dev/posts/mBsLTgflx#c-S2AKOJs9Q","author":{"@type":"Person","name":"David Clabaugh","url":"https://daily.dev/5awtooth","image":"https://avatars.githubusercontent.com/u/8500545?v=4"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1}}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/npm-is-having-an-outage-and-nobody-can-do-anything-about-it-mbsltgflx#faq","mainEntity":[{"@type":"Question","name":"Why is npm install failing or hanging right now for packages that were just published?","acceptedAnswer":{"@type":"Answer","text":"npm's validation pipeline was stalling, causing newly published packages to sit in a 'Validating' state for 25 minutes or more before becoming reachable, while dependent packages that already referenced them failed to install. Provenance data was also failing to update outside version-specific pages, and the audit service appeared to be a bottleneck, since installs would go through with the --no-audit flag. developers hit by npm registry hiccups can follow real-time reports of outages like this on daily.dev."}},{"@type":"Question","name":"Is there a workaround for npm installs timing out during a registry outage?","acceptedAnswer":{"@type":"Answer","text":"Running npm install with the --no-audit flag has let installs complete when the normal path times out, suggesting the audit service is the bottleneck or is completely wedged during the outage. This does not fix broken provenance data or packages stuck in validation, but it can unblock installs that are otherwise hanging indefinitely. teams debugging flaky CI installs can track community workarounds for npm issues via daily.dev."}}]} ```