Skip to main content
npm

Incident with npm registry and website affecting logins and publishing

Degraded Lasted 34m · started · npm's page

Level
confirmed
Worst impact
Degraded
Components
www.npmjs.com website, Package installation, Package publishing, Security Audit
Down Index
29of 100

What to do

  • Check whether you use npm www.npmjs.com website, Package installation, Package publishing, Security Audit. 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 34m it lasted.

    Anything that failed between 2025-08-07 22:31 UTC and 2025-08-07 23:05 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

  1. investigating

    We are currently investigating this issue.

    provider

  2. monitoring

    The issue has been identified and a remediation is being put into place.

    provider

  3. 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-96f564eea5

Is npm still down?

No, this incident was resolved 2025-08-07 23:05 UTC. For npm's live state, see https://down.guide/npm.

How long did it last?

34m, from 2025-08-07 22:31 UTC to 2025-08-07 23:05 UTC, by the times npm posted.

What was affected?

npm named www.npmjs.com website, Package installation, Package publishing, Security Audit.

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.