npm: Issues publishing and installing packages

What to do

Check whether you use npm Package installation, Package publishing. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
Confirm your retries, queues and scheduled jobs caught up after the 12h 5m it lasted.
Anything that failed between 2025-04-11 02:46 UTC and 2025-04-11 14:51 UTC may need a replay.
Subscribe to npm's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=npm works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

investigatingApr 11, 2025, 2:46 AM UTC
We are investigating issues with access tokens, in the meantime user can recreate new tokens to unblock themselves.
provider
identifiedApr 11, 2025, 5:37 AM UTC
The issue has been identified and a fix is being implemented.
provider
identifiedApr 11, 2025, 8:32 AM UTC
We are continuing to work on a fix to restore older access tokens.
provider
monitoringApr 11, 2025, 12:52 PM UTC
We are monitoring results
provider
resolvedApr 11, 2025, 2:51 PM UTC
This incident was caused due to an internal bug during regular database maintenance, its resolved now.
provider

Reports count in aggregate; nothing about you is shown.

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Is npm still down?

No, this incident was resolved 2025-04-11 14:51 UTC. For npm's live state, see https://down.guide/npm.

How long did it last?

12h 5m, from 2025-04-11 02:46 UTC to 2025-04-11 14:51 UTC, by the times npm posted.

What was affected?

npm named Package installation, Package publishing.

What caused it?

npm hasn't published a root cause. If it does, it shows here.

Where does this come from?

npm's official status page, https://status.npmjs.org, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.