★★★★★ 4.5 CE

Vultr Regions, Deployment & Data Residency 2026

Vultr runs 33 datacenter regions, nine in the EU, with a deep compliance set. A region is fixed at deploy; instances can't migrate, so you recreate.

Cloud HostingVerified today

Full review Pricing Official site ↗

Vultr Regions & Deployment verdict

Verified today·7 sources checked

Vultr runs 33 cloud datacenter regions across six continents, with nine in Europe for EU residency.

Compliance is deep for a VPS host: SOC 2+ with HIPAA, PCI, CSA STAR Level 1, four ISO certifications, and GDPR with a DPA. A region is fixed at deploy, and an instance cannot be migrated, so you destroy and recreate.

How to pick your regions

Pick the region nearest your users at deploy, because moving means destroy-and-recreate. Use a European datacenter such as Amsterdam, Frankfurt or Paris for EU residency, where Vultr's SOC 2, ISO 27001 and GDPR posture is strong. For global reach, deploy per region and route with Global Load Balancers or the Vultr CDN. Two costs to plan for: pricing can vary by region, so confirm it before committing, and DDoS protection is a separate add-on rather than included.

Honest limits

A region is chosen at deploy and an instance cannot be migrated. To move it you destroy and recreate.
Pricing can vary by region due to local networking, hardware, labor, tax costs, and DDoS protection is a $10/month per-instance add-on, not included.
Cloud GPU instances are excluded from the 100% uptime SLA.

Regions: 33
EU regions: 9
Compliance: SOC 2, PCI, ISO x4
Region change: Not migratable
Continents: 6

View sources

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

Pick your Vultr region and deployment

Region and deployment planner

Target region

North AmericaDefault region

16 regions across 5 continents · nearest failover ord · residency: ams, fra, par +3

Create a Cloud Compute instance in ewr with the CLI.

bash

vultr-cli instance create \
  --region ewr \
  --plan vc2-1c-2gb \
  --os 1743 \
  --host my-instance

A Vultr instance's region is fixed at deploy, changing it means destroy-and-recreate. Instances don't autoscale; scale out with Load Balancers or VKE. The nearest region above is a placement hint.

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

Deploy Vultr: CLI, Terraform and API

Install the CLI, export your API key, then create an instance with a region, plan and OS. --region takes a region ID (e.g. ewr, lhr, sgp), --plan a plan ID (e.g. vc2-1c-2gb), --os an OS ID. Boolean flags use the = form.

vultr-clibash

brew install vultr/vultr-cli/vultr-cli
export VULTR_API_KEY=<your-api-key>

# Create an instance
vultr-cli instance create \
  --region ewr \
  --plan vc2-1c-2gb \
  --os 1743 \
  --host my-instance \
  --notify=true

vultr-cli instance list

The vultr_instance resource provisions an instance from a plan, region and OS, with optional backups, DDoS protection and IPv6. region and plan are required, plus one of os_id/iso_id/app_id/image_id/snapshot_id.

Terraformhcl

resource "vultr_instance" "my_instance" {
  plan            = "vc2-1c-2gb"
  region          = "sea"
  os_id           = 1743
  label           = "my-instance-label"
  hostname        = "my-instance"
  enable_ipv6     = true
  backups         = "enabled"
  backups_schedule { type = "daily" }
  ddos_protection = true
}

POST to https://api.vultr.com/v2/instances with a Bearer API key. Pass region, plan and an os_id (or another source). The full parameter list is in the API reference; this is the create-instance pattern.

API v2 (cURL)bash

curl -X POST "https://api.vultr.com/v2/instances" \
  -H "Authorization: Bearer ${VULTR_API_KEY}" \
  -H "Content-Type: application/json" \
  --data '{
    "region": "ewr",
    "plan": "vc2-1c-2gb",
    "os_id": 1743,
    "label": "my-instance",
    "hostname": "my-instance"
  }'

Vultr datacenter regions

Region	Continent	EU	Examples
North America (11)	North America	No	New York, Chicago, Dallas, LA, Miami, Seattle, Silicon Valley, Atlanta, Honolulu, Toronto, Mexico City
South America (2)	South America	No	Sao Paulo, Santiago
Amsterdam / Frankfurt	Europe	Yes	Netherlands, Germany
London / Manchester	Europe	Yes	United Kingdom (x2)
Paris / Madrid / Milan	Europe	Yes	France, Spain, Italy
Stockholm / Warsaw	Europe	Yes	Sweden, Poland
Tokyo / Osaka / Seoul	Asia	No	Japan (x2), Korea
Singapore / Bangalore / Mumbai / Delhi	Asia	No	Singapore, India (x3)
Tel Aviv	Asia / ME	No	Israel
Sydney / Melbourne	Oceania	No	Australia (x2)
Johannesburg	Africa	No	South Africa

