China connectivity tests: the evidence gate before we publish
This page is the public record for a narrow, repeatable question: can two prepared routes reach six named web surfaces from a documented connection in China? We publish observed results, dates and limitations—not invented uptime.
PUBLICATION GATE
Evidence before conclusions
Last methodology update: 2026-08-31. A connection means the underlying hotel, office, broadband or mobile path—not the prepared route being measured.
REPEATABLE METHOD
What the probe actually does
The public file is deliberately smaller than the private test configuration. It contains no subscription URL, server address, IP, username, password, key, token or raw error.
- 01Use a dedicated, non-customer test subscription
The probe never reads a customer account or customer credentials. One VLESS/Reality route and one TUIC route are started locally through separate SOCKS ports.
- 02Name the underlying connection
The operator records the city, connection type and test runner. Publishing requires two genuinely distinct underlying China connections.
- 03Check six explicit HTTPS surfaces
Each route requests the same six URLs with a 15-second ceiling and records only outcome, HTTP status and DNS, connection, TLS and total timing.
- 04Publish only complete runs
A run counts toward the gate only when both routes contain all six target IDs. Failures remain failures; they are not removed from the public record.
EXACT TEST SURFACES
Six endpoints, not six blanket promises
A web endpoint is a synthetic signal. Native sign-in, calls, notifications, files, media, APIs and background sync can behave differently.
www.google.commail.google.comweb.whatsapp.comwww.instagram.comslack.comteams.microsoft.comLIMITATIONS
What these checks cannot establish
- They are not a China-wide uptime percentage and must not be interpreted as one.
- They do not represent every hotel, carrier, city, hour, device or app version.
- A successful web response does not guarantee every native-app feature.
- Two routes on one server are resilience methods, not two independent server locations.
- Future runs may differ; every result therefore keeps its test time and connection label.