Togo Proxies

Hold the endpoint, protocol, credentials, and request constant while reopening the transport according to the documented client behavior. Report unique exits, repeats, failed observations, and sample size together; requests multiplexed on one connection are not independent rotations. Make the TGO log append-only during the pilot. Capture permission basis, intended selector, network and protocol, connection boundary, exit result, target response class, bytes where relevant, and UTC time. Apply the original stop condition without rewriting earlier rows. Use only an endpoint permitted for the Togo test, keep missing measurements explicit, and never rotate around a refusal or other mandatory stop.

Do not infer city, ZIP, coordinates, carrier, ASN, language, or resident identity from country success. If a narrower field matters, confirm that the chosen product supports it and validate that field in a separate test. The Africa list places Liberia's 15,092 and Mauritania's 14,691 nearest to the Togo historical total. That placement helps audit the catalogue; it neither confirms current supply nor ranks buyer outcomes. Keep TGO comparator rows labelled and diagnose the requested Togo route from its own evidence rather than a neighbouring count. Record why each comparator belongs in the authorized review before using it.

Approve the route only if the buyer-required DNS behavior is supported by the actual client and verified in the pilot. Prefer the simpler supported configuration when both modes produce equivalent accepted results. The TGO buying rule should combine product eligibility, verified country, maintained-client protocol, required session mode, accepted response, finite retry budget, and cost basis. Retest the Togo workflow after a material change and reject a result whose denominator omits failures. Reject any Togo conclusion built from an unverified exit, hidden failures, or a changed rule, and repeat TGO verification after a material configuration change.