Does Hosting Behind a CDN in China Require an ICP Filing?

Quick answer
A CDN that caches your content on nodes physically inside mainland China requires a filing for the accelerated domain.
A CDN whose edges sit outside the mainland — Hong Kong, Singapore, Japan — does not, even when it serves Chinese users.
The filing attaches to the domain being accelerated, so it can differ from the origin server’s location.
Vendors that partner with a mainland CDN for China acceleration will require your filing before enabling those nodes.
Serving from outside the mainland adds latency but avoids the entity requirement entirely.

Does a CDN need an ICP filing in China?

It depends on where the CDN’s nodes are, not on where the origin is. Caching is a form of hosting: the edge node stores and serves your content, and if that node is physically in mainland China it is providing an internet information service from China. The domain being accelerated therefore needs a filing held by a mainland entity. This is true even when the origin server is in another country — the requirement follows the content delivery point.

The same logic makes the negative case clear. A CDN with points of presence in Hong Kong, Singapore, Tokyo, or Seoul is outside the mainland, and serving Chinese users from those edges does not create a filing obligation. The user experience is slower than a mainland node, particularly for dynamic content, but the compliance surface stays at zero.

How China acceleration actually works on most CDNs

Global CDN vendors generally do not run their own mainland network. They partner with a licensed Chinese provider, and China acceleration is a separate product switched on per domain. That product requires the filing number before the mainland nodes can be enabled, and the requirement is enforced at configuration time, not after. Until it is supplied, the domain stays on the overseas edges.

There is also a filtering and content dimension that is often missed. Traffic served from mainland nodes passes through the regulatory environment that applies there, which affects what the network will serve. Teams planning to accelerate a domain into China should treat that as a distinct decision from turning on a global CDN, with its own review, rather than an extra checkbox in the same panel.

Choosing between mainland edges and nearby edges

Compare the two options on what each costs you. Mainland edges give the lowest latency to users inside China and require a filing, which requires a mainland entity, which is a corporate commitment. Nearby edges in Hong Kong or Singapore need no filing, work with a domain registered anywhere, and typically add tens of milliseconds for users in southern China, more further north.

For a product whose Chinese audience is a minority of traffic, nearby edges are usually the right answer and the decision is made once. For a product whose core market is China, the entity and the filing are part of doing business there, and mainland edges are a downstream benefit of that choice rather than a separate one.

Decision order for China acceleration:
1. Is a mainland legal entity (or Chinese citizen) available to hold a filing?
   - No  -> use a CDN with Hong Kong / Singapore / Tokyo edges; no filing.
   - Yes -> proceed.
2. Is the origin domain registered to that same entity?
   - No  -> transfer the domain to the entity first.
3. Apply for the filing, then enable the China acceleration product.
   - Verify the domain serves from inside the mainland after enablement.

Where teams get this wrong

The mistake is assuming a CDN is exempt because it is ‘just caching’. Caching is serving, and the location of the cache is what the regulator sees. The second mistake is ordering the acceleration in the belief that a filing can be attached later — configuration is blocked until the number exists, so the deployment stalls on a document with a weeks-long lead time.

A third, subtler case is an origin in the mainland with a CDN outside it, or the reverse. Because the filing attaches to each serving location, a mixed setup needs a clear picture of which nodes are inside the mainland and which domain they serve. Drawing that diagram before buying anything prevents discovering the requirement halfway through a migration.

Where this bites vibecoders
An assistant configuring a CDN will produce a sensible cache and purge setup and mention a China region as a flag, without knowing that enabling it requires a compliance registration tied to a legal entity. The generated plan treats geography as a performance setting. In this one case geography is a legal category, and the plan should split the China path into its own decision with its own prerequisites.

Where AI coding assistants get this wrong

Assuming caching is exempt from the filing requirement that applies to hosting.
Treating China acceleration as a region toggle rather than a separate compliance decision.
Enabling mainland nodes and expecting to supply the filing afterwards.
Planning a mainland origin with overseas edges without mapping which locations are inside China.
Ignoring that a mainland domain must be registered to the filing entity.
Presenting mainland edges as the only way to improve Chinese latency.

Checklist

Identify which of your CDN’s edges are physically inside mainland China.
Decide whether that acceleration is genuinely needed for your traffic mix.
Confirm a mainland entity can hold a filing for the accelerated domain.
Ensure the domain is registered to that entity before applying.
Apply for the filing, then enable the China product and verify from inside the mainland.
If no entity exists, use nearby overseas edges and record the latency trade-off.

FAQ

Can I use Cloudflare in China without an ICP filing?

You can use the global network, whose edges are outside the mainland, and it needs no filing. China acceleration is delivered through a mainland partner network and does require a filing for the accelerated domain. Without one, requests from China are served from overseas edges rather than mainland nodes.

Does the origin server location matter for CDN filing?

The requirement follows each location that serves content. If the edge caches are inside mainland China, a filing is needed regardless of where the origin sits. Conversely, mainland origin servers need a filing even if a CDN outside the mainland fronts them, because the origin itself is providing the service from China.

Is a Hong Kong CDN good enough for users in China?

For much of southern China, yes, in the sense that it is workable. It avoids the filing and entity requirements entirely, and the added latency is usually modest compared with the alternative of no edge presence. For a product whose primary market is China and where latency is a differentiator, mainland nodes justify the compliance work.

Can I move a filing from another CDN provider?

The filing is associated with the domain, but enabling a new provider’s mainland nodes generally involves a fresh submission under that provider’s account. Treat it as a new filing and plan the lead time. Ask the provider what it accepts before assuming an existing number can simply be reused.