★★★★★ 4.7 CE

Hetzner Regions, Deployment & Data Residency 2026

Hetzner runs six locations in four zones, three of them Hetzner-owned EU data centers. EU residency is the strength: ISO 27001, German BSI C5, strict GDPR.

Cloud HostingVerified today

Full review Pricing Official site ↗

Hetzner Regions & Deployment verdict

Verified today·7 sources checked

Hetzner runs six locations across four network zones.

Three are EU data centers it owns: Falkenstein and Nuremberg in Germany, Helsinki in Finland. Two US sites and Singapore are colocated.

How to pick your regions

For EU workloads Hetzner is a strong pick on both residency and price. Choose Falkenstein, Nuremberg or Helsinki for ISO 27001 and C5-certified, Hetzner-owned data centers, and use the cheap CX or Arm CAX plans. Keep a multi-server architecture inside one network zone so internal traffic stays free, since Private Networks cannot span zones. The location is fixed at creation, so place it right the first time. Outside the EU, expect US and Singapore to cost more and include far less traffic.

Honest limits

A server's location is fixed at creation. To move it you recreate from a Snapshot or Backup.
Arm CAX and Intel/AMD CX shared plans are EU-only. US and Singapore offer CPX and CCX at about 20% higher prices, and Private Networks cannot span zones.
US and Singapore are colocation sites, not Hetzner-owned data centers.

Locations: 6
Network zones: 4
EU data centers: 3 (owned)
Certifications: ISO 27001, C5
Location change: Recreate

View sources

This page covers where Hetzner deploys and how residency works. Performance and pricing live on their own pages.

Pick your Hetzner region and deployment

Region and deployment planner

Target region

EuropeData-residency region

6 regions across 3 continents · nearest failover nbg1 · residency: fsn1, nbg1, hel1

Create a server in fsn1 with the hcloud CLI.

bash

hcloud server create \
  --image ubuntu-24.04 \
  --type cx23 \
  --name my-server \
  --location fsn1

A Hetzner server's location is fixed at creation; to move, recreate from a Snapshot. Private networks stay within one zone; cross-zone traffic is billed as internet. The nearest region above is a placement hint.

Real Hetzner regions and deployment commands. Confirm residency guarantees against your contract.

Deploy Hetzner: hcloud CLI, API and Terraform

Install hcloud, create a context with a project API token, then create a server with a server type (cx23, cax11, cpx22, ccx13), an image and a location (fsn1, nbg1, hel1, ash, hil, sin). The CLI prints the IPv4 and root password.

hcloud CLIbash

brew install hcloud
hcloud context create my-project   # prompts for the API token

hcloud server-type list
hcloud image list

# Create a server in Nuremberg
hcloud server create \
  --image ubuntu-24.04 \
  --type cx23 \
  --name my-cool-server \
  --location nbg1

POST to https://api.hetzner.cloud/v1/servers with a Bearer token. name, server_type and image are required; location is optional (defaults to a Hetzner-chosen one). public_net controls IPv4/IPv6, and user_data takes a cloud-init script.

Cloud API (cURL)bash

curl \
  -H "Authorization: Bearer $API_TOKEN" \
  -H "Content-Type: application/json" \
  -X POST https://api.hetzner.cloud/v1/servers \
  -d '{
    "name": "my-server",
    "server_type": "cx23",
    "image": "ubuntu-24.04",
    "location": "nbg1",
    "public_net": { "enable_ipv4": true, "enable_ipv6": true }
  }'

The hcloud_server resource provisions a server from a type, image and location, with a public_net block for IPv4/IPv6. A private network attaches via a same-zone subnet (network_zone eu-central, us-east, us-west or ap-southeast).

Terraformhcl

resource "hcloud_server" "server_test" {
  name        = "test-server"
  image       = "ubuntu-24.04"
  server_type = "cx23"
  location    = "hel1"
  public_net {
    ipv4_enabled = true
    ipv6_enabled = true
  }
}

Locations and network zones

Location	City	Network zone	Hetzner-owned
fsn1	Falkenstein, Germany	eu-central	Yes
nbg1	Nuremberg, Germany	eu-central	Yes
hel1	Helsinki, Finland	eu-central	Yes
ash	Ashburn, VA, USA	us-east	No (colocated)
hil	Hillsboro, OR, USA	us-west	No (colocated)
sin	Singapore	ap-southeast	No (colocated)

