★★★★★ 4.9 CE

Kinsta Deployment, Regions & Data Residency 2026

Kinsta hosts on 27 Google Cloud data centers, eight in the EU for GDPR. Region is fixed per site at creation, with no multi-region failover and a 300+ PoP CDN.

Cloud HostingVerified today

Full review Pricing Official site ↗

Kinsta Deployment & Regions verdict

Verified today·6 sources checked

Kinsta hosts in 27 Google Cloud data centers across six continents, eight of them in the EU for GDPR residency.

You pick a region per site at creation through MyKinsta or the Kinsta API, and it cannot change afterward without a rebuild. There is no multi-region failover, since each site lives in one region.

How to pick your regions

Choose the region nearest your primary audience at creation, since you cannot move it later. For EU or GDPR work, provision in Frankfurt, Amsterdam or another of the eight EU data centers. If you need offsite disaster recovery, budget the external-backups add-on, because daily backups otherwise sit on the same host. For global reach, lean on the included Cloudflare CDN rather than expecting multi-region hosting, which Kinsta does not offer.

Honest limits

A site's region is fixed at creation. Changing it means recreating the site or a support migration.
There is no multi-region failover, since each site runs in a single data center, so resilience is backups plus Cloudflare, not region redundancy. Daily backups live on the same host by default, with offsite copies needing the external-backups add-on.
Region codes accepted by the API come from GET /company/{id}/available-regions, which can differ from generic GCP codes.

Data centers: 27
EU regions: 8
CDN PoPs: 300+
Multi-region failover: No
Cloud: Google Cloud

View sources

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

Pick your Kinsta region and deployment

Region and deployment planner

Target region

North AmericaDefault region

27 regions across 7 continents · nearest failover us-chicago-1 · residency: eu-amsterdam-1, eu-frankfurt-1, eu-paris-1 +5

Provision a WordPress site pinned to us-ashburn-1 via the Kinsta API (region is fixed at creation).

bash

curl -X POST https://api.kinsta.com/v2/sites \
  -H "Authorization: Bearer $KINSTA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "company": "$KINSTA_COMPANY_ID", "display_name": "production", "region": "us-ashburn-1", "install_mode": "new", "admin_email": "[email protected]", "admin_user": "admin", "admin_password": "CHANGE_ME", "site_title": "My Site", "wp_language": "en_US" }'

Kinsta pins each site to one region with no multi-region failover; the region is chosen at creation. Accepted codes come from GET /company/{id}/available-regions.

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

Deploy to a Kinsta region

POST to the Kinsta API to provision a WordPress site pinned to a data center. region takes a Kinsta data-center code (e.g. us-ashburn-1, eu-frankfurt-1); the region is fixed at creation. The call returns 202 with an operation_id you poll for completion.

Create site (cURL)bash

curl -X POST https://api.kinsta.com/v2/sites \
  -H "Authorization: Bearer $KINSTA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "company": "$KINSTA_COMPANY_ID",
    "display_name": "production",
    "region": "us-ashburn-1",
    "install_mode": "new",
    "is_subdomain_multisite": false,
    "admin_email": "[email protected]",
    "admin_user": "admin",
    "admin_password": "CHANGE_ME",
    "is_multisite": false,
    "site_title": "My Site",
    "woocommerce": false,
    "wordpressseo": false,
    "wp_language": "en_US"
  }'

The region field only accepts codes enabled for your company. Fetch the valid list first, then pass one of the returned codes as region in the create-site call.

List available regionsbash

# Returns the data-center codes valid for your account
curl https://api.kinsta.com/v2/company/$KINSTA_COMPANY_ID/available-regions \
  -H "Authorization: Bearer $KINSTA_API_KEY"

Site creation is asynchronous: the create call returns an operation_id. Poll the operations endpoint until it reports complete, then the site is live in the chosen region.

Poll the operation (Node)typescript

const res = await fetch('https://api.kinsta.com/v2/sites', {
  method: 'POST',
  headers: {
    Authorization: `Bearer ${process.env.KINSTA_API_KEY}`,
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
    company: process.env.KINSTA_COMPANY_ID,
    display_name: 'production',
    region: 'eu-frankfurt-1',
    install_mode: 'new',
    admin_email: '[email protected]',
    admin_user: 'admin',
    admin_password: process.env.WP_ADMIN_PW,
    site_title: 'My Site',
    wp_language: 'en_US',
  }),
});
const { operation_id } = await res.json(); // 202 Accepted

Data centers and locations

