How China network diagnostics work
DNS, HTTP, TCP, ping, and full page fetch — executed on real mainland infrastructure, not simulated.
A diagnostic is only as trustworthy as the place it runs from. Ours execute on launchready.cn infrastructure inside mainland China — not proxied, not simulated from a nearby region. Here is what each check tells you.
DNS resolution
How China resolvers answer for your domain, and how long they take. Surprisingly often, this is where the failure starts.
HTTP response
Status code and time-to-first-byte from mainland nodes — the number that correlates most with “the site feels slow.”
TCP connect
Raw handshake latency across the border, isolated from application overhead.
Ping latency
Round-trip time and packet-loss patterns, which reveal unstable routes that averages hide.
Full page fetch
The whole document: which resources load, which stall, and which never arrive. This is where blocked third-party dependencies show themselves.
Together the five checks produce a per-check verdict plus the failing dependency set — the raw input to a route recommendation.
