npm: increased origin latency resulting in burst of 503s
Timeline of updates
- resolved
briefly, between (2:54 - 2:58PM PDT) we saw a increase in origin latency, resulting in increased 503s from the registry; the problem has been resolved and we are investigating the underlying 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 2017-01-13 23:03 UTC, resolved after 0 min, 1 update(s).
- Title
- increased origin latency resulting in burst of 503s
- Vendor
- npm
- Date
- URL
- https://rewindex.com/company/npm/incidents/433rbgt7p9bn
npm profileRecent npm incidentsAll outages on January 13, 2017npm in January 2017MarkdownJSON