npm: www downtime
Timeline of updates
- resolved
The website was sporadically available over the course of about 50 minutes this morning as a result of a major network problem in Amazon's AWS us-west-2 region. Unlike the registry itself, the website is not completely redundant across AWS east and west regions. We have long-term plans in place to improve this design and we are continuing to work towards them.
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-03-20 15:09 UTC, resolved after 0 min, 1 update(s).
- Title
- www downtime
- Vendor
- npm
- Date
- URL
- https://rewindex.com/company/npm/incidents/w8yd5lf627qt
npm profileRecent npm incidentsAll outages on March 20, 2015npm in March 2015MarkdownJSON