Cloudflare Docs
Data Localization Suite
Cloudflare Docs
Data Localization Suite
GitHub icon
Edit this page on GitHub
Set theme to dark (⇧+D)
  1. Products
  2. Data Localization Suite
  3. Customer Metadata Boundary

Customer Metadata Boundary

As part of the Data Localization Suite, the Customer Metadata Boundary (CMB) ensures that any traffic metadata that can identify a customer’s end user (that is, contains the customer’s Account ID) will stay in the EU (European Union) or in the US (United States), depending on the region the customer selects. For example, if a customer selects the EU Customer Metadata Boundary, metadata will only be sent to our core data center located in the European Union.

​​ Customer traffic metadata flow

The following diagram is a high-level example of the flow of how metadata about a customer’s traffic is generated on a Cloudflare data center. Logs are exclusively sent to the EU core data center for Cloudflare customers and their authorized users to access and view.



​​ Log management

Additionally, customers have the option to configure Logpush to push their Customer Logs to various storage services, SIEMs, and log management providers.

​​ Data unavailability

If you encounter a message on the dashboard indicating that your data is unavailable due to your account’s Metadata Boundary configuration, this is because you are trying to access data that is not stored in your region (that is, you are in the US and trying to access data that is only stored in the EU, or vice versa). If you receive this error message while being in the region where your data is stored, there are two potential reasons why you might get this message:

  • Your account has Customer Metadata Boundary (CMB) enabled, and your request is being directed to an incorrect region. For example, if you are in the EU and CMB is configured to store your data in the US.

  • If you are trying to access your data from the correct region, such as being in the EU with CMB configured to save your data in the EU, the issue may be caused by network congestion. Typically, this problem resolves within a few minutes.

​​ Product specific-behavior

For detailed information about product-specific behavior regarding Metadata Boundary, refer to the Overview section.