Linode (Akamai Cloud) Regions, Deployment & Data Residency 2026
Linode runs 33 core regions on Akamai's edge, ten in Europe for EU residency. A region is fixed at creation, and it pairs compute with 4,350+ Akamai PoPs.
Linode (Akamai Cloud) Regions & Deployment verdict
Linode runs 33 core compute regions across six continents, with more distributed regions closer to users.
Ten sit in Europe for EU residency, and dedicated India sites cover Chennai and Mumbai. A region is fixed at creation, so changing it means migrating the instance.
Choose the region nearest your users at creation, because moving means a migration. Use a European site such as Frankfurt, London, Amsterdam or Paris for EU residency, or Chennai and Mumbai for India. The real lever is the Akamai edge: pair compute with Akamai CDN and DDoS on one platform. Two things to settle before production, since neither was on the accessible docs: verify the SLA, and verify any compliance requirements directly with Akamai.
- A Linode's region is set at creation, and changing it requires a migration, a long-running operation.
- Distributed compute regions sit closer to users but support fewer services than the 33 core regions. Jakarta and Sao Paulo also carry data-center-specific pricing above the standard rate.
- Akamai publishes no Compute Instance SLA percentage, and compliance certs were not on the accessible docs.
- Core regions
- 33
- EU regions
- 10
- Akamai edge PoPs
- 4,350+
- Region change
- Migration
- India sites
- Chennai, Mumbai
This page covers where Linode deploys and how residency works. Performance and pricing live on their own pages.
Pick your Linode (Akamai Cloud) region and deployment
15 regions across 5 continents · nearest failover us-central · residency: eu-west, eu-central, nl-ams +2
Create a Compute Instance in us-east with the CLI.
linode-cli linodes create \
--label my-linode \
--type g6-standard-2 \
--region us-east \
--image linode/ubuntu22.04 \
--root_pass 'aComplex@Password'A Linode's region is set at creation; changing it requires a migration. Compute Instances do not autoscale, scale out with a NodeBalancer or LKE. The nearest region above is a placement hint.
Real Linode (Akamai Cloud) regions and deployment commands. Confirm residency guarantees against your contract.
Deploy Linode: CLI, API and Terraform
Install and configure the CLI, then create an instance with a plan type, region and image. --type picks the plan (e.g. g6-nanode-1, g6-standard-2, g6-dedicated-4), --region sets the data center, and a StackScript can bootstrap it.
pip3 install linode-cli --upgrade
linode-cli configure # or: export LINODE_CLI_TOKEN=<token>
linode-cli linodes create \
--label my-linode \
--type g6-standard-2 \
--region us-east \
--image linode/ubuntu22.04 \
--root_pass 'aComplex@Password' \
--booted true
linode-cli regions listPOST to /v4/linode/instances with a Bearer token (OAuth scope linodes:read_write). region and type are required; supply at least one of root_pass, authorized_keys or authorized_users. The region cannot be changed later without a migration.
curl -H 'Content-Type: application/json' \
-H "Authorization: Bearer $TOKEN" \
-X POST https://api.linode.com/v4/linode/instances \
-d '{
"region": "us-east",
"type": "g6-nanode-1",
"image": "linode/ubuntu22.04",
"root_pass": "aComplex@Password",
"label": "my-linode",
"booted": true
}'The linode_instance resource provisions an instance in a region with a plan type and image. Changing region triggers a (long-running) migration, so set update timeouts accordingly. A VPC interface attaches private networking.
resource "linode_instance" "web" {
label = "simple_instance"
image = "linode/ubuntu22.04"
region = "us-central"
type = "g6-standard-1"
authorized_keys = ["ssh-rsa AAAA...Gw== [email protected]"]
private_ip = true
interface {
purpose = "vpc"
subnet_id = 123
ipv4 { vpc = "10.0.4.250" }
}
}Linode (Akamai Cloud) datacenter regions
| Region | Continent | EU | Note |
|---|---|---|---|
| Newark / Washington DC | North America | No | us-east; multiple US East sites |
| Dallas / Atlanta / Miami | North America | No | us-central / us-southeast |
| Fremont / Los Angeles / Seattle | North America | No | us-west |
| Toronto | North America | No | ca-central |
| Sao Paulo | South America | No | region-specific pricing |
| London / London 2 | Europe | Yes | eu-west (UK) |
| Frankfurt / Frankfurt 2 | Europe | Yes | eu-central (Germany) |
| Amsterdam / Paris / Paris 2 | Europe | Yes | Netherlands / France |
| Madrid / Milan / Stockholm | Europe | Yes | Spain / Italy / Sweden |
| Mumbai / Chennai | Asia | No | India-optimized core sites |
| Singapore / Singapore 2 | Asia | No | ap-south |
| Tokyo 2 / Tokyo 3 / Osaka | Asia | No | Japan |
| Jakarta | Asia | No | region-specific pricing |
| Sydney / Melbourne | Oceania | No | ap-southeast |
Region selection and migration
| Aspect | Behavior | Notes |
|---|---|---|
| Region choice | At creation | region is required when the instance is created |
| Region change | Migration (long-running) | Changing region in Terraform triggers a migration |
| Core regions | 33 | Full compute, storage, database services |
| Distributed regions | Limited services | Closer to users, fewer services |
| Region pricing | Higher in Jakarta, Sao Paulo | Data-center-specific pricing |
| India sites | Chennai, Mumbai | Optimized for the India market |
Linode (Akamai Cloud) data residency and regions
| Control | Option | Notes |
|---|---|---|
| EU regions | 10 European sites | Amsterdam, Frankfurt, London, Madrid, Milan, Paris, Stockholm |
| India residency | Chennai, Mumbai | Core sites optimized for India |
| Data scope | Instance in one region | Region fixed at creation, migrate to move |
| Edge security | DDoS protection included | On every instance, via Akamai |
| Compliance | Verify with Akamai | Cert details not on accessible docs pages |
Backed by Akamai's global edge
- Linode's core compute regions are integrated into Akamai's global network, so cloud and CDN/security services run on the same platform
- Akamai's global edge spans 4,350+ points of presence with more than 1 Pbps of edge capacity across 130+ countries and 1,200+ networks
- This lets a Linode workload pair compute with Akamai CDN, DDoS protection and security on the same backbone, reach no other independent VPS provider can match
What to verify before you commit to Linode (Akamai Cloud)
- A Linode's region is set at creation and can only be changed by migrating the instance, a long-running operation, so place it near your users up front
- Akamai does not publish a Compute Instance SLA percentage on its accessible pages, so confirm uptime and credit terms directly before committing production
- SOC 2, ISO 27001, HIPAA and PCI certification details were not on the accessible documentation, so verify regulated requirements with Akamai's trust team
- Jakarta and Sao Paulo carry data-center-specific pricing above the standard rate, so budget for region choice
Linode (Akamai Cloud) Regions & Deployment FAQ
How many regions does Linode have?
33 core compute regions across six continents, each with full compute, storage, database services, plus distributed compute regions that sit closer to users with a smaller service set. North America has the most sites: Newark, Washington DC, Dallas, Atlanta, Miami, Fremont, Los Angeles, Seattle, Toronto. Europe has ten, with more sites across Asia, Oceania, South America.
Can I change a Linode's region after creating it?
Not in place. The region is set when you create the instance, and it can only change by migrating the Linode to a new data center, a long-running operation. In Terraform, changing region triggers that migration, so raise the update timeout. Place the instance near your users up front to avoid it.
Does Linode support EU data residency?
Yes, through ten European core sites: Amsterdam, Frankfurt, Frankfurt 2, London, London 2, Madrid, Milan, Paris, Paris 2, Stockholm. Chennai and Mumbai cover India. DDoS protection is included everywhere. Compliance details for SOC 2, ISO 27001, HIPAA, PCI were not on the accessible documentation, so confirm them with Akamai's trust team.
What makes Linode different from other VPS providers on reach?
Its compute is integrated into Akamai's global network, the world's largest edge: 4,350+ points of presence, 1+ Pbps of capacity, 130+ countries, 1,200+ networks. A Linode workload can therefore pair compute with Akamai CDN, DDoS protection and security on a single backbone, a reach no standalone VPS provider matches.
How do I deploy to a specific Linode region?
Pass the region at creation. With the CLI: linode-cli linodes create --type g6-standard-2 --region us-east --image linode/ubuntu22.04. Via the API, POST /v4/linode/instances with region and type. In Terraform, set region on the linode_instance resource, and changing it later forces a migration. Run linode-cli regions list to see the current region IDs.
Sources & verification
| Source | What was checked | Last checked |
|---|---|---|
| Linode Official | Official product page | July 10, 2026 |
| Akamai Cloud Computing Getting Started With The Linod | Cloud Computing Getting Started With The Linode CLI | July 10, 2026 |
| Akamai Cloud Computing How To Choose A Data Center | Cloud Computing How To Choose A Data Center | July 10, 2026 |
| Akamai Reference Post Linode Instance | Linode API Post Linode Instance | July 10, 2026 |
| Akamai Why Akamai Global Infrastructure | Why Akamai Global Infrastructure | July 10, 2026 |
| Terraform Registry | Latest Instance | July 10, 2026 |
| Vpsbenchmarks Hosters Linode | Independent reference | July 10, 2026 |
Every fact on this Linode (Akamai Cloud) 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.
Explore Linode (Akamai Cloud)
Every page on Linode (Akamai Cloud) in one place, you are on regions & deployment.
Snapshot, score and verdict
You are here
Latency, throughput, uptime and behaviour under scale
Every tier and the entry price
Compared and ranked vs peers
Price and feature change history
Browse the full Cloud Hosting category