npm: Increased 503s for the npmjs.com website
Timeline of updates
- resolved
A blip on a package metadata box left zombie connections on a DB box, consuming needed connections & causing 503s on the website. The old connections have been flushed and the service appears to have recovered.
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: major) posted by npm, started 2016-10-10 04:31 UTC, resolved after 1.2 h, 1 update(s).
- Title
- Increased 503s for the npmjs.com website
- Vendor
- npm
- Date
- URL
- https://rewindex.com/company/npm/incidents/qnhlwlbxkr7l
npm profileRecent npm incidentsAll outages on October 10, 2016npm in October 2016MarkdownJSON