Skip to content
Get Started

Does Cloudflare Work in China? What Mainland Visitors Get Without the China Network

Cloudflare’s global network was reachable from all three mainland Chinese carriers in our tests, but most requests traveled much farther than Hong Kong or Tokyo. On November 15 and 16, 2026, we ran four rounds of HTTPS requests from mainland China to one Cloudflare address serving sa.net. Of the 92 completed responses, 89 came from Amsterdam, Los Angeles, or London. Three came from Hong Kong.

Median TCP setup to the Cloudflare address took 3.8 to 4.9 times as long as a direct connection to our Tokyo network in the same rounds. Seven China Unicom requests to the Cloudflare address did not complete, while requests from the same probes to Tokyo did.

Riven Cloud sells VPS with carrier-specific routes to mainland China, so this comparison involves our own product. The tables report aggregates from our tests. The original Globalping measurement IDs and pinned Cloudflare address were not retained with this article, so the individual samples are not independently auditable. You can repeat the method against your own hostname, but a new run will use a different probe set.

What Cloudflare offers inside mainland China

As of November 16, 2026, Cloudflare’s global network does not serve visitors from data centers inside mainland China. Its separate China Network runs selected Cloudflare services on mainland data centers operated by JD Cloud.

The onboarding documentation lists two commercial and regulatory requirements: an Enterprise plan with a separate China Network subscription, and a valid Internet Content Provider filing or license for every apex domain being onboarded. Our guide to real-name registration and ICP filings explains the distinction.

Without the China Network, mainland visitors use Cloudflare data centers outside the mainland. Cloudflare’s geographic routing documentation states this directly. Its China Network FAQ also says that Cloudflare reroutes an affected China Network domain to data centers outside China if its ICP filing or license is revoked.

Where mainland visitors land on the global network

Cloudflare announces shared anycast addresses from many locations. The visitor’s ISP chooses a BGP path according to its routing and peering policies, while Cloudflare’s traffic engineering can also influence the result. The closest data center by geography is not guaranteed.

Cloudflare also says the set of data centers able to serve a domain varies between customers. A mainland visitor’s ingress point therefore depends on the addresses available for that zone, the carrier’s path, and current network conditions. The four rounds below show what happened to one address range, not a permanent map of Cloudflare routing in China.

What four rounds from mainland China measured

We used Globalping, a public network of measurement probes, to issue HTTPS requests from China Telecom, China Unicom, and China Mobile in 22 mainland cities. The selected probes were on AS4134, AS4837, AS9808, and provincial carrier networks. Our guide to China’s carrier ASNs explains those identifiers.

The rounds ran at 05:49 and 21:30 China Standard Time on Sunday, November 15, and at 10:30 and 21:30 on Monday, November 16. Probe availability changed between rounds. We included a probe when it completed a request to at least one Riven Cloud host, giving 30, 23, 29, and 18 probes. That produced 100 sets of measurements.

Each probe requested three endpoints: the pinned Cloudflare address serving sa.net, the Tokyo Looking Glass, and the Singapore Looking Glass. The Cloudflare request used /cdn-cgi/trace, whose colo field identifies the data center that received the request. One request on each path returned no probe report, leaving 99 reported requests per path.

CarrierRequestsCloudflare data center or outcome
China Telecom21Amsterdam (21)
China Unicom36Los Angeles (28), London (1), no complete response (7)
China Mobile42London (39), Hong Kong (3)

The landing cities did not change between rounds. All three Hong Kong responses came from one China Mobile probe in Beijing. That probe reached Cloudflare with TCP setup times of 42 and 43 ms in two rounds, compared with 60 ms to Tokyo. On Sunday evening, its Cloudflare TCP setup took 108 ms.

Round (China Standard Time)ProbesCloudflare TCP setupTokyo TCP setupSingapore TCP setup
Sunday 05:4930206 ms53 ms70 ms
Sunday 21:3023257 ms53 ms67 ms
Monday 10:3029205 ms54 ms69 ms
Monday 21:3018236 ms56 ms67 ms

Each cell is the median among reported requests in that round. Globalping defines its tcp stage as the interval after DNS lookup until the TCP connection is established. For a normal TCP handshake, this is approximately one network round trip.

The direct paths changed little across the four rounds. Median TCP setup to Cloudflare was 3.8 to 4.9 times the Tokyo figure. This comparison isolates connection setup. We do not compare first-byte times because /cdn-cgi/trace and the two Looking Glass sites use different TLS and application stacks.

HTTP completion also differed. Tokyo completed all 99 reported requests, Singapore completed 98, and the Cloudflare path completed 92. The seven incomplete Cloudflare requests all came from China Unicom probes in the last three rounds. Each of those probes completed its Tokyo request in the same round. The measurements do not identify whether loss, congestion, a middlebox, or an endpoint behavior caused the failures.

The same probes also requested www.cloudflare.com, which used a different Cloudflare address range. Of 93 completed requests, 88 arrived in Los Angeles, 3 in San Jose, and 2 in Hong Kong. This second target shows that distant ingress was not unique to the sa.net zone, but it does not prove that every Cloudflare range follows the same path.

Between Riven Cloud’s two locations, Tokyo had the shorter TCP setup time in 75 of 97 paired measurements. Singapore was shorter in 22, and 21 of those probes were in Guangdong, Guangxi, or Yunnan.

What the measurement does not show

Four rounds over two days are a snapshot. The probe set changed each time, and only one China Telecom probe was available in the final round. A sample of 18 to 30 probes cannot establish a daily pattern or represent every residential and mobile access network. Some Globalping probes also run in data centers.

