Package Install failures due to "304 Not Modified" responses in Mumbai, India region
Dec 17, 12:50 UTCDec 17, 16:19 UTC
Duration
3h 29m
Impact
Major
Root cause
Not disclosed
npm, 90 days
7 incidents
Affected
Package installation
Final update
This incident has been resolved.
Timeline
- Resolved · Dec 17, 16:19 UTC
This incident has been resolved.
- Monitoring · Dec 17, 15:43 UTC
A fix has been implemented and we are monitoring the results.
- Identified · Dec 17, 14:37 UTC
The issue has been identified and a fix is being implemented.
- Investigating · Dec 17, 12:50 UTC
We are currently investigating failures to install packages due to TAR_BAD_ARCHIVE or 304 Not Modified responses for clients in Mumbai, India.
More from npm
Full history| Started | Incident | Impact | Duration |
|---|---|---|---|
| Sep 1517:20 UTC | Package Publish Degradation | minor | 1h |
| Sep 1516:13 UTC | Publishing Packages Degraded Performance | minor | 22m |
| Sep 411:29 UTC | npm audits endpoint is having issues | minor | 2h 20m |
| Sep 321:42 UTC | Intermittent Failures Impacting npm Publish | minor | 1h 39m |
| Jul 3012:06 UTC | intermittent Publish Failures | minor | 4h 24m |
| Jul 2411:08 UTC | Publish and Install failures | major | 31m |
From vendors' own status pages and disclosures. Times as reported. Logos via logo.dev; trademarks belong to their owners.