Status monitoring
In placeThe current state of the services is on a public status page.
The current state of the services is shown on the status page, linked from the security page.
Where the services run and how customers are kept apart.
6 in place
The current state of the services is on a public status page.
The current state of the services is shown on the status page, linked from the security page.
The websites, products, databases and files run on Cloudflare’s network.
The websites, the products and their databases and files run on Cloudflare’s distributed infrastructure.
Workers are placed in the San Jose region, and database primaries are in western North America.
Our Workers are placed in the San Jose region and our database primaries are in western North America. Requests reach Cloudflare’s network at the location nearest to the person making them.
Source: DPA, Section 9.1
Requests pass through Cloudflare’s network, which applies its protections against network attacks.
Requests pass through Cloudflare’s network, which applies its protections against network attacks.
Every record is tied to its customer. One customer cannot reach another customer’s data.
Every record is tied to the customer it belongs to, and the services are designed so that one customer cannot reach another customer’s data.
Agency and Consulting keep their data in their own databases and file storage, apart from the rest of the platform.
Credential keys are derived per user from a master key held in a secrets store outside our databases.
Encryption keys for stored credentials are derived for each user from a master key held in a secrets store outside our databases.
Key versions are recorded, so keys can be rotated and stored data re-encrypted under the new version. Changes to platform keys and the secrets vault are restricted to the most privileged staff roles.
Source: DPA, Annex 2