Minor impactResolvedDevOps

npm incident: Degraded Performance in View Package and Login on npmjs.com

npm reported this minor-impact incident on its official status page on Mar 31, 2026, 19:12 UTC. It was resolved after 2h 37m.

Right now npm is operational. Live npm status →

🔔 Get alerted when npm has issuesFree · email alerts · no credit card
Mar 31, 2026, 19:12 UTC
started
Mar 31, 2026, 21:49 UTC
resolved
2h 37m
duration
Minor
impact

Affected components

  • www.npmjs.com website
  1. resolvedMar 31, 2026, 21:49 UTC

    This incident has been resolved.

  2. monitoringMar 31, 2026, 21:12 UTC

    A fix has been implemented and we are monitoring the results.

  3. investigatingMar 31, 2026, 20:42 UTC

    We have implemented initial fixes and are continuing to investigate this issue

  4. investigatingMar 31, 2026, 19:12 UTC

    We are seeing degraded performance in package viewing and authentication on npmjs website. We are currently investigating the 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.

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

npm incident on Mar 31, 2026: Degraded Performance in View Package and Login on npmjs.com · APIStatus.watch