# npm: Difficulties with our CDN

> npm status incident “Difficulties with our CDN” on 2016-02-18: impact none (vendor’s label), 53 min, 1 update(s). Archived by Rewindex.

Canonical: https://rewindex.com/company/npm/incidents/llbnlcknnlkf
Last updated: 2016-02-18T21:15:00Z

- Impact (vendor’s label): none
- Status: resolved
- Started: 2016-02-18 20:22 UTC · Resolved: 2016-02-18 21:15 UTC · Duration: 53 min
- Updates: 1
- [Vendor status page: https://status.npmjs.org/incidents/llbnlcknnlkf](https://status.npmjs.org/incidents/llbnlcknnlkf)
- [Company: npm](https://rewindex.com/company/npm.md)

## Timeline of updates

- **resolved** 2016-02-18 21:15 UTC: 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 .) Registry responses should be back to normal.

_From the vendor’s published history: only the final update text is available for incidents before Rewindex began polling this page._

## 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).

- Canonical URL: https://rewindex.com/company/npm/incidents/llbnlcknnlkf
- Citation: npm, “Difficulties with our CDN” (2016-02-18 20:22 UTC). Archived by Rewindex: https://rewindex.com/company/npm/incidents/llbnlcknnlkf (CC BY 4.0).
- Markdown link: `[npm: Difficulties with our CDN (2016-02-18)](https://rewindex.com/company/npm/incidents/llbnlcknnlkf)`


---
Canonical: https://rewindex.com/company/npm/incidents/llbnlcknnlkf · Markdown: https://rewindex.com/company/npm/incidents/llbnlcknnlkf.md · JSON: https://rewindex.com/api/v1/companies/npm/incidents/llbnlcknnlkf · Data licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) · Generated 2026-11-04T21:52:37.814Z