Cloudflare Docs
Data Localization Suite
Cloudflare Docs
Data Localization Suite
Edit this page
Report an issue with this page
Log into the Cloudflare dashboard
Set theme to dark (⇧+D)
  1. Products
  2. Data Localization Suite
  3. Regional Services
  4. Get started

Get Started

You can use Regional Services through the dashboard or via API.

​​ Configure Regional Services in the dashboard

To use Regional Services, you need to first create a DNS record in the dashboard:

  1. Log in to the Cloudflare dashboard, and select an account and domain.
  2. Go to the DNS tab.
  3. Follow these steps to create a DNS record.
  4. From the Region dropdown, select the region you would like to use on your domain. This value will be applied to all DNS records on the same hostname. This means that if you have two DNS records of the same hostname and change the region for one of them, both records will have the same region.

Refer to the table below for the complete list of available regions and their definitions.

RegionDefinition
AustraliaCloudflare will only use data centers that are physically located within Australia to decrypt and service HTTPS traffic.
CanadaCloudflare will only use data centers that are physically located within Canada to decrypt and service HTTPS traffic.
European UnionCloudflare will only use data centers that are physically located within the European Union. For more details, refer to the list of European Union countries.
IndiaCloudflare will only use data centers that are physically located within India to decrypt and service HTTPS traffic.
JapanCloudflare will only use data centers that are physically located within Japan to decrypt and service HTTPS traffic.
United States of AmericaCloudflare will only use data centers that are physically located within the United States of America to decrypt and service HTTPS traffic.
FedRAMP CompliantCloudflare will only use data centers that are FedRAMP certified.
ISO 27001 Certified European UnionCloudflare will only use data centers that are physically located within the European Union and that adhere to the ISO 27001 certification.
GermanyCloudflare will only use data centers that are physically located within Germany to decrypt and service HTTPS traffic.
SingaporeCloudflare will only use data centers that are physically located within Singapore to decrypt and service HTTPS traffic.
South KoreaCloudflare will only use data centers that are physically located within South Korea to decrypt and service HTTPS traffic.
AustriaCloudflare will only use data centers that are physically located within Austria to decrypt and service HTTPS traffic.
BrazilCloudflare will only use data centers that are physically located within Brazil to decrypt and service HTTPS traffic.
Cloudflare Green EnergyCloudflare will only use data centers that are committed to powering their operations with renewable energy.
Exclusive of Hong Kong and MacauCloudflare 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 BelarusCloudflare will only use data centers that are NOT physically located within Russia and Belarus to decrypt and service HTTPS traffic.
FranceCloudflare will only use data centers that are physically located within Metropolitan France (the European territory of France) to decrypt and service HTTPS traffic.
Hong KongCloudflare will only use data centers that are physically located within Hong Kong to decrypt and service HTTPS traffic.
ItalyCloudflare will only use data centers that are physically located within Italy to decrypt and service HTTPS traffic.
NATOCloudflare 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.
NetherlandsCloudflare will only use data centers that are physically located within the Netherlands to decrypt and service HTTPS traffic.
RussiaCloudflare will only use data centers that are physically located within Russia to decrypt and service HTTPS traffic.
Saudi ArabiaCloudflare will only use data centers that are physically located within Saudi Arabia to decrypt and service HTTPS traffic.
South AfricaCloudflare will only use data centers that are physically located within South Africa to decrypt and service HTTPS traffic.
SpainCloudflare will only use data centers that are physically located within Spain to decrypt and service HTTPS traffic.
SwitzerlandCloudflare will only use data centers that are physically located within Switzerland to decrypt and service HTTPS traffic.
TaiwanCloudflare will only use data centers that are physically located within Taiwan to decrypt and service HTTPS traffic.
US State of CaliforniaCloudflare will only use data centers that are physically located within the US State of California to decrypt and service HTTPS traffic.
US State of FloridaCloudflare will only use data centers that are physically located within the US State of Florida to decrypt and service HTTPS traffic.
US State of TexasCloudflare will only use data centers that are physically located within the US State of Texas to decrypt and service HTTPS traffic.

​​ Configure Regional Services via API

You can also use Regional Services via API. These are some examples of API requests.

List all the available regions
Request
curl "https://api.cloudflare.com/client/v4/accounts/{account_id}/addressing/regional_hostnames/regions" \

--header "X-Auth-Email: <EMAIL>" \

--header "X-Auth-Key: <API_KEY>" | jq .

Response
{
  "success": true,
  "errors": [],
  "result": [
    {
      "key": "ca",
      "label": "Canada"
    },
    {
      "key": "eu",
      "label": "Europe"
    }
  ],
  "messages": []

}
Create a new regional hostname entry
Request
curl "https://api.cloudflare.com/client/v4/zones/{zone_id}/addressing/regional_hostnames" \

--header "X-Auth-Key: <API_KEY>" \

--header "X-Auth-Email: <EMAIL>" \

--header "Content-Type: application/json" \

--data '{"hostname": "ca.regional.ipam.rocks", "region_key": "ca"}' | jq .

Response
{
  "success": true,
  "errors": [],
  "result": {
    "hostname": "ca.regional.ipam.rocks",
    "region_key": "ca",
    "created_on": "2023-01-13T23:59:45.276558Z"
  },
  "messages": []

}
List all regional hostnames for a zone or get a specific one
Request
curl "https://api.cloudflare.com/client/v4/zones/{zone_id}/addressing/regional_hostnames" \

--header "X-Auth-Email: <EMAIL>" \

--header "X-Auth-Key: <API_KEY>" | jq .

Response
{
  "success": true,
  "errors": [],
  "result": [
    {
      "hostname": "ca.regional.ipam.rocks",
      "region_key": "ca",
      "created_on": "2023-01-14T00:47:57.060267Z"
    }
  ],
  "messages": []

}
List all regional hostnames for a specific zone
Request
curl "https://api.cloudflare.com/client/v4/zones/{zone_id}/addressing/regional_hostnames/ca.regional.ipam.rocks" \

--header "X-Auth-Email: <EMAIL>" \

--header "X-Auth-Key: <API_KEY>" | jq .

Response
{
  "success": true,
  "errors": [],
  "result": {
    "hostname": "ca.regional.ipam.rocks",
    "region_key": "ca",
    "created_on": "2023-01-13T23:59:45.276558Z"
  },
  "messages": []

}
Patch the region for a specific hostname
Request
curl --request PATCH \

"https://api.cloudflare.com/client/v4/zones/{zone_id}/addressing/regional_hostnames/ca.regional.ipam.rocks" \

--header "X-Auth-Email: <EMAIL>" \

--header "X-Auth-Key: <API_KEY>" \

--header "Content-Type: application/json" \

--data '{"region_key": "eu"}' | jq .

Response
{
  "success": true,
  "errors": [],
  "result": {
    "hostname": "ca.regional.ipam.rocks",
    "region_key": "eu",
    "created_on": "2023-01-13T23:59:45.276558Z"
  },
  "messages": []

}
Delete the region configuration
Request
curl --request DELETE \

"https://api.cloudflare.com/client/v4/zones/{zone_id}/addressing/regional_hostnames/ca.regional.ipam.rocks" \

--header "X-Auth-Email: <EMAIL>" \

--header "X-Auth-Key: <API_KEY>" | jq .

Response
{
  "success": true,
  "errors": [],
  "result": null,
  "messages": []

}

​​ Terraform support

You can also configure Regional Services using Terraform. For more details, refer to the cloudflare_regional_hostname resource in the Terraform documentation.