npm: Packages failed to display on website
Timeline of updates
- resolved
A bad rollout caused package pages on production to fail to render for a few minutes. The change has been rolled back. No data was corrupted and no information was lost. Some package pages are currently still failing to display but will correct themselves once data falls out of cache in 5 minutes.
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 2015-05-22 23:39 UTC, resolved after 0 min, 1 update(s).
- Title
- Packages failed to display on website
- Vendor
- npm
- Date
- URL
- https://rewindex.com/company/npm/incidents/d2r3tqh21t94
npm profileRecent npm incidentsAll outages on May 22, 2015npm in May 2015MarkdownJSON