Hetzner region selection and networking

Aspect	Behavior	Notes
Location choice	At creation, fixed	To move, recreate from a Snapshot or Backup
Network zones	4	eu-central, us-east, us-west, ap-southeast
Private networks	Same-zone only	All subnets must be in one network zone
Cross-zone traffic	Billed as internet	EU-to-US server traffic is normal internet traffic
Plan availability	CX/CAX EU-only	CPX (AMD) and CCX (dedicated) in all six locations
Datacenter ownership	EU owned, US/SG colocated	Germany and Finland Hetzner-owned

Hetzner data residency and compliance

Control	Option	Notes
EU data centers	Falkenstein, Nuremberg, Helsinki	Hetzner-owned (Germany, Finland)
GDPR	Core priority (German HQ)	Strict GDPR compliance
ISO certification	ISO/IEC 27001	EU data center parks (Germany, Finland)
German cloud standard	BSI C5	Cloud Computing Compliance Criteria Catalogue
Data scope	Server in one location	Location fixed at creation

What to verify before you commit to Hetzner

A server's location is fixed at creation; to move it you recreate the server in the new location from a Snapshot or Backup
There are only six locations, and the cheap Arm (CAX) and Intel/AMD (CX) shared plans are EU-only, with US and Singapore offering CPX and CCX at ~20% higher prices and as little as 1 TB of traffic
Private Networks cannot span network zones, and cross-zone traffic (for example EU to US) is billed as normal internet traffic, so a multi-zone deployment loses free internal networking
US and Singapore are colocation sites Hetzner does not own, unlike its German and Finnish data center parks, which matters for the strongest residency assurances

Hetzner Regions & Deployment FAQ

Where are Hetzner's data centers?

Six locations across four network zones. The eu-central zone has three, all Hetzner-owned: fsn1 in Falkenstein and nbg1 in Nuremberg in Germany, hel1 in Helsinki in Finland. us-east is ash in Ashburn, Virginia. us-west is hil in Hillsboro, Oregon. ap-southeast is sin in Singapore. The US and Singapore sites are colocation rather than Hetzner-owned, and Singapore opened in 2024.

Can I change a Hetzner server's location?

No. The location is chosen at creation and cannot be changed for an existing server. To move it, you create a new server in the target location using a Snapshot or Backup of the original. Plan placement up front, especially since private Networks are confined to a single network zone.

Does Hetzner support EU data residency?

Strongly. Hetzner is a German company with strict GDPR compliance, and its three EU data centers in Falkenstein, Nuremberg, Helsinki are owned and operated by Hetzner and ISO/IEC 27001 certified. It also holds the German BSI C5, the Cloud Computing Compliance Criteria Catalogue, a meaningful assurance for regulated and business-critical EU workloads.

Why are some Hetzner plans EU-only?

The cheapest shared families, CX on Intel/AMD and CAX on Ampere Arm, are available only in the EU, at Falkenstein, Nuremberg, Helsinki. The CPX shared line on AMD and the dedicated CCX line on AMD EPYC run in all six locations. US and Singapore prices run about 20% higher and include as little as 1 TB of traffic against 20 TB in the EU, so Hetzner's value is strongest in Europe.

How do I deploy to a specific Hetzner location?

Pass the location. With the CLI: hcloud server create --image ubuntu-24.04 --type cx23 --name my-server --location nbg1. Via the API, POST to https://api.hetzner.cloud/v1/servers with server_type, image, location. In Terraform, set location on the hcloud_server resource. Valid codes are fsn1, nbg1, hel1, ash, hil, sin.

Sources & verification

Verified by ComparEdgeMethod: Vendor docs, official pages, and selected independent sources

Source	What was checked	Last checked
Hetzner Official	Official product page	July 10, 2026
Hetzner Cloud	Cloud	July 10, 2026
Hetzner Cloud General Purpose	Cloud General Purpose	July 10, 2026
Hetzner Developer docs	Product documentation	July 10, 2026
Hetzner Developer docs	General Locations	July 10, 2026
Hetzner Developer docs	Servers Faq	July 10, 2026
Hetzner Tutorials Howto Hcloud Cli	Tutorials Howto Hcloud CLI	July 10, 2026

Every fact on this Hetzner page is tied to a named source and a verification date. Freshness-sensitive figures trace to the sources above; verify against the vendor before relying on them.