npm: Package Install failures due to "304 Not Modified" responses in Mumbai, India region

What to do

Check whether you use npm Package installation in apac, in. 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 3h 29m it lasted.
Anything that failed between 2024-12-17 12:50 UTC and 2024-12-17 16:19 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.

investigatingDec 17, 2024, 12:50 PM UTC
We are currently investigating failures to install packages due to TAR_BAD_ARCHIVE or 304 Not Modified responses for clients in Mumbai, India.
provider
identifiedDec 17, 2024, 2:37 PM UTC
The issue has been identified and a fix is being implemented.
provider
monitoringDec 17, 2024, 3:43 PM UTC
A fix has been implemented and we are monitoring the results.
provider
resolvedDec 17, 2024, 4:19 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 2024-12-17 16:19 UTC. For npm's live state, see https://down.guide/npm.

How long did it last?

3h 29m, from 2024-12-17 12:50 UTC to 2024-12-17 16:19 UTC, by the times npm posted.

What was affected?

npm named Package installation in apac, in.

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.