- Level
- confirmed
- Worst impact
- Degraded
- Components
- www.npmjs.com website
- Down Index
- 24of 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 5h 37m it lasted.
Anything that failed between 2025-11-18 13:34 UTC and 2025-11-18 19:11 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 currently investigating intermittent connectivity issues affecting npmjs.com. Our team is actively working to restore full service. We apologize for any inconvenience and will provide updates as we learn more.
provider
- monitoring
A fix has been implemented and we are monitoring the results.
provider
- monitoring
This incident has been resolved. All services are now operating normally. We apologize for the disruption and appreciate your patience.
provider
- resolved
We have confirmed that all systems are now fully operational and the connectivity issues have been completely 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-ec000a6e57
Is npm still down?
No, this incident was resolved 2025-11-18 19:11 UTC. For npm's live state, see https://down.guide/npm.
How long did it last?
5h 37m, from 2025-11-18 13:34 UTC to 2025-11-18 19:11 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.