Skip to content

Commit d684c0f

Browse files
mathew-cfmathew-cf
committed
Update region lists, sort them and move them onto a single page
1 parent a470a25 commit d684c0f

File tree

2 files changed

+123
-141
lines changed

2 files changed

+123
-141
lines changed

‎src/content/docs/data-localization/region-support.mdx‎

Lines changed: 70 additions & 39 deletions
Original file line numberDiff line numberDiff line change
@@ -1,52 +1,83 @@
11
---
2-
title: Region support
2+
title: Region Support
33
pcx_content_type: reference
44
sidebar:
55
order: 2
66
head:
77
- tag: title
8-
content: Regional product support
9-
8+
content: Region Support
109
---
1110

1211
Support by product and region is summarized in the following table:
1312

14-
| Region | Geo Key Manager | Regional Services | Customer Metadata Boundary |
15-
| ---------------------------------- | --------------- | ----------------- | ----------------------------- |
16-
| US | ✅ | ✅ | ✅ |
17-
| EU | ✅ | ✅ | ✅ |
18-
| UK | ✅ | ✅ | Can use EU metadata boundary. |
19-
| Canada | ✅ | ✅ | ✘ |
20-
| Australia | ✅ | ✅ | ✘ |
21-
| Japan | ✅ | ✅ | ✘ |
22-
| India | ✅ | ✅ | ✘ |
23-
| ISO 27001 Certified European Union | ✅ | ✅ | Can use EU metadata boundary. |
24-
| Germany | ✅ | ✅ | Can use EU metadata boundary. |
25-
| Singapore | ✅ | ✅ | ✘ |
26-
| South Korea | ✅ | ✅ | ✘ |
27-
| Austria | ✘ | ✅ | Can use EU metadata boundary. |
28-
| Brazil | ✘ | ✅ | ✘ |
29-
| Cloudflare Green Energy | ✘ | ✅ | ✘ |
30-
| Exclusive of Hong Kong and Macau | ✘ | ✅ | ✘ |
31-
| Exclusive of Russia and Belarus | ✘ | ✅ | ✘ |
32-
| France | ✘ | ✅ | Can use EU metadata boundary. |
33-
| Hong Kong | ✘ | ✅ | ✘ |
34-
| Italy | ✘ | ✅ | Can use EU metadata boundary. |
35-
| NATO | ✘ | ✅ | ✘ |
36-
| Netherlands | ✘ | ✅ | Can use EU metadata boundary. |
37-
| Russia | ✘ | ✅ | ✘ |
38-
| Saudi Arabia | ✘ | ✅ | ✘ |
39-
| South Africa | ✘ | ✅ | ✘ |
40-
| Spain | ✘ | ✅ | Can use EU metadata boundary. |
41-
| Switzerland | ✘ | ✅ | ✘ |
42-
| Taiwan | ✘ | ✅ | ✘ |
43-
| US State of California | ✘ | ✅ | ✘ |
44-
| US State of Florida | ✘ | ✅ | ✘ |
45-
| US State of Texas | ✘ | ✅ | ✘ |
46-
| FedRAMP Moderate Compliant (Domestic) [^1] | ✅ | ✅ | ✅ |
47-
| FedRAMP Moderate Compliant (International) [^2] | ✘ | ✅ | ✅ |
13+
| Region | Geo Key Manager | Regional Services | Customer Metadata Boundary |
14+
| ------------------------------------------ | --------------- | ----------------- | ----------------------------- |
15+
| Australia | ✅ | ✅ | ✘ |
16+
| Austria | ✘ | ✅ | Can use EU metadata boundary. |
17+
| Brazil | ✘ | ✅ | ✘ |
18+
| Canada | ✅ | ✅ | ✘ |
19+
| Cloudflare Green Energy | ✘ | ✅ | ✘ |
20+
| European Union | ✅ | ✅ | ✅ |
21+
| Exclusive of Hong Kong and Macau | ✘ | ✅ | ✘ |
22+
| Exclusive of Russia and Belarus | ✘ | ✅ | ✘ |
23+
| FedRAMP Moderate Compliant (Domestic) | ✅ | ✅ | ✅ |
24+
| FedRAMP Moderate Compliant (International) | ✘ | ✅ | ✅ |
25+
| France | ✘ | ✅ | Can use EU metadata boundary. |
26+
| Germany | ✅ | ✅ | Can use EU metadata boundary. |
27+
| Hong Kong | ✘ | ✅ | ✘ |
28+
| India | ✅ | ✅ | ✘ |
29+
| ISO 27001 Certified European Union | ✅ | ✅ | Can use EU metadata boundary. |
30+
| Italy | ✘ | ✅ | Can use EU metadata boundary. |
31+
| Japan | ✅ | ✅ | ✘ |
32+
| NATO | ✘ | ✅ | ✘ |
33+
| Netherlands | ✘ | ✅ | Can use EU metadata boundary. |
34+
| Russia | ✘ | ✅ | ✘ |
35+
| Saudi Arabia | ✘ | ✅ | ✘ |
36+
| Singapore | ✅ | ✅ | ✘ |
37+
| South Africa | ✘ | ✅ | ✘ |
38+
| South Korea | ✅ | ✅ | ✘ |
39+
| Spain | ✘ | ✅ | Can use EU metadata boundary. |
40+
| Switzerland | ✘ | ✅ | ✘ |
41+
| Taiwan | ✘ | ✅ | ✘ |
42+
| United Kingdom | ✅ | ✅ | Can use EU metadata boundary. |
43+
| United States of America | ✅ | ✅ | ✅ |
44+
| US State of California | ✘ | ✅ | ✘ |
45+
| US State of Florida | ✘ | ✅ | ✘ |
46+
| US State of Texas | ✘ | ✅ | ✘ |
4847

