npm: 500s on package servers and npmjs.com
Timeline of updates
- resolved
We've resolved an issue regarding 500s on package servers and npmjs.com. Package installs and npmjs.com page views should have returned to normal. We identified the culprit as a bot making an unusually high rate of requests on a route that was not cached. We've blocked the offending IP and intend to implement additional measures to prevent this from occurring again in the future.
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-09-06 21:36 UTC, resolved after 2.0 h, 1 update(s).
- Title
- 500s on package servers and npmjs.com
- Vendor
- npm
- Date
- URL
- https://rewindex.com/company/npm/incidents/25brbmchw606
npm profileRecent npm incidentsAll outages on September 6, 2017npm in September 2017MarkdownJSON