The npm website went down on Apr 27, 2026 at 21:06 UTC; package installation, publishing, search, and replication remained operational.
Key Takeaways
Only the www.npmjs.com website is affected; core services (installation, publishing, search, security audit, replication feed) show operational status.
npm’s status page shows 99.95% uptime over the prior 90 days, making this a rare major outage for the website layer.
The incident was unresolved as of the status update timestamp; no root cause was disclosed.
No other incidents were reported in the preceding 13 days, isolating this as a sudden event rather than a pattern.
Hacker News Comment Review
Commenters immediately tied the outage to concurrent GitHub instability, pointing to a shared Azure infrastructure dependency as the likely common cause.
The thread surfaced latent frustration with npm and GitHub’s consolidation under Microsoft, with at least one commenter floating Cloudflare as a potential alternative registry host.
One commenter made a dry supply-chain security joke, reflecting the community’s running wariness about centralized npm as an attack surface.
Notable Comments
@corvad: Flags possible Azure infra link between the simultaneous npm and GitHub outages.
@xmprt: Raises whether Cloudflare or another provider could step in with a competing registry service.
@cozzyd: “That’s one way to fix supply chain vulnerabilities.”
