Major impactResolvedDevOps

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

npm reported this major-impact incident on its official status page on Dec 17, 2024, 12:50 UTC. It was resolved after 3h 29m.

Right now npm is operational. Live npm status →

🔔 Get alerted when npm has issuesFree · email alerts · no credit card
Dec 17, 2024, 12:50 UTC
started
Dec 17, 2024, 16:19 UTC
resolved
3h 29m
duration
Major
impact

Affected components

  • Package installation

Timeline

updates from npm's status page ↗
  1. resolvedDec 17, 2024, 16:19 UTC

    This incident has been resolved.

  2. monitoringDec 17, 2024, 15:43 UTC

    A fix has been implemented and we are monitoring the results.

  3. identifiedDec 17, 2024, 14:37 UTC

    The issue has been identified and a fix is being implemented.

  4. investigatingDec 17, 2024, 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.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in npm's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does npm have incidents?

npm reported 8 incidents in the last 90 days, 1 of them major or critical. A typical incident lasted 1h 59m. See npm's uptime and incident history

← Previous: Intermittent issues with package install (Nov 16, 2024)Next: npm is experiencing intermittent degraded installs (Jan 8, 2025) →
npm outage on Dec 17, 2024: Package Install failures due to "304 Not Modified" responses in Mumbai, India region · APIStatus.watch