npm: Registry outage
Timeline of updates
- resolved
A misconfiguration caused a production push to the registry to fail, leading to 120 seconds of registry unavailability from 13:34 - 13:36 Pacific Time before the change was rolled back. We have modified our push process to catch this form of error in future.
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-19 21:19 UTC, resolved after 0 min, 1 update(s).
- Title
- Registry outage
- Vendor
- npm
- Date
- URL
- https://rewindex.com/company/npm/incidents/ktx6f2nmjt8c
npm profileRecent npm incidentsAll outages on March 19, 2015npm in March 2015MarkdownJSON