npm: Increased 502 and 503 rates for the website
Timeline of updates
- resolved
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 npm’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.npmjs.org (opens in new tab).
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).
- Title
- Increased 502 and 503 rates for the website
- Vendor
- npm
- Date
- URL
- https://rewindex.com/company/npm/incidents/gylcj2g9k99p
npm profileRecent npm incidentsAll outages on August 19, 2016npm in August 2016MarkdownJSON