Vultr region selection and routing

Aspect	Behavior	Notes
Region choice	At deploy	Set per instance when created
Region change	Not migratable	Destroy and recreate in the new region
Footprint	33 regions / 6 continents	Develop locally, deploy globally
Edge routing	Global Load Balancers + CDN	Process requests at the nearest region
Region pricing	Varies by region	Some locations cost more (networking, taxes)
CDN	$10/mo + bandwidth	Six continents, push and pull zones

Vultr data residency and compliance

Control	Option	Notes
EU regions	9 European datacenters	Amsterdam, Frankfurt, London, Manchester, Paris, Madrid, Stockholm, Warsaw, Milan
Compliance	SOC 2+ (HIPAA), PCI, CSA STAR L1	Audited certifications
ISO certifications	27001:2022, 27017, 27018, 20000-1	Information security and service management
GDPR	Compliant + DPA	Data Processing Addendum available
Data scope	Instance in one region	Region fixed at deploy

What to verify before you commit to Vultr

A Vultr instance's region is set at deploy and cannot be migrated afterward, so to move regions you destroy and recreate the instance, placing it near your users up front
DDoS protection is not bundled, it is a $10/month per-instance add-on, so factor it in for exposed production workloads
Cloud GPU instances are excluded from the 100% uptime SLA due to limited availability, so do not rely on the guarantee for GPU workloads
Pricing can vary by region due to local networking, hardware, labor and tax costs, so confirm the rate for your chosen datacenter

Vultr Regions & Deployment FAQ

How many regions does Vultr have?

33 cloud datacenter regions across six continents. North America has 11: New York, Chicago, Dallas, Los Angeles, Miami, Seattle, Silicon Valley, Atlanta, Honolulu, Toronto, Mexico City. South America has 2 in Sao Paulo and Santiago. Europe has 9. Asia and the Middle East hold 8, Australia 2, Africa 1 in Johannesburg. Global Load Balancers and the Vultr CDN route requests to the nearest region.

Can I change a Vultr instance's region after deploying?

No. The region is chosen when you create the instance, and an instance cannot be migrated to a different region afterward. You destroy it and recreate it in the new region, so place it near your users up front. Note that pricing can vary by region because of local networking, hardware, labor, tax costs.

Does Vultr support EU data residency?

Yes, through nine European datacenters: Amsterdam, Frankfurt, London, Manchester, Paris, Madrid, Stockholm, Warsaw, Milan. Vultr's compliance is deep: SOC 2+ with HIPAA, PCI Merchant, CSA STAR Level 1, and ISO/IEC 27001:2022, 27017, 27018, 20000-1. It is GDPR compliant with a Data Processing Addendum available.

What compliance certifications does Vultr hold?

SOC 2+ with HIPAA, PCI as a Merchant, CSA STAR Level 1, and ISO/IEC 20000-1:2018, 27001:2022, 27017:2015, 27018:2019. It is GDPR compliant and offers a Data Processing Addendum. That is a notably broad set for a VPS-focused provider, useful when you need an audited host in the EU.

How do I deploy to a specific Vultr region?

Pass the region at creation. With the CLI: vultr-cli instance create --region ewr --plan vc2-1c-2gb --os 1743. In Terraform, set region and plan on the vultr_instance resource. Via the API, POST https://api.vultr.com/v2/instances with region, plan, os_id. Region IDs are short codes like ewr for New York, lhr for London, fra for Frankfurt, sgp for Singapore.

Sources & verification

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

Source	What was checked	Last checked
Vultr Official	Official product page	July 10, 2026
GitHub Vultr Vultr Cli	Vultr Vultr CLI	July 10, 2026
Terraform Registry	Latest Instance	July 10, 2026
Vpsbenchmarks Hosters Vultr	Independent reference	July 10, 2026
Vultr Api	API reference	July 10, 2026
Vultr Features Advanced Networking	Features Advanced Networking	July 10, 2026
Vultr Features Datacenter Regions	Features Datacenter Regions	July 10, 2026

Every fact on this Vultr 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.