npm: Increased WWW 503 rates for some users
Timeline of updates
- resolved
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 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-02-18 03:13 UTC, resolved after 0 min, 1 update(s).
- Title
- Increased WWW 503 rates for some users
- Vendor
- npm
- Date
- URL
- https://rewindex.com/company/npm/incidents/jphmndkmdbcg
npm profileRecent npm incidentsAll outages on February 18, 2016npm in February 2016MarkdownJSON