China Proxies

Run one protocol at a time with the same authorized destination and acceptance rule. Store negotiation errors, proxy authentication responses, TLS failures, destination status, and the observed country so a client mismatch is not confused with a location failure. Build the CHN evidence packet from a redacted configuration, client version, independent exit check, ordered request IDs, response categories, timestamps, and stop-rule outcome. A row without the planned control or required measurement remains inconclusive. Use only an endpoint permitted for the China test, keep missing measurements explicit, and never rotate around a refusal or other mandatory stop.

Identify whether the client, gateway, upstream connection, TLS layer, or destination produced the earliest signal. Rotation must not be used to conceal a quota, block, access-control response, or other explicit stop signal. Pakistan at 700,273 and Philippines at 613,557 are the neighbouring historical records used to place China in Asia. They provide no basis for claiming present stock, equivalent targeting, or destination acceptance. Keep CHN comparator rows labelled and diagnose the requested China route from its own evidence rather than a neighbouring count. Record why each comparator belongs in the authorized review before using it.

Approve the requested country only from its own verified pilot. A successful regional control can explain the experiment, but it cannot replace missing evidence for the route the buyer intends to use. China buyers should reject any CHN result that lacks exit verification, protocol compatibility, session evidence, a stable acceptance rule, failed-attempt accounting, or a bounded retry policy. Approve only the configuration that passed the recorded pilot. Reject any China conclusion built from an unverified exit, hidden failures, or a changed rule, and repeat CHN verification after a material configuration change.