npm: Degraded Package Install Experience

What to do

Check whether you use npm Package installation. Check your stack
Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.
Confirm your retries, queues and scheduled jobs caught up after the 3h 9m it lasted.
Anything that failed between 2025-08-26 12:40 UTC and 2025-08-26 15: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.

investigatingAug 26, 2025, 12:40 PM UTC
We are investigating an issue where users are experiencing failures during npm install. Errors observed include 429 Too Many Requests and 403 Forbidden for GitHub Actions.
provider
investigatingAug 26, 2025, 12:41 PM UTC
We are continuing to investigate this issue.
provider
identifiedAug 26, 2025, 2:27 PM UTC
The issue has been identified and a fix is being implemented.
provider
monitoringAug 26, 2025, 3:15 PM UTC
A fix has been implemented and we are monitoring the results.
provider
monitoringAug 26, 2025, 3:16 PM UTC
We are continuing to monitor for any further issues.
provider
resolvedAug 26, 2025, 3:49 PM UTC
This incident has been resolved.
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-08-26 15:49 UTC. For npm's live state, see https://down.guide/providers/npm.

How long did it last?

3h 9m, from 2025-08-26 12:40 UTC to 2025-08-26 15:49 UTC, by the times npm posted.

What was affected?

npm named Package installation.

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.