Does Zenlayer Work in China? ICP, Data Residency & a China-Reaching Network
Zenlayer runs a network that genuinely reaches mainland China — its Global Network lists data-center locations across two dozen mainland-Chinese cities — so unlike an offshore-only CDN it can be part of a China-facing setup. But the transport layer carries no ICP filing and doesn't settle where your users' data may live. A compliance-first look at the two doors Zenlayer leaves to you.
Does Zenlayer work in China?
Yes — Zenlayer genuinely reaches mainland China, which an offshore-only CDN cannot claim: its own Global Network lists data-center locations in some two dozen mainland cities. But the network is only the transport layer — it carries no ICP filing and does not settle where your users’ data may live.
On its Global Network page Zenlayer lists Mainland China among its data-center locations — Beijing, Shanghai, Shenzhen, Guangzhou, Chengdu, Hangzhou, Suzhou, Wuhan and more — so reaching China is not the question. What that network does not grant is the right to operate: a public mainland site still needs an ICP filing tied to a licensed mainland host, and routing any mainland traffic offshore is a cross-border transfer of personal data under PIPL. The table below separates what Zenlayer’s network does from what it leaves to you.
This is a risk map, not a verdict — ICP, in-country storage or both turn on your entity, your data and who your users are. Our China team can map your exposure with you →
What Zenlayer's own documentation says about China
| Fact | Primary source |
|---|---|
| Zenlayer is not offshore-only — its network runs inside mainland China. On its own Global Network page, Zenlayer lists Mainland China among its data-center locations and, expanded, names some two dozen mainland cities — Beijing, Shanghai, Shenzhen, Guangzhou, Chengdu, Hangzhou, Suzhou, Wuhan, Tianjin, Nanjing, Xi’an and more. Unlike a purely offshore CDN, it has a real in-country footprint that can legitimately form part of a China-facing architecture. | Zenlayer — Global Network (zenlayer.com/global-network), retrieved 2026-10-07 |
| Reaching the mainland is a network fact; being cleared to publish there is a licensing one. A public-facing site shown to mainland visitors turns on an ICP filing tied to a licensed mainland hosting resource and granted to a China-registered entity (State Council Order No. 292; MIIT Order No. 33) — not something a network vendor obtains on your behalf. Zenlayer’s transport can carry you to China; the ICP filing is still yours to hold. | State Council Order No. 292; MIIT Order No. 33 (ICP filing regime) |
| Carry mainland traffic to any offshore node and you cross the border. A mainland visitor’s request routed outside the mainland — a real client IP included — is a cross-border transfer of personal information under PIPL (notice, separate consent and one transfer mechanism, Articles 38–43); for a critical information infrastructure operator or a large-volume handler, personal information collected in China must be stored in the mainland (PIPL Article 40; Cybersecurity Law Article 39 (formerly Article 37)). The network moves the bytes; lawful handling of that personal data is yours. | PIPL Articles 38–43 & 40; Cybersecurity Law Article 39 (formerly Article 37) |
| A China-reaching network is the transport half of the question, not the legal half. Whether Zenlayer "works" in China turns less on reachability — its network is built to reach the mainland and is not blocked — than on two things a network cannot grant you: an ICP filing tied to a mainland hosting resource, and a lawful home for your users' personal data. Those are facts about your entity and your data, not your bandwidth, and no amount of network tuning settles them. | 21YunBox compliance analysis, retrieved 2026-10-07; State Council Order No. 292; MIIT Order No. 33; PIPL Articles 38–43 |
Sources verified by the 21YunBox compliance team on 2026-10-07.
For a mainland-China audience, the real question about Zenlayer is not whether its network is fast, or even whether it reaches the country — it does both. It is whether reaching China is the same as being cleared to operate there. It is not. Zenlayer runs a genuine in-country network, with data centers in Beijing, Shanghai and across the mainland, so unlike an offshore-only CDN it can honestly be part of a China-facing setup. But a network is transport: it does not carry the ICP filing a public mainland site needs, and it does not decide where your users’ personal data is allowed to live. Those two doors stay open, and they are yours to walk through.
Zenlayer in China at a glance
| What decides it | In Zenlayer's own terms |
|---|---|
| Where it runs | A genuine in-country network — Zenlayer's Global Network lists Mainland China among its data-center locations, naming some two dozen mainland cities (Beijing, Shanghai, Shenzhen, Guangzhou, Chengdu, Hangzhou, Suzhou, Wuhan and more). This is not an offshore-only edge. |
| How the mainland is reached | Through in-country sites or its wider Asia-Pacific edge. But network reach is a transport fact: whichever path carries the bytes, it does not by itself make you cleared to operate a public site in the mainland. |
| Serving the public | A public-facing site shown to mainland visitors turns on an ICP filing tied to a licensed mainland host — granted to a China-registered entity, not supplied by a network vendor. The transport reaches China; the ICP filing is yours to hold. |
| Your users' data | Mainland visitors' personal information routed offshore — real client IPs included — is a cross-border transfer PIPL governs; CIIOs and large-volume handlers must keep it in-country. |
| Is it reachable? | Yes — Zenlayer's network is built to reach the mainland and is not blocked. Reachability is the transport question, never the legal one. |
A network that reaches China — which an offshore CDN cannot claim
Start with what is true in Zenlayer’s favor. It is not a purely offshore provider that merely paints packets toward China from the outside. On its own Global Network page Zenlayer lists Mainland China among its data-center locations and, expanded, names some two dozen mainland cities — Beijing and Shanghai, Shenzhen, Guangzhou, Chengdu, Hangzhou, Suzhou, Wuhan and more. That is a real in-country footprint, and it means Zenlayer’s network can legitimately form part of a China-facing architecture.
So the deciding question is not “can it reach China?” It plainly can. It is what that network does and does not carry for you. A network moves bytes. It does not, by itself, confer the legal standing to publish to the Chinese public or settle where personal data may rest. Those are the parts that decide whether a China presence is lawful, and they sit a layer above the wire.
Reaching the mainland is not the same as being ICP-filed
Here is the line a network cannot cross for you. Having bytes reach the mainland — whether from in-country racks or from an offshore edge — is not the same as being cleared to publish there. An in-mainland deployment serving the public waits on a licence you must already hold; an offshore path sidesteps the in-China hosting trigger but earns you no licence either. The network settles the route, never the right to operate.
That license is the ICP filing (ICP 备案) required under State Council Order No. 292 and MIIT Order No. 33. It attaches to a mainland hosting resource and is granted to a China-registered entity — not to a network vendor on your behalf. Zenlayer supplies the transport and the racks; the filing is yours to obtain, and your public mainland site cannot lawfully go live without it. Serving from Hong Kong instead sidesteps the in-China hosting trigger, but it buys you no ICP footing either — it simply keeps the site offshore. Either way, “we already run on Zenlayer” does not answer the licensing question; it only moves where the question gets asked.
Your China users’ data, and the cross-border line
The second door is about data, and it opens the moment mainland traffic leaves the mainland. When a mainland visitor’s request is carried to any offshore node — Hong Kong or elsewhere, both outside the mainland for data-protection purposes — their personal information travels with it, and under China’s Personal Information Protection Law that is a cross-border transfer the handler (you, not Zenlayer) must support with notice, separate consent and one transfer mechanism: a CAC security assessment, the CAC standard contract, or certification (Articles 38–43).
This is also where a purely network-level fix can quietly become a compliance problem. A visitor’s real IP address is itself personal information; forwarding mainland client IPs out across the border to an offshore origin is exactly the kind of transfer PIPL reaches. And if you are a critical information infrastructure operator or a large-volume handler, personal information collected in China must be stored in the mainland (PIPL Article 40; Cybersecurity Law Article 39 (formerly Article 37)) — a residency duty that routing through Hong Kong cannot satisfy.
This is a risk map, not a verdict: whether you need an ICP filing, in-country storage, or both depends on what you serve, how much personal data you hold, and where you route it — worth settling with counsel before you build.
Where 21YunBox fits — a compliant overlay, not a migration
You keep your Zenlayer network. We add the one piece a transport layer cannot grant on its own: compliant, ICP-filed delivery from inside the mainland, set in front of your existing origin — no rebuild, no second codebase, and no move off the connectivity you already run. We work alongside whatever carries your traffic, not against it; the network stays the network, and the compliance layer becomes ours to stand up and keep lawful. Our China team maps your ICP and data-residency obligations against your entity and data volumes, then delivers the in-country delivery and storage a lawful China presence needs — so reaching China and being cleared to operate there finally become the same thing.
Related reading:
