npm: Difficulties with our CDN
Timeline of updates
- resolved
Registry 503 responses were elevated because of errors with one of the points of presence of our CDN provider. They identified & fixed the incident. (You can read more details in their incident report here: https://status.fastly.com/incidents/gjgcmfljjdpk (opens in new tab) .) Registry responses should be back to normal.
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 2016-02-18 20:22 UTC, resolved after 53 min, 1 update(s).
- Title
- Difficulties with our CDN
- Vendor
- npm
- Date
- URL
- https://rewindex.com/company/npm/incidents/llbnlcknnlkf
npm profileRecent npm incidentsAll outages on February 18, 2016npm in February 2016MarkdownJSON