# npm: increased timeouts on registry and website

> npm status incident “increased timeouts on registry and website” on 2017-07-13: impact none (vendor’s label), 0 min, 1 update(s). Archived by Rewindex.

Canonical: https://rewindex.com/company/npm/incidents/p3ld2xkmt8p2
Last updated: 2017-07-13T23:18:00Z

- Impact (vendor’s label): none
- Status: resolved
- Started: 2017-07-13 23:18 UTC · Resolved: 2017-07-13 23:18 UTC · Duration: 0 min
- Updates: 1
- [Vendor status page: https://status.npmjs.org/incidents/p3ld2xkmt8p2](https://status.npmjs.org/incidents/p3ld2xkmt8p2)
- [Company: npm](https://rewindex.com/company/npm.md)

## Timeline of updates

- **resolved** 2017-07-13 23:18 UTC: Between the 3:55 and 4:10 (PDT) an increased rate of 503s was observed on the registry and npmjs.com website. We believe we have isolated the underlying issue and corrected it. We will be looking into adding additional monitoring, to identify this specific category of failure faster.

_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-07-13 23:18 UTC, resolved after 0 min, 1 update(s).

- Canonical URL: https://rewindex.com/company/npm/incidents/p3ld2xkmt8p2
- Citation: npm, “increased timeouts on registry and website” (2017-07-13 23:18 UTC). Archived by Rewindex: https://rewindex.com/company/npm/incidents/p3ld2xkmt8p2 (CC BY 4.0).
- Markdown link: `[npm: increased timeouts on registry and website (2017-07-13)](https://rewindex.com/company/npm/incidents/p3ld2xkmt8p2)`


---
Canonical: https://rewindex.com/company/npm/incidents/p3ld2xkmt8p2 · Markdown: https://rewindex.com/company/npm/incidents/p3ld2xkmt8p2.md · JSON: https://rewindex.com/api/v1/companies/npm/incidents/p3ld2xkmt8p2 · Data licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) · Generated 2026-11-05T17:24:13.194Z