rewindex

CompaniesnpmIncidents

npm: Reported 502s serving tarballs to some regions

No impact listedStatus: resolvedStarted Resolved (3.4 h)1 updatestatus.npmjs.org (opens in new tab)

Timeline of updates

  1. resolved

    Issues with tarball serving should be resolved now. A writeup of the outage will be made available on the npmjs.org blog.

From npm’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.

How the archive is checked, and what it cannot prove.

This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.

Impact, status and times are the vendor’s own, as last archived. View on status.npmjs.org (opens in new tab).

Cite this

Status incident (vendor impact label: none) posted by npm, started 2016-07-06 13:38 UTC, resolved after 3.4 h, 1 update(s).

Title
Reported 502s serving tarballs to some regions
Vendor
npm
Date
URL
https://rewindex.com/company/npm/incidents/nl2mpgltpnvj

npm profileRecent npm incidentsAll outages on July 6, 2016npm in July 2016MarkdownJSON