npm.com hit a major outage on Apr 27, 2026 at 21:06 UTC; package installation, publishing, search, and security audit all stayed operational.
Key Takeaways
Only the www.npmjs.com website frontend was affected; the registry itself remained fully operational, meaning CI pipelines and npm install were unimpacted.
npm’s 90-day website uptime sat at 99.95% before this incident, marking it as a rare but real failure for one of the most-trafficked developer portals.
The status page logged an unresolved incident as of the 21:06 UTC update with no ETA or root cause posted.
Package publishing, search, security audit, and the replication feed each showed 99.98-100% uptime over 90 days, isolating the failure cleanly to the web layer.
Hacker News Comment Review
The simultaneous GitHub outage led several commenters to suspect a shared Azure infrastructure failure underneath both services, since npm is Microsoft-owned via GitHub.
eBay was independently reported down around the same window, muddying the Azure theory and suggesting a possible broader CDN or cloud provider event.
Dark humor dominated: supply chain security jokes and calls to keep npm offline permanently reflect long-running community frustration with the registry’s historical reliability and security posture.
Notable Comments
@corvad: Flagged the GitHub-plus-npm overlap as evidence of a shared Azure infra root cause.
@cozzyd: “That’s one way to fix supply chain vulnerabilities.”
