← Live dashboard

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

ResolvedmajorOfficial source confirmedSingle region affectedFirst recorded update Dec 17, 2024, 12:50 PM · Resolved Dec 17, 2024, 04:19 PM

This incident has been resolved.

npm live status →

What visitors reported during this incident

No visitor reports were filed for this incident.

Having problems with npm now? Check the current status

Affected services

Package installation

Updates (4)

  1. Dec 17, 2024, 04:19 PM
    Package Install failures due to "304 Not Modified" responses in Mumbai, India region

    This incident has been resolved.

    npm ↗
  2. Dec 17, 2024, 03:43 PM
    Package Install failures due to "304 Not Modified" responses in Mumbai, India region

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

    npm ↗
  3. Dec 17, 2024, 02:37 PM
    Package Install failures due to "304 Not Modified" responses in Mumbai, India region

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

    npm ↗
  4. Dec 17, 2024, 12:50 PM
    Package Install failures due to "304 Not Modified" responses in Mumbai, India region

    We are currently investigating failures to install packages due to TAR_BAD_ARCHIVE or 304 Not Modified responses for clients in Mumbai, India.

    npm ↗

What to do next

  • Verify your own services recovered cleanly. Some upstream outages leave queues or caches in a degraded state, run smoke tests before declaring green internally.
  • Save the post-mortem. Vendors usually publish a detailed RCA 1-3 days later. We'll add it to this page when it appears.
  • Watch the provider going forward. Follow npm's status feed →

GlobalOutageMap aggregates publicly reported signals. We never claim authoritative status, always cross-check the provider's official channel before making business decisions.