# npm: Elevated 503s on registry

> npm status incident “Elevated 503s on registry” on 2015-06-16: impact none (vendor’s label), 0 min, 1 update(s). Archived by Rewindex.

Canonical: https://rewindex.com/company/npm/incidents/w5gfqx98m4qm
Last updated: 2015-06-16T17:57:00Z

- Impact (vendor’s label): none
- Status: resolved
- Started: 2015-06-16 17:57 UTC · Resolved: 2015-06-16 17:57 UTC · Duration: 0 min
- Updates: 1
- [Vendor status page: https://status.npmjs.org/incidents/w5gfqx98m4qm](https://status.npmjs.org/incidents/w5gfqx98m4qm)
- [Company: npm](https://rewindex.com/company/npm.md)

## Timeline of updates

- **resolved** 2015-06-16 17:57 UTC: New code rolled out to the registry failed under load and was rolled back back; there were 5 minutes of highly elevated 503s worldwide from 10.36am to 10.41am Pacific Time. We are making changes to our rollout process to more slowly roll out new code to prevent a recurrence of this kind of error.

_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 2015-06-16 17:57 UTC, resolved after 0 min, 1 update(s).

- Canonical URL: https://rewindex.com/company/npm/incidents/w5gfqx98m4qm
- Citation: npm, “Elevated 503s on registry” (2015-06-16 17:57 UTC). Archived by Rewindex: https://rewindex.com/company/npm/incidents/w5gfqx98m4qm (CC BY 4.0).
- Markdown link: `[npm: Elevated 503s on registry (2015-06-16)](https://rewindex.com/company/npm/incidents/w5gfqx98m4qm)`


---
Canonical: https://rewindex.com/company/npm/incidents/w5gfqx98m4qm · Markdown: https://rewindex.com/company/npm/incidents/w5gfqx98m4qm.md · JSON: https://rewindex.com/api/v1/companies/npm/incidents/w5gfqx98m4qm · Data licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) · Generated 2026-11-04T13:06:21.892Z