npm: Increased registry 503 rates
Timeline of updates
- resolved
We've now resolved this issue for all the packages. We will be publishing a post-mortem regarding this issue. Our apologies!
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: minor) posted by npm, started 2016-03-02 02:15 UTC, resolved after 2.3 h, 1 update(s).
- Title
- Increased registry 503 rates
- Vendor
- npm
- Date
- URL
- https://rewindex.com/company/npm/incidents/9zwnxr4n3bpl
npm profileRecent npm incidentsAll outages on March 2, 2016npm in March 2016MarkdownJSON