What visitors reported during this incident
No visitor reports were filed for this incident.
Having problems with npm now? Check the current statusAffected services
Package installationPackage publishing
Updates (5)
- Apr 11, 2025, 02:51 PMIssues publishing and installing packages
This incident was caused due to an internal bug during regular database maintenance, its resolved now.
npm ↗ - Apr 11, 2025, 12:52 PMIssues publishing and installing packages
We are monitoring results
npm ↗ - Apr 11, 2025, 08:32 AMIssues publishing and installing packages
We are continuing to work on a fix to restore older access tokens.
npm ↗ - Apr 11, 2025, 05:37 AMIssues publishing and installing packages
The issue has been identified and a fix is being implemented.
npm ↗ - Apr 11, 2025, 02:46 AMIssues publishing and installing packages
We are investigating issues with access tokens, in the meantime user can recreate new tokens to unblock themselves.
npm ↗
What to do next
- Verify your own services recovered cleanly. Some upstream outages leave queues or caches in a degraded state, run smoke tests before declaring green internally.
- Save the post-mortem. Vendors usually publish a detailed RCA 1-3 days later. We'll add it to this page when it appears.
- Watch the provider going forward. Follow npm's status feed →
GlobalOutageMap aggregates publicly reported signals. We never claim authoritative status, always cross-check the provider's official channel before making business decisions.