Glossary
CN2 / CMI Transit
Definition
CN2 and CMI are names for carrier networks and transit paths within China's telecommunications infrastructure. CMI is China Mobile International Limited, China Mobile's international telecommunications services company — providing a full spectrum of international telecommunication services and cloud computing solutions to carriers, enterprises, and users worldwide. CN2 is a China Telecom product. These names appear in the context of cross-border transit — the path traffic takes between mainland Chinese networks and servers outside the country.
What CN2 and CMI are
- Carrier networks and transit paths. Traffic between mainland Chinese networks and servers abroad crosses international links. CN2 and CMI name specific carrier infrastructure in that path.
- Context for the transit problem. Congested cross-border transit is the first of three compounding causes that make websites slow for China visitors. Sites hosted outside mainland China often load in 15–30+ seconds for visitors there, and cross-border transit is the primary variable.
- Per-carrier measurement is the testing doctrine. China testing runs the China Telecom, China Unicom, and China Mobile lines separately — never averaged. When your test tool offers carrier-line filters, run the test on each line and record results separately.
- Names, not performance tiers. CN2 and CMI identify whose network the traffic rides. No performance claim attaches to either name.
What they are not
- Not a CDN. A carrier transit path is not a content delivery network. A mainland CDN means edge caching on China networks to cut cross-border latency. CN2 and CMI are the pipes, not the cache.
- Not a hosting region. Naming a transit path does not replace the need for mainland hosting. The edge has to be inside the country for a CDN to cut the cross-border hop.
- Not a substitute for mainland hosting. The fix for congested transit remains mainland hosting and a China-terminating CDN, not a premium-transit label. Offshore CDNs with no mainland edge still serve Chinese visitors from datacenters abroad. Caching assets on offshore CDN nodes does not touch the cross-border hop.
Why CN2 / CMI transit matters for foreign companies
Which carrier path traffic rides is an invisible variable in every China speed test. A test that averages across carriers hides the problem: a site that loads acceptably on one carrier line may time out on another. The only honest measurement runs each carrier line separately.
Per-carrier measurement is the testing doctrine. 17ce.com and ping.chinaz.com offer carrier-line filters for China Telecom, China Unicom, and China Mobile; boce.com runs tests from mainland nodes. Use them. Record results per carrier — never averaged. What to record per run: timestamp, network type, first-render time, and time to first byte. Conditions change over time, so a single run is not a conclusion.
The fix for congested transit is infrastructure, not a label. Mainland hosting removes the cross-border hop: origin sits on the same networks as visitors. A mainland CDN cuts cross-border latency by caching on China networks. CDN configuration covers static assets, media, and cache policies tuned for China ISPs. These are the proven fixes — not a transit-path upgrade on the origin side.
The hybrid architecture addresses transit directly. Most brands keep their global website and add a China-facing edge layer. Content is authored once and delivered through two paths. The China path can go live while the broader China plan (entity, filing, full deployment) progresses in parallel. Mainland hosting and CDN improve time-to-first-byte and reliability — the transit problem disappears when the origin sits inside the country.
Frequently asked questions
What are CN2 and CMI transit?
CN2 and CMI are names for carrier networks and transit paths within China's telecommunications infrastructure. CMI is China Mobile International Limited, China Mobile's international telecommunications services company. CN2 is a China Telecom product. These names appear in the context of cross-border transit — the path traffic takes between mainland Chinese networks and servers outside the country.
What is the difference between CN2 and CMI?
CN2 is a China Telecom product. CMI is China Mobile International Limited, China Mobile's international telecommunications services company. Both are names for carrier networks and transit paths, not performance tiers — no performance claim attaches to either name.
What about names like CMIN2, CUG, and 9929 — are those faster China routes?
CMIN2, CUG, and 9929 are more carrier line-product names of the same kind as CN2 and CMI — they appear in cross-border transit and China-optimized hosting menus. The same rule applies to all of them: a line name identifies whose network product the traffic rides, not a guaranteed performance tier. No performance claim attaches to any of these names. The honest comparison is per-carrier, per-line measurement of your actual site — the testing doctrine on this page — not label shopping.
When does CN2/CMI transit matter for a China-bound site?
Congested cross-border transit is the first of three compounding causes that make websites slow for China visitors. Sites hosted outside mainland China often load in 15–30+ seconds for visitors there, and cross-border transit is the primary variable. Which carrier path traffic rides is an invisible variable in every China speed test — a site that loads acceptably on one carrier line may time out on another. The only honest measurement runs each carrier line separately.
Is CN2/CMI transit the same thing as a China CDN?
No. A carrier transit path is not a content delivery network. CN2 and CMI are the pipes, not the cache. A mainland CDN means edge caching on China networks to cut cross-border latency — the edge has to be inside the country for a CDN to cut the cross-border hop.
How do I test website performance on each Chinese carrier line?
Per-carrier measurement is the testing doctrine. 17ce.com and ping.chinaz.com offer carrier-line filters for China Telecom, China Unicom, and China Mobile; boce.com runs tests from mainland nodes. Record results per carrier — never averaged. What to record per run: timestamp, network type, first-render time, and time to first byte.
Can CN2/CMI transit replace mainland hosting and CDN?
No. The fix for congested transit remains mainland hosting and a China-terminating CDN, not a premium-transit label. Mainland hosting removes the cross-border hop: origin sits on the same networks as visitors. A mainland CDN cuts cross-border latency by caching on China networks. The transit problem disappears when the origin sits inside the country.
Related terms
- CDN (China Content Delivery Network) — a mainland CDN means edge caching on China networks to cut cross-border latency — the edge has to be inside the country for a CDN to touch the cross-border hop.
- Great Firewall (GFW) — the colloquial term for China's filtering of many global internet services. Requests to filtered services are not answered.
- AWS China Regions — the Amazon Web Services cloud regions physically located in mainland China — currently the Beijing Region and the Ningxia Region.
- Azure China (21Vianet) — a physically separated instance of Microsoft's cloud platform located in mainland China.
Related reading
- How to Test Your Website from China — per-carrier measurement, test tools, and what to record per run.
- Why Your Website Is Slow in China — all three compounding causes and what actually fixes them.
- China CDN for Foreign Companies — the edge-inside-country rule and the full prerequisite chain before any CDN configuration.
- China Digital Entry Glossary — the full term set in one place.
How does your site test on each carrier line?
Per-carrier measurement is the testing doctrine: run Telecom, Unicom, and Mobile separately, and fix what the numbers show. Start with the infrastructure service or the 10-point China readiness diagnostic.
hello@chinagateway.pro