Region code	Location	Area	Cloud
us-ashburn-1	Ashburn, VA, USA	North America	Google Cloud
us-chicago-1	Chicago, IL, USA	North America	Google Cloud
us-phoenix-1	Phoenix, AZ, USA	North America	Google Cloud
us-sanjose-1	San Jose, CA, USA	North America	Google Cloud
ca-montreal-1	Montreal, Canada	North America	Google Cloud
ca-toronto-1	Toronto, Canada	North America	Google Cloud
sa-saopaulo-1	Sao Paulo, Brazil	South America	Google Cloud
sa-santiago-1	Santiago, Chile	South America	Google Cloud
eu-frankfurt-1	Frankfurt, Germany	Europe	Google Cloud
eu-amsterdam-1	Amsterdam, Netherlands	Europe	Google Cloud
eu-paris-1	Paris, France	Europe	Google Cloud
eu-madrid-1	Madrid, Spain	Europe	Google Cloud
eu-milan-1	Milan, Italy	Europe	Google Cloud
eu-stockholm-1	Stockholm, Sweden	Europe	Google Cloud
eu-zurich-1	Zurich, Switzerland	Europe	Google Cloud
uk-london-1	London, United Kingdom	Europe	Google Cloud
il-jerusalem-1	Jerusalem, Israel	Middle East	Google Cloud
me-riyadh-1	Riyadh, Saudi Arabia	Middle East	Google Cloud
af-johannesburg-1	Johannesburg, South Africa	Africa	Google Cloud
ap-tokyo-1	Tokyo, Japan	Asia-Pacific	Google Cloud
ap-osaka-1	Osaka, Japan	Asia-Pacific	Google Cloud
ap-seoul-1	Seoul, South Korea	Asia-Pacific	Google Cloud
ap-singapore-1	Singapore	Asia-Pacific	Google Cloud
ap-mumbai-1	Mumbai, India	Asia-Pacific	Google Cloud
ap-batam-1	Batam, Indonesia	Asia-Pacific	Google Cloud
ap-sydney-1	Sydney, Australia	Asia-Pacific	Google Cloud
ap-melbourne-1	Melbourne, Australia	Asia-Pacific	Google Cloud

Region reach and delivery

Capability	How it works	Notes
Region selection	Per site, at creation	Chosen in MyKinsta or via the API region field
Change after creation	Not supported	Requires recreating the site or a support migration
Multi-site placement	Independent per site	Each site in an account can sit in a different region
CDN reach	300+ Cloudflare PoPs	Free, HTTP/3 and Brotli; static assets and cached HTML
Edge caching	Dynamic HTML at the edge	Cached HTML served from 300+ PoPs, free on all plans
CDN bandwidth	125-1,500 GB / plan	Included allowance scales with the plan

Data residency and backups

Data	Where it lives	Notes
Site files and database	Chosen GCP region	Fixed to the data center selected at creation
EU / GDPR residency	8 EU data centers	Amsterdam, Frankfurt, Madrid, Milan, Paris, Stockholm, Zurich, London
Daily backups	Same host	Automatic; retained 14 days on lower plans, 30 days on higher
Offsite backups	AWS S3 or GCS	Add-on: $2/site/mo + $1/GB, weekly or monthly
Sub-daily backups	Same host	Add-on: 6-hour $20/site/mo, hourly $100/site/mo
CDN cache	Ephemeral at edge	Cached copies at 300+ Cloudflare PoPs, not persistent storage

What to verify before you commit to Kinsta

A site's region is fixed at creation and cannot be changed later without recreating the site or a support-assisted migration, so pick the region nearest your audience up front
There is no multi-region failover: each site lives in exactly one data center, so resilience comes from backups and Cloudflare in front, not from automatic region redundancy
Daily backups are stored on the same host by default; for true offsite copies you must add the external-backups add-on writing to S3 or GCS
EU data residency is met by choosing one of the eight EU data centers, but Kinsta publishes no EU-only contractual residency guarantee beyond the region choice itself

Kinsta Deployment & Regions FAQ

How many data centers does Kinsta have and where?

27 Google Cloud data centers across six continents. North America has six: Ashburn, Chicago, Phoenix, San Jose, Montreal, Toronto. South America has Sao Paulo and Santiago. Europe has eight including London: Frankfurt, Amsterdam, Paris, Madrid, Milan, Stockholm, Zurich, London. The Middle East adds Jerusalem and Riyadh, Africa adds Johannesburg, and Asia-Pacific holds eight: Tokyo, Osaka, Seoul, Singapore, Mumbai, Batam, Sydney, Melbourne.

Can I change a Kinsta site's region after creating it?

No. The data center is chosen when the site is created, in MyKinsta or via the Kinsta API region field, and cannot change afterward without recreating the site or a support-assisted migration. Each site in your account can sit in a different region, so plan placement per site up front, nearest your audience.

Does Kinsta support EU data residency for GDPR?

Yes, by choosing one of the eight EU data centers: Amsterdam, Frankfurt, Madrid, Milan, Paris, Stockholm, Zurich, London. Site files and database then live in that Google Cloud region. Kinsta does not publish an EU-only contractual residency guarantee beyond the region selection itself, and CDN edge copies are ephemeral worldwide.

Does Kinsta have multi-region failover?

No. Each site runs in exactly one data center, with no automatic multi-region failover. Resilience comes from automatic daily backups, the optional sub-daily and offsite backup add-ons, and the Cloudflare CDN and DDoS protection in front of the site, not from region-level redundancy.

How do I deploy a site to a specific Kinsta region programmatically?

POST to https://api.kinsta.com/v2/sites with a Bearer API key and a region code such as us-ashburn-1 or eu-frankfurt-1 in the body, alongside company, display_name, install_mode, plus the WordPress admin fields. Fetch valid codes first from GET /company/{id}/available-regions. The call returns 202 with an operation_id to poll until the site is live.

Sources & verification

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

Source	What was checked	Last checked
Kinsta Official	Official product page	July 10, 2026
Kinsta Cloudflare Integration	Cloudflare Integration	July 10, 2026
Kinsta Pricing	Pricing and plans	July 10, 2026
Kinsta Service Information Data Center Locations	Service Information Data Center Locations	July 10, 2026
Kinsta Wordpress Hosting Wordpress Backups	Wordpress Hosting Wordpress Backups	July 10, 2026
Kinsta Wordpress Sites Create A Site.Md	Wordpress Sites Create A Site.md	July 10, 2026

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