npm: Timeouts on some package tarballs
Timeline of updates
- resolved
For 2 hours 8am - 10am Pacific time a small percentage of requests, approximately 2%, for package tarballs were timing out (HTTP 503). This issue has now been corrected, but we are conducting a more detailed investigation into the root cause.
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 2015-03-21 17:31 UTC, resolved after 0 min, 1 update(s).
- Title
- Timeouts on some package tarballs
- Vendor
- npm
- Date
- URL
- https://rewindex.com/company/npm/incidents/r1419p6j73x4
npm profileRecent npm incidentsAll outages on March 21, 2015npm in March 2015MarkdownJSON