48+
| Region | Definition |
49+
| ------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
50+
| Australia | Cloudflare will only use data centers that are physically located within Australia to decrypt and service HTTPS traffic. |
51+
| Austria | Cloudflare will only use data centers that are physically located within Austria to decrypt and service HTTPS traffic. |
52+
| Brazil | Cloudflare will only use data centers that are physically located within Brazil to decrypt and service HTTPS traffic. |
53+
| Canada | Cloudflare will only use data centers that are physically located within Canada to decrypt and service HTTPS traffic. |
54+
| Cloudflare Green Energy | Cloudflare will only use data centers that are committed to powering their operations with renewable energy. |
55+
| 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). |
56+
| 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. |
57+
| 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. |
58+
| FedRAMP Moderate Compliant (Domestic) | Cloudflare will only use data centers that are FedRAMP Moderate certified and located within the United States. |
59+
| FedRAMP Moderate Compliant (International) | Cloudflare will only use data centers that are FedRAMP Moderate certified globally. |
60+
| 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. |
61+
| Germany | Cloudflare will only use data centers that are physically located within Germany to decrypt and service HTTPS traffic. |
62+
| Hong Kong | Cloudflare will only use data centers that are physically located within Hong Kong to decrypt and service HTTPS traffic. |
63+
| India | Cloudflare will only use data centers that are physically located within India to decrypt and service HTTPS traffic. |
64+
| 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. |
65+
| Italy | Cloudflare will only use data centers that are physically located within Italy to decrypt and service HTTPS traffic. |
66+
| Japan | Cloudflare will only use data centers that are physically located within Japan to decrypt and service HTTPS traffic. |
67+
| 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/). |
68+
| Netherlands | Cloudflare will only use data centers that are physically located within the Netherlands to decrypt and service HTTPS traffic. |
69+
| Russia | Cloudflare will only use data centers that are physically located within Russia to decrypt and service HTTPS traffic. |
70+
| Saudi Arabia | Cloudflare will only use data centers that are physically located within Saudi Arabia to decrypt and service HTTPS traffic. |
71+
| Singapore | Cloudflare will only use data centers that are physically located within Singapore to decrypt and service HTTPS traffic. |
72+
| South Africa | Cloudflare will only use data centers that are physically located within South Africa to decrypt and service HTTPS traffic. |
73+
| South Korea | Cloudflare will only use data centers that are physically located within South Korea to decrypt and service HTTPS traffic. |
74+
| Spain | Cloudflare will only use data centers that are physically located within Spain to decrypt and service HTTPS traffic. |
75+
| Switzerland | Cloudflare will only use data centers that are physically located within Switzerland to decrypt and service HTTPS traffic. |
76+
| Taiwan | Cloudflare will only use data centers that are physically located within Taiwan to decrypt and service HTTPS traffic. |
77+
| United Kingdom | Cloudflare will only use data centers that are physically located within the United Kingdom to decrypt and service HTTPS traffic. |
78+
| 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. |
79+
| 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. |
80+
| 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. |
81+
| 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. |
4982

5083
Only supported in [Geo Key Manager v2](/ssl/edge-certificates/geokey-manager/).
51-
[^1]: FedRAMP Moderate Compliant (Domestic) was previously named FedRAMP Compliant. It consists of our FedRAMP Moderate compliant data centers in the US.
52-
[^2]: FedRAMP Moderate Compliant (International) consists of all our FedRAMP Moderate compliant data centers globally.

0 commit comments

Comments
 (0)