npm: Slew of 503s on npmjs.com
Timeline of updates
- resolved
The npmjs.com website was down for up to 15 minutes today, between 10:30 AM PT and 10:45 AM PT. This was due to a web spider, which slammed the website with a 500% spike in requests in the span of that time. We have identified the bot and banned its user agent.
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 2016-07-20 18:10 UTC, resolved after 0 min, 1 update(s).
- Title
- Slew of 503s on npmjs.com
- Vendor
- npm
- Date
- URL
- https://rewindex.com/company/npm/incidents/cblzh1fs08sd
npm profileRecent npm incidentsAll outages on July 20, 2016npm in July 2016MarkdownJSON