npm: Elevated 503s on registry
Timeline of updates
- resolved
New code rolled out to the registry failed under load and was rolled back back; there were 5 minutes of highly elevated 503s worldwide from 10.36am to 10.41am Pacific Time. We are making changes to our rollout process to more slowly roll out new code to prevent a recurrence of this kind of error.
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-06-16 17:57 UTC, resolved after 0 min, 1 update(s).
- Title
- Elevated 503s on registry
- Vendor
- npm
- Date
- URL
- https://rewindex.com/company/npm/incidents/w5gfqx98m4qm
npm profileRecent npm incidentsAll outages on June 16, 2015npm in June 2015MarkdownJSON