# npm: Increased 502 and 503 rates for the website

> npm status incident “Increased 502 and 503 rates for the website” on 2016-08-19: impact none (vendor’s label), 0 min, 1 update(s). Archived by Rewindex.

Canonical: https://rewindex.com/company/npm/incidents/gylcj2g9k99p
Last updated: 2016-08-19T10:20:00Z

- Impact (vendor’s label): none
- Status: resolved
- Started: 2016-08-19 10:20 UTC · Resolved: 2016-08-19 10:20 UTC · Duration: 0 min
- Updates: 1
- [Vendor status page: https://status.npmjs.org/incidents/gylcj2g9k99p](https://status.npmjs.org/incidents/gylcj2g9k99p)
- [Company: npm](https://rewindex.com/company/npm.md)

## Timeline of updates

- **resolved** 2016-08-19 10:20 UTC: At 7:55 UTC our monitoring alerted us to increased 502 and 503 rates for the website. We've determined the culprit to be a stuck Node.js process and restarted it at 8:12 UTC, which fixed the issue immediately. We will continue investigating the root cause of this problem.

_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-08-19 10:20 UTC, resolved after 0 min, 1 update(s).

- Canonical URL: https://rewindex.com/company/npm/incidents/gylcj2g9k99p
- Citation: npm, “Increased 502 and 503 rates for the website” (2016-08-19 10:20 UTC). Archived by Rewindex: https://rewindex.com/company/npm/incidents/gylcj2g9k99p (CC BY 4.0).
- Markdown link: `[npm: Increased 502 and 503 rates for the website (2016-08-19)](https://rewindex.com/company/npm/incidents/gylcj2g9k99p)`


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