CDN in China and Restricted Markets

· Mei-Lin Wu · 4 min read

The China Challenge

China is the world's largest internet market (1+ billion users) but the most challenging for CDN delivery. The Great Firewall (GFW) inspects and filters all cross-border internet traffic, causing: 300-500ms+ latency for content outside China, complete blocks for many services, and unpredictable packet loss on international links. For foundational context, read CDN Monitoring and Observability: Metrics That Matter — FlyFish NWA.

ICP License Requirement

To operate a website in China (served from Chinese servers/CDN), you need an ICP (Internet Content Provider) license — a registration with China's Ministry of Industry and Information Technology (MIIT). There are two types:

Performance Comparison: Edge vs Origin Processing
Metric Edge Processing Origin Processing Improvement
Latency (p50)8–15 ms120–300 ms15–20x faster
Cache Hit Ratio85–95%N/AReduces origin load
TLS Handshake1–5 ms (nearby PoP)50–150 ms10–30x faster
Bandwidth Cost$0.01–0.04/GB$0.05–0.12/GB3–5x cheaper
Availability99.99% (multi-PoP)99.9% (single DC)10x fewer outages
CDN Network Overview — Understanding the delivery architectureCDN Network Overview — Understanding the delivery architecture CDN Network Topology — Content Delivery Flow U User A Tokyo U User B London U User C New York Edge Server Tokyo PoP Edge Server London PoP Edge Server New York PoP Mid-Tier Cache Origin Shield Origin Server Your Server Request Cache Miss Fetch Cache Hit → Instant Response
Figure 1: CDN Network Overview — Understanding the delivery architecture

Without an ICP license, no Chinese CDN provider will serve your content from within China.

CDN Options for China

Chinese CDN Providers

International CDN Providers in China

Architecture: China + Global

Global users → International CDN (Cloudflare/CloudFront)
                    ↓ (failover)
China users  → Chinese CDN (Alibaba Cloud)
                    ↓
              Origin server(s)

Route Chinese users to the Chinese CDN via DNS (geo-routing). This requires: separate CDN configuration for China, ICP license, and potentially separate origin servers or database replicas in China.

Request Lifecycle — How content moves through the CDNRequest Lifecycle — How content moves through the CDN CDN Request Flow — From Browser to Edge CDN Request Lifecycle Step 1 DNS Lookup Step 2 TCP Connect Step 3 TLS Handshake Step 4 Edge Server Step 5 Cache Check Step 6 Response Cache HIT → 5ms response Cache MISS → Fetch origin 0ms ~50ms (cache hit) ~200ms (cache miss)
Figure 2: Request Lifecycle — How content moves through the CDN

Other Restricted Markets

Russia

Russia's TSPU (Technical System for Countermeasures against Threats) can throttle or block international CDN traffic. Russian CDN options: Selectel CDN, G-Core (based in Luxembourg but with Russian PoPs), CDNvideo. International CDNs with Russian PoPs: Cloudflare, Akamai.

Iran

Iran's National Information Network filters international traffic. ArvanCloud is the primary domestic CDN provider. International CDNs have limited or no PoPs in Iran.

Middle East and Africa

Less restricted but with limited CDN PoP coverage. Akamai has the broadest presence. Cloudflare has grown PoPs significantly in these regions. Consider regional providers for specific markets.

Content Compliance

Operating in restricted markets requires content compliance: China requires content censorship mechanisms, Russia requires data localization (see compliance guide), and various countries have specific content restrictions.

External References

References & Standards: Cloudflare documentation · RFC 7234