One China Unicom probe in Fuzhou was excluded. In every round, connections to the Cloudflare address and both Riven Cloud hosts were reset about 6 ms after opening. That was earlier than a response from Tokyo or Singapore could return, so the reset occurred on the probe-side path or in the test environment. The same probe could load sa.net through the Cloudflare address returned by its resolver.

We pinned one Cloudflare address and did not compare Cloudflare plans. Some China Mobile probes resolved sa.net to a second Cloudflare address and reached San Jose instead of London. Ingress can differ between address ranges within one zone, and both Cloudflare’s traffic engineering and carrier routing can change.

These figures cover connection setup and request completion. They do not measure sustained download throughput, cached-object performance, or whether a particular domain is filtered. A TCP connection to the pinned Cloudflare address opened in 98 of 99 reported attempts. That only establishes reachability for one address from those probes on those two days.

What proxying changes about an optimized origin route

Cloudflare’s proxy status documentation explains the two paths. A proxied record returns Cloudflare anycast addresses, so the visitor connects to Cloudflare first. A DNS-only record returns the origin address, and the HTTP or HTTPS connection goes directly to that origin.

With the proxy enabled, an origin’s route does not improve the visitor-to-Cloudflare leg. The origin network still matters when Cloudflare fetches content from it, but the visitor does not have a direct session with the origin.

This distinction matters for carrier-specific routes such as CTGNet with China Telecom’s CN2 premium segment, China Unicom Premium (CUP), and China Mobile International N2 (CMIN2). Buying an origin with those routes does not guarantee that mainland visitors use them while the hostname remains proxied. Verify the visitor-facing path instead of assuming the origin route survives the proxy.

How we serve sa.net

Riven Cloud uses both paths. Most regions resolve sa.net to Cloudflare. Mainland resolvers normally receive an address on our Singapore network, with no HTTP proxy between the visitor and Riven Cloud.

Across the four rounds, mainland probes resolved sa.net 98 times. They received our Singapore address in 90 cases, with a median TCP setup time of 71 ms. The other eight resolutions returned a Cloudflare address, with a median TCP setup time of 206 ms.

Regional DNS depends on how the authoritative service locates the recursive resolver. A mainland user whose resolver appears to be outside the region can receive the global answer. Any regional DNS design needs to account for that mismatch.

How to check your own hostname

Run the checks from a mainland network or a probe on the carrier you care about:

# Which Cloudflare data center answers?
curl -s https://example.com/cdn-cgi/trace | grep -E '^(colo|loc)='

# Cumulative milestones from the start of one curl request
curl -o /dev/null -s -w 'dns: %{time_namelookup}\ntcp ready: %{time_connect}\ntls ready: %{time_appconnect}\nfirst byte: %{time_starttransfer}\n' https://example.com/

# Which address does the local resolver return?
dig +short example.com A

Test all three carriers and more than one time of day. If mainland China is a small share of the audience, keeping Cloudflare’s proxy may be worth the longer connection setup observed in this sample.

For an Enterprise customer with the required ICP filing or license, the China Network is Cloudflare’s product for serving traffic inside mainland China. Without it, a team that needs a direct carrier path can consider a separate DNS-only hostname or regional DNS. That choice exposes the origin address and removes Cloudflare’s cache, WAF, and DDoS mitigation from the direct requests, so the origin needs its own TLS certificate, access controls, rate limiting, and capacity planning.

After a change, measure again from the target carriers. A domestic access network can still be the slow part, as our guide to last-mile routing problems explains.

Reachability and route quality are different questions

The Cloudflare address was reachable in 98 of 99 reported TCP attempts. Most completed requests still entered Cloudflare in Europe or the United States, while three entered in Hong Kong. Median TCP setup to Tokyo was shorter in every round.

Test the hostname and address range your users will receive. Riven Cloud’s public Looking Glass is available in Tokyo and Singapore, and the current KVM VPS plans use CTGNet, CUP, and CMIN2.

Frequently asked questions about Cloudflare in China

Is Cloudflare blocked in China?

The address in our test was not universally blocked. Probes on China Telecom, China Unicom, and China Mobile opened a TCP connection in 98 of 99 reported attempts, and 92 received a complete HTTP response. This result does not show whether another Cloudflare address or a specific domain is filtered.

Do I need an ICP license to use Cloudflare for visitors in China?

Cloudflare does not require an ICP filing or license for its global network, which serves mainland visitors from outside the mainland. As of November 16, 2026, Cloudflare requires a valid ICP filing or license for each apex domain onboarded to the China Network.

What is the Cloudflare China Network, and who can use it?

It is a separate Cloudflare service running selected products on mainland data centers operated by JD Cloud. As of November 16, 2026, it requires an Enterprise plan, a China Network subscription, and a valid ICP filing or license for each apex domain.

Does a cheaper Cloudflare plan make China slower?

Our tests did not compare plans. Cloudflare says the set of data centers able to serve a domain varies between customers, but its documentation does not say that a specific global plan will select a particular ingress point for mainland users. No global-network plan places a zone inside mainland China without the separate China Network.

Does Cloudflare Turnstile work in China?

As of November 16, 2026, Cloudflare’s China Network FAQ says Turnstile is not supported in mainland China. Cloudflare warns that both China Network zones and global zones may have problems with Turnstile when visitors are in the mainland. Test any form that depends on it from a mainland network.

How do I check which Cloudflare data center serves my visitors in China?

Request /cdn-cgi/trace on your hostname from a mainland network and read the colo line. You can also read the three-letter location code at the end of the CF-Ray response header. Check China Telecom, China Unicom, and China Mobile separately because their paths can differ.

Share