# npm: Increased WWW 503 rates for some users

> npm status incident “Increased WWW 503 rates for some users” on 2016-02-18: impact none (vendor’s label), 0 min, 1 update(s). Archived by Rewindex.

Canonical: https://rewindex.com/company/npm/incidents/jphmndkmdbcg
Last updated: 2016-02-18T03:13:00Z

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

## Timeline of updates

- **resolved** 2016-02-18 03:13 UTC: We started observing short influxes of increased 503 rates for some WWW users starting at around 10:30 UTC today, up to 15:00 UTC today. This was identified as a misconfiguration and has since been fixed, with additional steps being taken to prevent this class of a problem in the future. Our apologies.

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

- Canonical URL: https://rewindex.com/company/npm/incidents/jphmndkmdbcg
- Citation: npm, “Increased WWW 503 rates for some users” (2016-02-18 03:13 UTC). Archived by Rewindex: https://rewindex.com/company/npm/incidents/jphmndkmdbcg (CC BY 4.0).
- Markdown link: `[npm: Increased WWW 503 rates for some users (2016-02-18)](https://rewindex.com/company/npm/incidents/jphmndkmdbcg)`


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