Minor impactResolvedDevOps

npm incident: Degraded performance for package publish

npm reported this minor-impact incident on its official status page on Mar 5, 2026, 11:41 UTC. It was resolved after 5h 55m.

Right now npm is operational. Live npm status →

🔔 Get alerted when npm has issuesFree · email alerts · no credit card
Mar 5, 2026, 11:41 UTC
started
Mar 5, 2026, 17:35 UTC
resolved
5h 55m
duration
Minor
impact

Affected components

  • Package publishing

Timeline

updates from npm's status page ↗
  1. resolvedMar 5, 2026, 17:35 UTC

    This incident has been resolved.

  2. monitoringMar 5, 2026, 13:01 UTC

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

  3. investigatingMar 5, 2026, 11:41 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.

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 with package installation (Feb 25, 2026)Next: Issue with npm website and login. (Mar 25, 2026) →
npm incident on Mar 5, 2026: Degraded performance for package publish · APIStatus.watch