Critical impactResolvedDevOps

npm outage: npm Website is unavailable

npm reported this critical-impact incident on its official status page on Apr 27, 2026, 21:06 UTC. It was resolved after 1h 24m.

Right now npm is operational. Live npm status →

🔔 Get alerted when npm has issuesFree · email alerts · no credit card

Apr 27, 2026, 21:06 UTC

started

Apr 27, 2026, 22:30 UTC

resolved

1h 24m

duration

Critical

impact

Affected components

www.npmjs.com website

Timeline

updates from npm's status page ↗

resolvedApr 27, 2026, 22:30 UTC
This incident has been resolved.
investigatingApr 27, 2026, 22:28 UTC
We are continuing to investigate this issue.
investigatingApr 27, 2026, 21:06 UTC
We are currently investigating this issue.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in npm's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

1Password: Login and Sync IssuesCritical · Apr 27, 2026, 14:54 UTC
Snyk: Snyk recurring tests showing slow performanceMinor · Apr 21, 2026, 18:58 UTC
Mux: Issues downloading MP4 assetsMinor · Apr 27, 2026, 20:08 UTC

How often does npm have incidents?

npm reported 8 incidents in the last 90 days, 1 of them major or critical. A typical incident lasted 1h 59m. See npm's uptime and incident history

← Previous: Degraded Performance in View Package and Login on npmjs.com (Mar 31, 2026)Next: npm website degraded service (Apr 28, 2026) →