Does Vultr Work in China? ICP, Data Residency & an Offshore Host
Vultr runs 33 cloud data center regions worldwide — none inside mainland China, the nearest in Japan, South Korea and Singapore — so a China-facing site is served offshore with no ICP-filing path, and your users' data lands outside the mainland under PIPL. A compliance-first look at the two doors.
Does Vultr work in China?
Whether Vultr works for a mainland-China audience is first a licensing and data-residency question, not a latency one. Vultr is reachable and quick from inside China — what carries the legal risk is where the servers sit and what you store on them.
Vultr's own regions page lists 33 cloud data center regions worldwide, and not one is inside mainland China — the closest sit in Japan (Tokyo, Osaka), South Korea (Seoul) and Singapore. So a public site served to mainland visitors from Vultr arrives from offshore, with no ICP-filing path on Vultr itself; and any personal data you keep there for Chinese users is a cross-border transfer PIPL governs. The table below pairs Vultr's own footprint with the China rules it triggers — and the compliant, ICP-filed in-country path.
This is a risk map, not a legal verdict — your obligations turn on what you serve and what you store. Our China team can map the ICP and data-residency path with you →
Compliance snapshot
- ✓ Reachable and fast from inside China on both paths we measured — loaded on every attempt
- ✕ No mainland-China data center — none of Vultr's 33 regions sits in the mainland
- ✕ No ICP-filing path on Vultr itself — a public mainland site is served from offshore
- ! Storing Chinese users' personal data in a Vultr region is a cross-border PI transfer (PIPL)
- ✓ A compliant path exists: ICP-filed in-country delivery and storage in front of your Vultr origin
What Vultr's documentation says, and what we measured from inside China
| Fact | Primary source |
|---|---|
| On Vultr's own regions page, the network spans “33 cloud data center regions” worldwide — in Asia, Tokyo and Osaka (Japan), Seoul (South Korea) and Singapore, plus Bangalore, Mumbai and Delhi NCR (India). None is inside mainland China, and the nearest — Japan, South Korea and Singapore — are all outside the mainland. Vultr's own pitch is to “develop locally, deploy globally,” spinning up “a high performance SSD VPS in 33 cities around the globe” — with no such city in the mainland. | Vultr — Cloud data center regions, retrieved 2026-10-07 |
| Serving a public website to mainland-China visitors from inside the mainland requires an ICP filing (ICP 备案) under the State Council's Order No. 292 and MIIT's Order No. 33, and that filing must attach to a hosting resource physically located in the mainland. Because Vultr operates no mainland-China region, a Vultr-hosted site has no ICP-filing path on Vultr itself — it is reaching mainland users from offshore. | PRC Regulations on Telecommunications (State Council Order No. 292); Administrative Measures for the Filing of Non-operational Internet Information Services (MIIT Order No. 33) |
| Storing Chinese users' personal data in a Vultr region puts it outside the mainland, so PIPL treats it as a cross-border transfer: the handler — you, not Vultr — must give notice, obtain separate consent, and satisfy one transfer mechanism (a CAC security assessment, the CAC standard contract, or certification). A CIIO or large-volume handler must store personal information collected in China inside mainland China (PIPL Article 40; Cybersecurity Law Article 39 (formerly Article 37)) — which none of Vultr's offshore regions can do. | PIPL Chapter III, Articles 38–43 and Article 40; Cybersecurity Law Article 39 (formerly Article 37) |
Measured from inside mainland China on both paths we tested, www.vultr.com is reachable and fast. From an Alibaba Cloud cn-zhangjiakou datacenter probe, 3 runs on 2026-08-28, it completed all 3 loads — median time to first byte 185ms, median largest-contentful-paint 1,383ms, full load ~5.6s. From a Beijing residential broadband line on 2026-08-30 it again completed 3 of 3 — median first byte 206ms, median largest-contentful-paint 1,634ms, full load ~3.4s. This measures the reachability of Vultr's own corporate site, not an application you host in its offshore regions — and reachability is the delivery half, not the legal half. | 21YunBox — China delivery measurement, measured from inside mainland China (datacenter probe and Beijing residential broadband) |
Sources verified by the 21YunBox compliance team on 2026-10-07.
For a mainland-China audience, the first question about Vultr is not how quickly it loads — it is whether your servers are allowed to sit where they sit, and whether your users’ data is allowed to live there. Vultr answers the geography in its own words: across its 33 cloud data center regions, not one is inside mainland China. That makes a China-facing Vultr deployment reachable but wholly offshore, which leaves it without a path to the ICP filing a public mainland site turns on, and turns any personal data you hold for Chinese users into a cross-border transfer Chinese law governs. The speed holds up fine; the licensing and the data residency are where the risk lives.
Vultr in China at a glance
| What decides it | In Vultr's own terms |
|---|---|
| Where it runs | 33 cloud data center regions worldwide. In Asia: Tokyo and Osaka (Japan), Seoul (South Korea), Singapore, plus Bangalore, Mumbai and Delhi NCR (India). No region is inside mainland China. |
| The nearest to China | Japan (Tokyo, Osaka), South Korea (Seoul) and Singapore — each is still outside the mainland, so a mainland-facing site is delivered from offshore. |
| Serving the public | A site shown to mainland visitors from inside China needs an ICP filing tied to a mainland hosting resource. With no mainland region, Vultr offers no ICP-filing path of its own. |
| Your data on Vultr | Personal data of Chinese users stored in a Vultr region sits offshore — a cross-border transfer PIPL governs, plus a data-localization duty for CIIOs and large-volume handlers that offshore regions cannot meet. |
| Is it reachable? | Yes — Vultr's own site loaded on every attempt measured from inside mainland China, on both a datacenter probe and a Beijing home line. Reachability is the delivery half, not the legal half. |
No mainland region, so no footing for an ICP filing
Vultr’s platform is large and genuinely global — its own regions page counts “33 cloud data center regions” and invites you to “spin up a high performance SSD VPS in 33 cities around the globe.” In Asia those cities are Tokyo and Osaka in Japan, Seoul in South Korea, Singapore, and the India metros of Bangalore, Mumbai and Delhi NCR. Scan the list for mainland China and there is nothing there; the closest Vultr gets is Japan, South Korea and Singapore, all of them outside it.
That single geographic fact settles the licensing question before performance is even on the table. A public-facing website delivered to mainland visitors from inside China turns on an ICP filing (ICP 备案) under State Council Order No. 292 and MIIT Order No. 33, and the filing has to attach to a hosting resource that physically sits in the mainland. Vultr has no such resource to attach to, so there is nothing on Vultr to file against. This is where “we’re already running on Vultr” quietly stops working: being able to reach China is not the same as being licensed to operate there, and no amount of region-switching inside Vultr’s map creates the mainland footing a filing requires.
Your China users’ data stays offshore
Point a China audience at a Vultr region and your users’ personal information comes to rest in Japan, South Korea, Singapore or wherever else you deploy — in every case outside the mainland. Under China’s Personal Information Protection Law that movement is a cross-border transfer, and the obligation lands on the handler — you, not Vultr. You have to give notice, obtain separate consent, and clear one transfer mechanism: a CAC security assessment, the CAC standard contract, or certification. And if you are a critical information infrastructure operator or a large-volume handler, personal information collected in China has to be stored in the mainland (PIPL Article 40; Cybersecurity Law Article 39 (formerly Article 37)) — a residency duty that none of Vultr’s regions can satisfy, because none of them is in China.
Reachable, not blocked — which is the point
Vultr is not blocked in China, and we can show it. In 21YunBox’s own measurements from inside the mainland, Vultr’s site finished loading on every attempt on both paths we tested. From an Alibaba Cloud cn-zhangjiakou datacenter probe, three runs on 2026-08-28, it completed all three loads — median time to first byte 185ms, median largest-contentful-paint 1,383ms, full load about 5.6 seconds. From a Beijing residential broadband line on 2026-08-30 it again completed three of three — median first byte 206ms, median largest-contentful-paint 1,634ms, full load about 3.4 seconds. One caveat worth stating plainly: this measures the reachability of Vultr’s own corporate site, not an application you host in its offshore regions — and reachability is the delivery half of the question, not the legal half.
So the exposure on a China-facing Vultr site is not that people cannot get to it. It is that getting to it hands you neither an ICP filing nor in-country data residency. Those are compliance facts, and tuning the network does not move them.
Read this as a risk map rather than a verdict: whether you need an ICP filing, in-country storage, or both comes down to what you serve, how much personal data you hold, and who your users are — all of it worth settling with counsel before you build.
Where 21YunBox fits — a compliant overlay, not a migration
You keep building on Vultr. We add the one piece a host with no mainland presence cannot supply: compliant, ICP-filed in-country delivery in front of your Vultr origin, no rebuild — no second codebase, and no move off Vultr. Our China team maps your ICP and data-residency obligations against your entity and your data volumes, then stands up the in-country delivery and storage a lawful China presence needs, while your application keeps running exactly where it runs today.
Related reading:
Frequently Asked Questions
Does Vultr have a data center in mainland China?
No. Vultr's own regions page lists 33 cloud data center regions worldwide, and none is in mainland China. Its closest locations are in Japan (Tokyo, Osaka), South Korea (Seoul) and Singapore — all outside the mainland — so a site served to mainland visitors from Vultr is delivered from offshore and has no ICP-filing path on Vultr itself.
Is it against the law to host a China-facing site on Vultr?
Not by itself. Two separate duties create the exposure: serving a public site to mainland visitors from inside China requires an ICP filing, which attaches to mainland hosting Vultr does not offer; and holding Chinese users' personal data offshore is a cross-border transfer PIPL governs, with a data-localization duty for CIIOs and large-volume handlers. Treat it as a risk to work through with counsel for your data volumes and role, not a blanket ban.
Can 21YunBox help run a Vultr site in China?
Yes. Our China team can assess your ICP and data-residency exposure and provide the compliant, ICP-filed in-country delivery and storage a US- or EU-based host cannot. Get in touch to work through your setup — your application stays on Vultr.
