# npm: increased origin latency resulting in burst of 503s

> npm status incident “increased origin latency resulting in burst of 503s” on 2017-01-13: impact none (vendor’s label), 0 min, 1 update(s). Archived by Rewindex.

Canonical: https://rewindex.com/company/npm/incidents/433rbgt7p9bn
Last updated: 2017-01-13T23:03:00Z

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

## Timeline of updates

- **resolved** 2017-01-13 23:03 UTC: briefly, between (2:54 - 2:58PM PDT) we saw a increase in origin latency, resulting in increased 503s from the registry; the problem has been resolved and we are investigating the underlying cause.

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

- Canonical URL: https://rewindex.com/company/npm/incidents/433rbgt7p9bn
- Citation: npm, “increased origin latency resulting in burst of 503s” (2017-01-13 23:03 UTC). Archived by Rewindex: https://rewindex.com/company/npm/incidents/433rbgt7p9bn (CC BY 4.0).
- Markdown link: `[npm: increased origin latency resulting in burst of 503s (2017-01-13)](https://rewindex.com/company/npm/incidents/433rbgt7p9bn)`


---
Canonical: https://rewindex.com/company/npm/incidents/433rbgt7p9bn · Markdown: https://rewindex.com/company/npm/incidents/433rbgt7p9bn.md · JSON: https://rewindex.com/api/v1/companies/npm/incidents/433rbgt7p9bn · Data licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) · Generated 2026-11-04T15:34:50.097Z