Premium vs standard transit to China

What premium routing changes

Premium China routing is a carrier-backed path for your company's internal traffic. Standard international transit uses the public internet path mix. Filing and data-transfer steps stay with you and your counsel in both cases. The difference is not a faster pipe for every packet; it is a different path and a different capacity model.

Where the application serves visitors inside China, the filing and hosting questions dominate the decision; where it serves your own sites and devices, the traffic profile does. Start there, then compare the technical options. A premium path does not remove a filing obligation, and a standard path does not create one where none applies.

Latency: what a premium path can and cannot fix

Light in fiber travels at roughly 200,000 km per second, about two thirds of the speed of light in a vacuum. That sets a physical floor: a 10,000 km path has a one-way propagation time of about 50 ms before any router, queue or detour. A premium path can remove a long detour and reduce jitter by keeping traffic on a controlled route. It cannot beat the fiber floor, and it cannot fix an application that makes six sequential round trips.

Measure round-trip time, jitter and loss from both ends, at peak and off-peak. Use the fiber latency floor tool to separate physics from routing. If the measured round-trip time is close to the floor, the remaining problem is usually application design or congestion, not the path.

Loss, jitter and congestion

Packet loss and jitter are the usual reasons a China-facing application feels slow even when the latency looks acceptable. They come from congestion, route changes, wireless links and overloaded equipment. Premium capacity is usually sold with a committed information rate and a burst allowance; standard transit is best effort. Ask what is committed, what is measured, over what window, and what happens when the measurement misses. A number without a method is not a service definition.

ITU-T Y.1541 defines IP quality-of-service classes and objectives, and ITU-T G.114 gives guidance on one-way transmission time for voice. Use them to frame the questions, not as a substitute for a route test.

Security and exposure

A private line is private in the sense that it is not on the public internet; it is not encrypted by default. Run IPsec or TLS over it as you would over any other path, and keep the same identity and access controls. Standard transit exposes the service to the public internet, so DDoS filtering, a web application firewall, rate limits and a tested failover matter more than the path choice. A private path can still be reached through a public-facing application. Ask where the handoff sits, which side owns the router, and whether the service includes any filtering. Do not assume that a private path removes the need for security controls.

Compliance and filing

MIIT Circular [2017] No. 32, issued by MIIT and reproduced by the Cyberspace Administration of China, targets unapproved cross-border dedicated lines used to conduct cross-border business. It also requires basic telecom operators that lease international private lines to keep user records and to state that the lines are for internal office use only.

Where a website is hosted inside mainland China, an ICP filing is made for each domain through the hosting or CDN provider. MLPS 2.0 grades systems operated in China and sets the controls for each grade. Personal information leaving China follows the Personal Information Protection Law and its export mechanisms. Neither premium routing nor standard transit removes these steps; scope them with your counsel. This is general information, not legal advice. Regulations change, so check the official texts and your own obligations. The compliance primer covers the rule and the steps in more detail; the ICP filing and data residency entries cover the vocabulary.

How to compare two quotes

Ask for the route in writing: the handoff type (Layer 2 or Layer 3), the endpoints, the last mile, the committed rate and the burst. Ask which party provides the router, the cross-connect and the local loop. Ask for the measurement plan: probe locations, test window, packet size, and whether the result is one-way or round-trip. Ask how a fault is escalated and who owns the carrier interface on each side. A support model describes how faults are handled; it does not state an outcome. Ask what is excluded: filing support, equipment, installation, testing, moves and changes. The lowest monthly line item often has the largest excluded scope.

Which option fits

Internal sites, factories, offices and device backhaul usually fit a premium private path because the traffic is the company's own and the path can be controlled. Public visitor traffic is different: filing and hosting dominate, and a CDN plus standard transit may be enough. A hybrid is common: public content on standard transit or a CDN, and a private path for internal systems, management access and device data. Keep the two roles separate in the design so a filing or security issue on one does not force a redesign of the other.

Where the application serves visitors inside China, do not buy a private line and assume the filing question disappears. Where it serves only your own sites, do not buy public transit and assume the internal-use question disappears. Write the use case down in one sentence before the quote: who the users are, where the systems sit, and whether the traffic is internal or public. That sentence is the scope the rest of the comparison hangs on. For the product vocabulary, see IP transit, IEPL vs IPLC, China routing explained, and how networks are named in routing data.

Common mistakes

Comparing Mbps only. Ignoring the last mile. Assuming premium fixes application latency. Assuming standard transit is unregulated. Forgetting that a private line is not encrypted. Buying a route without a baseline measurement. Treating a quote as a service definition. Leaving the filing question to the network team alone.

What stays the same

Both options carry your traffic only; neither is a public internet service for third parties. Both need the same commercial basics: a signed contract, a defined traffic scope, and contacts on both ends. Both also need a named owner on your side for changes, incidents and billing. This is not legal advice. The product definition is scoped per quote; ask for a quote and we scope the current options with you.