# Contentful: Cloudflare incident status update

> Contentful status incident “Cloudflare incident status update” on 2017-02-24: impact none (vendor’s label), 0 min, 1 update(s). Archived by Rewindex.

Canonical: https://rewindex.com/company/contentful/incidents/lcs2blvf73gt
Last updated: 2017-02-24T13:44:00Z

- Impact (vendor’s label): none
- Status: resolved
- Started: 2017-02-24 13:44 UTC · Resolved: 2017-02-24 13:44 UTC · Duration: 0 min
- Updates: 1
- [Vendor status page: https://www.contentfulstatus.com/incidents/lcs2blvf73gt](https://www.contentfulstatus.com/incidents/lcs2blvf73gt)
- [Company: Contentful](https://rewindex.com/company/contentful.md)

## Timeline of updates

- **resolved** 2017-02-24 13:44 UTC: This update is meant to give a security status assessment updated with all information we could collect on this incident, as of Friday the 24th of February 13:17 UTC. One of the biggest global CDN providers had a severe security issue \[1\]\[2\] which exposed private user data and credentials to the outside world. The full scope of the issue is not yet fully clear. We have reviewed the services used by Contentful according to a public list \[3\] of potentially compromised web applications. The only service in this list we are aware of using is Zendesk, whose security staff have assured us that no credentials were leaked on their side. Contentful itself is NOT using Cloudflare to provide its services, so no data was leaked from Contentful. We recommend the following: \* To rotate Contentful API Keys that transited through Cloudflare systems (i.e. if you are a customer of Cloudflare and use their product to protect a proxy to the Contentful API) \* Should you be using the same password to access Contentful that you use on other services, we recommend that you change it and use a password that is unique and used only for Contentful. We will be monitoring the situation and will update accordingly if something changes. \[1\]: https://blog.cloudflare.com/incident-report-on-memory-leak-caused-by-cloudflare-parser-bug/ \[2\]: https://techcrunch.com/2017/02/23/major-cloudflare-bug-leaked-sensitive-data-from-customers-websites/ \[3\]: https://github.com/pirate/sites-using-cloudflare

_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 Contentful, started 2017-02-24 13:44 UTC, resolved after 0 min, 1 update(s).

- Canonical URL: https://rewindex.com/company/contentful/incidents/lcs2blvf73gt
- Citation: Contentful, “Cloudflare incident status update” (2017-02-24 13:44 UTC). Archived by Rewindex: https://rewindex.com/company/contentful/incidents/lcs2blvf73gt (CC BY 4.0).
- Markdown link: `[Contentful: Cloudflare incident status update (2017-02-24)](https://rewindex.com/company/contentful/incidents/lcs2blvf73gt)`


---
Canonical: https://rewindex.com/company/contentful/incidents/lcs2blvf73gt · Markdown: https://rewindex.com/company/contentful/incidents/lcs2blvf73gt.md · JSON: https://rewindex.com/api/v1/companies/contentful/incidents/lcs2blvf73gt · Data licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) · Generated 2026-11-04T14:09:27.036Z