# npm: 500s on package servers and npmjs.com

> npm status incident “500s on package servers and npmjs.com” on 2017-09-06: impact none (vendor’s label), 2.0 h, 1 update(s). Archived by Rewindex.

Canonical: https://rewindex.com/company/npm/incidents/25brbmchw606
Last updated: 2017-09-06T23:38:00Z

- Impact (vendor’s label): none
- Status: resolved
- Started: 2017-09-06 21:36 UTC · Resolved: 2017-09-06 23:38 UTC · Duration: 2.0 h
- Updates: 1
- [Vendor status page: https://status.npmjs.org/incidents/25brbmchw606](https://status.npmjs.org/incidents/25brbmchw606)
- [Company: npm](https://rewindex.com/company/npm.md)

## Timeline of updates

- **resolved** 2017-09-06 23:38 UTC: 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 the vendor’s published history: only the final update text is available for incidents before Rewindex began polling this page._

## 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).

- Canonical URL: https://rewindex.com/company/npm/incidents/25brbmchw606
- Citation: npm, “500s on package servers and npmjs.com” (2017-09-06 21:36 UTC). Archived by Rewindex: https://rewindex.com/company/npm/incidents/25brbmchw606 (CC BY 4.0).
- Markdown link: `[npm: 500s on package servers and npmjs.com (2017-09-06)](https://rewindex.com/company/npm/incidents/25brbmchw606)`


---
Canonical: https://rewindex.com/company/npm/incidents/25brbmchw606 · Markdown: https://rewindex.com/company/npm/incidents/25brbmchw606.md · JSON: https://rewindex.com/api/v1/companies/npm/incidents/25brbmchw606 · Data licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) · Generated 2026-11-04T18:00:32.472Z