npm: 503s on www
Timeline of updates
- resolved
Our primary cache server for the website failed. The site is supposed to fail over to the spare cache server automatically, but due to a bug this didn't happen. Instead, we manually failed over to the spare server. The website was totally unavailable for 15 minutes from 15:47 to 16:02 Pacific Time. 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 2015-10-21 23:13 UTC, resolved after 0 min, 1 update(s).
- Title
- 503s on www
- Vendor
- npm
- Date
- URL
- https://rewindex.com/company/npm/incidents/7pl97c4wj506
npm profileRecent npm incidentsAll outages on October 21, 2015npm in October 2015MarkdownJSON