Minor impactResolvedDevOps

npm incident: Issues publishing and installing packages

npm reported this minor-impact incident on its official status page on Apr 11, 2025, 02:46 UTC. It was resolved after 12h 5m.

Right now npm is operational. Live npm status →

🔔 Get alerted when npm has issuesFree · email alerts · no credit card
Apr 11, 2025, 02:46 UTC
started
Apr 11, 2025, 14:51 UTC
resolved
12h 5m
duration
Minor
impact

Affected components

  • Package installation
  • Package publishing

Timeline

updates from npm's status page ↗
  1. resolvedApr 11, 2025, 14:51 UTC

    This incident was caused due to an internal bug during regular database maintenance, its resolved now.

  2. monitoringApr 11, 2025, 12:52 UTC

    We are monitoring results

  3. identifiedApr 11, 2025, 08:32 UTC

    We are continuing to work on a fix to restore older access tokens.

  4. identifiedApr 11, 2025, 05:37 UTC

    The issue has been identified and a fix is being implemented.

  5. investigatingApr 11, 2025, 02:46 UTC

    We are investigating issues with access tokens, in the meantime user can recreate new tokens to unblock themselves.

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.

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: Issues publishing and installing packages (Apr 5, 2025)Next: Issues with package install, package publish, and login. (Jun 12, 2025) →
npm incident on Apr 11, 2025: Issues publishing and installing packages · APIStatus.watch