npm: Increased 503 rates for public packages
Timeline of updates
- resolved
We've identified the issue as a case of a service's process getting stuck and resolved it by rolling the affected service.
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-06-09 14:25 UTC, resolved after 5 min, 1 update(s).
- Title
- Increased 503 rates for public packages
- Vendor
- npm
- Date
- URL
- https://rewindex.com/company/npm/incidents/7g3q33m6ncpn
npm profileRecent npm incidentsAll outages on June 9, 2017npm in June 2017MarkdownJSON