You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/content/docs/data-localization/faq.mdx
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -38,4 +38,8 @@ Yes, you have these options available:
38
38
39
39
These options only offer L3/L4 DDoS protection and using them imply that no application / L7 security or performance services can be applied.
40
40
41
+
## I have configured [Customer Metadata Boundary](/data-localization/metadata-boundary/) for EU region, I'm accessing the Cloudflare Dashboard from Europe, why am I getting an error `Data not available due to your account's Customer Metadata Boundary configuration`?
42
+
43
+
The Cloudflare API (even through the dashboard) uses dynamic steering based on health check probes. This can lead to users being steered temporarily to another core data center (AMS or PDX) for some period of time. [Out of region access](/data-localization/metadata-boundary/out-of-region-access/) allows requests arriving at PDX to pull analytics from AMS and vice-versa. The analytics are still exclusively stored in the CMB configured region.
0 commit comments