Limitations
There are some caveats and limitations when deploying Data Localization Suite features.
Cloudflare is working hard to improve this offering and fill the gaps. If you have a specific feature request, please contact your Account Team.
Key Management
When using Geo Key Manager or Keyless SSL, some caveats may apply.
The remote procedure call from the server to the key server can add latency to the handshake, slowing down connection establishment. The additional latency cost corresponds to the round-trip time from the server to the key server, which can be as much as a second if the key server is on the other side of the world. Luckily, this latency cost only applies to the first time you connect to a server. Once the handshake is complete, the key server is not involved. Furthermore, if you reconnect to a site you do not have to pay the latency cost either because resuming a connection with TLS Session Resumption does not require the private key. Hence, latency is only added for the initial connection.
Learn more about how it works in our blog post.
Regional Services
When using Regional Services, some caveats and limitations may apply.
For product-specific caveats, refer to Cloudflare product compatibility page.
The following features and protocols are not supported by Regional Services and might not work on regionalized hostnames:
Since Regional Services leverages Spectrum in the background, Spectrum limitations apply.
Regional Services does not apply to Subrequests.
Customer Metadata Boundary
There are certain limitations and caveats when using Customer Metadata Boundary.
Specifically most of the Zone Analytics & Logs UI Tabs will be showing up as empty, when configuring Customer Metadata Boundary to EU only. It is recommended to use the UI Security Analytics instead, or the HTTP request logs via Logpush.
For product-specific caveats, refer to Cloudflare product compatibility page.
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.
Dashboard UI Analytics
In some cases, when using Customer Metadata Boundary set to the EU, some Dashboard UI Analytics might show up empty.