- Level
- confirmed
- Worst impact
- Degraded
- Components
- www.npmjs.com website
- Down Index
- 23of 100
What to do
Check whether you use npm www.npmjs.com website. 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 37m it lasted.
Anything that failed between 2026-03-31 19:12 UTC and 2026-03-31 21:49 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 4
- investigating
We are seeing degraded performance in package viewing and authentication on npmjs website. We are currently investigating the issue.
provider
- investigating
We have implemented initial fixes and are continuing to investigate this issue
provider
- monitoring
A fix has been implemented and we are monitoring 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-030977380a
Is npm still down?
No, this incident was resolved 2026-03-31 21:49 UTC. For npm's live state, see https://down.guide/npm.
How long did it last?
2h 37m, from 2026-03-31 19:12 UTC to 2026-03-31 21:49 UTC, by the times npm posted.
What was affected?
npm named www.npmjs.com website.
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.