-
Notifications
You must be signed in to change notification settings - Fork 10k
Update DLS region lists, sort them and move them onto a single page #22910
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
angelampcosta
merged 4 commits into
cloudflare:production
from
mathew-cf:consolidate-regions-table
Jun 5, 2025
Merged
Changes from 1 commit
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
2a374e2
Update region lists, sort them and move them onto a single page
mathew-cf 7a869f5
Update src/content/docs/data-localization/region-support.mdx
mathew-cf e5c05e3
Update src/content/docs/data-localization/region-support.mdx
mathew-cf 668d8bc
Update src/content/docs/data-localization/region-support.mdx
mathew-cf File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,52 +1,83 @@ | ||
| --- | ||
| title: Region support | ||
| title: Region Support | ||
| pcx_content_type: reference | ||
| sidebar: | ||
| order: 2 | ||
| head: | ||
| - tag: title | ||
| content: Regional product support | ||
|
|
||
| content: Region Support | ||
mathew-cf marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| --- | ||
|
|
||
| Support by product and region is summarized in the following table: | ||
|
|
||
| | Region | Geo Key Manager | Regional Services | Customer Metadata Boundary | | ||
| | ---------------------------------- | --------------- | ----------------- | ----------------------------- | | ||
| | US | ✅ | ✅ | ✅ | | ||
| | EU | ✅ | ✅ | ✅ | | ||
| | UK | ✅ | ✅ | Can use EU metadata boundary. | | ||
| | Canada | ✅ | ✅ | ✘ | | ||
| | Australia | ✅ | ✅ | ✘ | | ||
| | Japan | ✅ | ✅ | ✘ | | ||
| | India | ✅ | ✅ | ✘ | | ||
| | ISO 27001 Certified European Union | ✅ | ✅ | Can use EU metadata boundary. | | ||
| | Germany | ✅ | ✅ | Can use EU metadata boundary. | | ||
| | Singapore | ✅ | ✅ | ✘ | | ||
| | South Korea | ✅ | ✅ | ✘ | | ||
| | Austria | ✘ | ✅ | Can use EU metadata boundary. | | ||
| | Brazil | ✘ | ✅ | ✘ | | ||
| | Cloudflare Green Energy | ✘ | ✅ | ✘ | | ||
| | Exclusive of Hong Kong and Macau | ✘ | ✅ | ✘ | | ||
| | Exclusive of Russia and Belarus | ✘ | ✅ | ✘ | | ||
| | France | ✘ | ✅ | Can use EU metadata boundary. | | ||
| | Hong Kong | ✘ | ✅ | ✘ | | ||
| | Italy | ✘ | ✅ | Can use EU metadata boundary. | | ||
| | NATO | ✘ | ✅ | ✘ | | ||
| | Netherlands | ✘ | ✅ | Can use EU metadata boundary. | | ||
| | Russia | ✘ | ✅ | ✘ | | ||
| | Saudi Arabia | ✘ | ✅ | ✘ | | ||
| | South Africa | ✘ | ✅ | ✘ | | ||
| | Spain | ✘ | ✅ | Can use EU metadata boundary. | | ||
| | Switzerland | ✘ | ✅ | ✘ | | ||
| | Taiwan | ✘ | ✅ | ✘ | | ||
| | US State of California | ✘ | ✅ | ✘ | | ||
| | US State of Florida | ✘ | ✅ | ✘ | | ||
| | US State of Texas | ✘ | ✅ | ✘ | | ||
| | FedRAMP Moderate Compliant (Domestic) [^1] | ✅ | ✅ | ✅ | | ||
| | FedRAMP Moderate Compliant (International) [^2] | ✘ | ✅ | ✅ | | ||
| | Region | Geo Key Manager | Regional Services | Customer Metadata Boundary | | ||
| | ------------------------------------------ | --------------- | ----------------- | ----------------------------- | | ||
| | Australia | ✅ | ✅ | ✘ | | ||
| | Austria | ✘ | ✅ | Can use EU metadata boundary. | | ||
| | Brazil | ✘ | ✅ | ✘ | | ||
| | Canada | ✅ | ✅ | ✘ | | ||
| | Cloudflare Green Energy | ✘ | ✅ | ✘ | | ||
| | European Union | ✅ | ✅ | ✅ | | ||
| | Exclusive of Hong Kong and Macau | ✘ | ✅ | ✘ | | ||
| | Exclusive of Russia and Belarus | ✘ | ✅ | ✘ | | ||
| | FedRAMP Moderate Compliant (Domestic) | ✅ | ✅ | ✅ | | ||
| | FedRAMP Moderate Compliant (International) | ✘ | ✅ | ✅ | | ||
| | France | ✘ | ✅ | Can use EU metadata boundary. | | ||
| | Germany | ✅ | ✅ | Can use EU metadata boundary. | | ||
| | Hong Kong | ✘ | ✅ | ✘ | | ||
| | India | ✅ | ✅ | ✘ | | ||
| | ISO 27001 Certified European Union | ✅ | ✅ | Can use EU metadata boundary. | | ||
| | Italy | ✘ | ✅ | Can use EU metadata boundary. | | ||
| | Japan | ✅ | ✅ | ✘ | | ||
| | NATO | ✘ | ✅ | ✘ | | ||
| | Netherlands | ✘ | ✅ | Can use EU metadata boundary. | | ||
| | Russia | ✘ | ✅ | ✘ | | ||
| | Saudi Arabia | ✘ | ✅ | ✘ | | ||
| | Singapore | ✅ | ✅ | ✘ | | ||
| | South Africa | ✘ | ✅ | ✘ | | ||
| | South Korea | ✅ | ✅ | ✘ | | ||
| | Spain | ✘ | ✅ | Can use EU metadata boundary. | | ||
| | Switzerland | ✘ | ✅ | ✘ | | ||
| | Taiwan | ✘ | ✅ | ✘ | | ||
| | United Kingdom | ✅ | ✅ | Can use EU metadata boundary. | | ||
| | United States of America | ✅ | ✅ | ✅ | | ||
| | US State of California | ✘ | ✅ | ✘ | | ||
| | US State of Florida | ✘ | ✅ | ✘ | | ||
| | US State of Texas | ✘ | ✅ | ✘ | | ||
|
|
||
mathew-cf marked this conversation as resolved.
Show resolved
Hide resolved
|
||
| | Region | Definition | | ||
| | ------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | ||
| | Australia | Cloudflare will only use data centers that are physically located within Australia to decrypt and service HTTPS traffic. | | ||
| | Austria | Cloudflare will only use data centers that are physically located within Austria to decrypt and service HTTPS traffic. | | ||
| | Brazil | Cloudflare will only use data centers that are physically located within Brazil to decrypt and service HTTPS traffic. | | ||
| | Canada | Cloudflare will only use data centers that are physically located within Canada to decrypt and service HTTPS traffic. | | ||
| | Cloudflare Green Energy | Cloudflare will only use data centers that are committed to powering their operations with renewable energy. | | ||
| | European Union | Cloudflare will only use data centers that are physically located within the European Union. For more details, refer to the [list of European Union countries](https://european-union.europa.eu/principles-countries-history/country-profiles_en). | | ||
| | Exclusive of Hong Kong and Macau | Cloudflare will only use data centers that are NOT physically located within Hong Kong and Macau to decrypt and service HTTPS traffic. | | ||
| | Exclusive of Russia and Belarus | Cloudflare will only use data centers that are NOT physically located within Russia and Belarus to decrypt and service HTTPS traffic. | | ||
| | FedRAMP Moderate Compliant (Domestic) | Cloudflare will only use data centers that are FedRAMP Moderate certified and located within the United States. | | ||
| | FedRAMP Moderate Compliant (International) | Cloudflare will only use data centers that are FedRAMP Moderate certified, including certified locations outside the United States. | | ||
| | France | Cloudflare will only use data centers that are physically located within Metropolitan France (the European territory of France) to decrypt and service HTTPS traffic. | | ||
| | Germany | Cloudflare will only use data centers that are physically located within Germany to decrypt and service HTTPS traffic. | | ||
| | Hong Kong | Cloudflare will only use data centers that are physically located within Hong Kong to decrypt and service HTTPS traffic. | | ||
| | India | Cloudflare will only use data centers that are physically located within India to decrypt and service HTTPS traffic. | | ||
| | ISO 27001 Certified European Union | Cloudflare will only use data centers that are physically located within the [European Union](https://european-union.europa.eu/principles-countries-history/country-profiles_en) and that adhere to the ISO 27001 certification. | | ||
| | Italy | Cloudflare will only use data centers that are physically located within Italy to decrypt and service HTTPS traffic. | | ||
| | Japan | Cloudflare will only use data centers that are physically located within Japan to decrypt and service HTTPS traffic. | | ||
| | NATO | Cloudflare will only use data centers that are physically located within North Atlantic Treaty Organization (NATO) countries. For more details, refer to the [list of NATO countries](https://www.nato.int/nato-welcome/). | | ||
| | Netherlands | Cloudflare will only use data centers that are physically located within the Netherlands to decrypt and service HTTPS traffic. | | ||
| | Russia | Cloudflare will only use data centers that are physically located within Russia to decrypt and service HTTPS traffic. | | ||
| | Saudi Arabia | Cloudflare will only use data centers that are physically located within Saudi Arabia to decrypt and service HTTPS traffic. | | ||
| | Singapore | Cloudflare will only use data centers that are physically located within Singapore to decrypt and service HTTPS traffic. | | ||
| | South Africa | Cloudflare will only use data centers that are physically located within South Africa to decrypt and service HTTPS traffic. | | ||
| | South Korea | Cloudflare will only use data centers that are physically located within South Korea to decrypt and service HTTPS traffic. | | ||
| | Spain | Cloudflare will only use data centers that are physically located within Spain to decrypt and service HTTPS traffic. | | ||
| | Switzerland | Cloudflare will only use data centers that are physically located within Switzerland to decrypt and service HTTPS traffic. | | ||
| | Taiwan | Cloudflare will only use data centers that are physically located within Taiwan to decrypt and service HTTPS traffic. | | ||
| | United Kingdom | Cloudflare will only use data centers that are physically located within the United Kingdom to decrypt and service HTTPS traffic. | | ||
| | United States of America | Cloudflare will only use data centers that are physically located within the United States of America to decrypt and service HTTPS traffic. | | ||
| | US State of California | Cloudflare will only use data centers that are physically located within the US State of California to decrypt and service HTTPS traffic. | | ||
| | US State of Florida | Cloudflare will only use data centers that are physically located within the US State of Florida to decrypt and service HTTPS traffic. | | ||
| | US State of Texas | Cloudflare will only use data centers that are physically located within the US State of Texas to decrypt and service HTTPS traffic. | | ||
|
|
||
| Only supported in [Geo Key Manager v2](/ssl/edge-certificates/geokey-manager/). | ||
| [^1]: FedRAMP Moderate Compliant (Domestic) was previously named FedRAMP Compliant. It consists of our FedRAMP Moderate compliant data centers in the US. | ||
angelampcosta marked this conversation as resolved.
Show resolved
Hide resolved
|
||
| [^2]: FedRAMP Moderate Compliant (International) consists of all our FedRAMP Moderate compliant data centers globally. | ||
| Only supported in [Geo Key Manager v2](/ssl/edge-certificates/geokey-manager/). | ||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.