npm: increased rate of 503s.
Timeline of updates
- resolved
An increased request rate caused by bot behavior caused slower than usual response times and increased error rates. Lasted from 15:00 - 15:45
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-03-15 16:27 UTC, resolved after 0 min, 1 update(s).
- Title
- increased rate of 503s.
- Vendor
- npm
- Date
- URL
- https://rewindex.com/company/npm/incidents/5mbr4c40fx0t
npm profileRecent npm incidentsAll outages on March 15, 2017npm in March 2017MarkdownJSON