- Level
- confirmed
- Worst impact
- Degraded
- Components
- Package publishing
- Down Index
- 23of 100
What to do
Check whether you use npm 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 2h 55m it lasted.
Anything that failed between 2025-10-20 17:20 UTC and 2025-10-20 20:15 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.
Updates from npm 3
- investigating
We are currently investigating this issue.
provider
- monitoring
We are seeing recovery in package publishing. We will continue to monitor the results.
provider
- resolved
This incident has been resolved.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-b7d22ff8f8
Is npm still down?
No, this incident was resolved 2025-10-20 20:15 UTC. For npm's live state, see https://down.guide/npm.
How long did it last?
2h 55m, from 2025-10-20 17:20 UTC to 2025-10-20 20:15 UTC, by the times npm posted.
What was affected?
npm named 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.