# npm: Investigating 503 rate on registry

> npm status incident “Investigating 503 rate on registry” on 2016-02-22: impact none (vendor’s label), 47 min, 1 update(s). Archived by Rewindex.

Canonical: https://rewindex.com/company/npm/incidents/5d9sdsdhbrss
Last updated: 2016-02-22T22:16:00Z

- Impact (vendor’s label): none
- Status: resolved
- Started: 2016-02-22 21:29 UTC · Resolved: 2016-02-22 22:16 UTC · Duration: 47 min
- Updates: 1
- [Vendor status page: https://status.npmjs.org/incidents/5d9sdsdhbrss](https://status.npmjs.org/incidents/5d9sdsdhbrss)
- [Company: npm](https://rewindex.com/company/npm.md)

## Timeline of updates

- **resolved** 2016-02-22 22:16 UTC: The issues with the POP appear to be resolved.

_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 2016-02-22 21:29 UTC, resolved after 47 min, 1 update(s).

- Canonical URL: https://rewindex.com/company/npm/incidents/5d9sdsdhbrss
- Citation: npm, “Investigating 503 rate on registry” (2016-02-22 21:29 UTC). Archived by Rewindex: https://rewindex.com/company/npm/incidents/5d9sdsdhbrss (CC BY 4.0).
- Markdown link: `[npm: Investigating 503 rate on registry (2016-02-22)](https://rewindex.com/company/npm/incidents/5d9sdsdhbrss)`


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