npm: Increased error rates due to a CDN provider outage
Timeline of updates
- resolved
Starting at around 13:50 UTC our monitoring started reporting increased error rates, which we shortly after identified as related to an outage of our CDN provider. The situation was resolved by that provider at around 14:03 UTC. We are continuing to pay close attention to our metrics.
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 2017-06-28 14:41 UTC, resolved after 0 min, 1 update(s).
- Title
- Increased error rates due to a CDN provider outage
- Vendor
- npm
- Date
- URL
- https://rewindex.com/company/npm/incidents/kppc56fcgbdv
npm profileRecent npm incidentsAll outages on June 28, 2017npm in June 2017MarkdownJSON