Does Cloudflare Work in China?

Quick answer
The standard Cloudflare network does not have points of presence inside mainland China, so requests are typically served from Hong Kong, Japan, Singapore, or Korea.
That works in the sense that the site loads, but latency and packet loss across the border are unpredictable, and some networks throttle cross-border traffic.
Cloudflare’s China Network is a separate enterprise offering operated with a mainland partner, with points of presence inside the mainland.
The China Network requires an ICP filing for the domains served, so it is not a way to avoid filing.
A common architecture is mainland hosting for mainland users and Cloudflare for the rest of the world.

Does Cloudflare work in mainland China?

Yes, in the sense that a site behind the global Cloudflare network is reachable from the mainland. No, in the sense that traffic is not served from inside the mainland: the standard anycast network has no mainland points of presence, so a user in Shanghai is typically routed to Hong Kong, Japan, Korea, or Singapore.

The practical result is workable but inconsistent. Latency is higher than a domestic CDN, cross-border links fluctuate with congestion and policy, and performance varies by carrier and province. For a brochure site that is acceptable; for an interactive app it is often the difference between usable and not.

What is the Cloudflare China Network?

It is a separate product that places points of presence inside the mainland through a local partner arrangement. It is aimed at enterprise customers, requires a contract rather than a self-serve plan, and is priced differently from the global network.

The critical constraint is compliance: serving content from mainland nodes requires the domain to have an ICP filing, and the partner operates within mainland rules. The China Network is therefore a performance product for organisations that are already compliant, not a route to becoming compliant.

Does Cloudflare remove the need for ICP filing?

No. If the origin server is in the mainland, the filing requirement attaches to that hosting. If the origin is outside the mainland and only the global network is in front, the site is not mainland-hosted and does not need a filing, which is what many teams actually mean when they ask the question.

That distinction is the whole answer. Cloudflare in front of a Hong Kong origin is a legitimate no-filing architecture. Cloudflare in front of a Shanghai origin does not make the Shanghai origin exempt. And Cloudflare China Network requires the filing because it serves from the mainland.

What architecture works best for a mixed audience?

Serve mainland users from mainland infrastructure with a filing, and everyone else from the global network. That usually means two origins, a geo-aware DNS or routing layer, and careful session handling so users do not bounce between environments. It is more complex than a single deployment, which is why many small teams choose one audience first.

If the mainland audience is small, host outside the mainland and accept the latency. If the mainland audience is the product, file and host domestically, then put the global audience behind a CDN. Trying to serve both from one origin is where the worst performance and compliance compromises come from.

Where this bites vibecoders
The generated advice is often that Cloudflare fixes China because it is a CDN. It does not: a proxy outside the mainland cannot make cross-border traffic fast, and putting a proxy in front of a mainland origin does not create a filing. The decision is about where the origin sits, not about which CDN is in front of it.

Where AI coding assistants get this wrong

Assuming a global CDN has points of presence inside mainland China.
Believing Cloudflare in front of a mainland origin removes the filing requirement.
Choosing the global network for an interactive mainland app and attributing latency to the app.
Confusing the self-serve plan with the enterprise China Network.
Serving mainland and global users from one origin without measuring either.
Forgetting that the China Network requires a filing before it will serve the domain.

Checklist

Decide where the origin server sits before choosing a CDN.
Measure real mainland latency from several carriers, not from one test.
Use the global network only for audiences outside the mainland.
Treat the China Network as an enterprise product with compliance prerequisites.
Keep one authoritative source of session state for mixed audiences.
Re-measure after any routing change.

FAQ

Is Cloudflare blocked in China?

The service is not uniformly blocked, but the global network has no mainland points of presence, so requests cross the border. Reachability varies by carrier, province, and time. That variability, rather than a simple block, is what teams encounter when they test from the mainland.

Can I use Cloudflare with a mainland-hosted server?

You can put the global network in front of a mainland origin, but the origin still needs a filing, and the proxy adds a cross-border hop that can make performance worse than serving directly. For mainland users, a domestic CDN with mainland nodes is the usual choice.

Does the China Network work with a Hong Kong company?

The China Network requires ICP filing for the domains it serves, and that filing requires a mainland entity and mainland hosting. A Hong Kong company without a mainland entity therefore cannot use it in the ordinary case, even though it can host in Hong Kong freely.

What latency should I expect from outside the mainland?

It varies too much to promise a number. Cross-border latency is higher and less stable than domestic latency, and the distribution has a long tail during congestion. Measure with real users across carriers before committing an interactive product to a cross-border architecture.