Kenya Proxies

Use the same client, endpoint, protocol, browser state, and acceptance rule for both routes. Verify each observed exit independently and retain country labels on every row so results cannot be merged into an ambiguous regional total. Keep the KEN run manifest with client, protocol, network, selector, session rule, authorized endpoint, expected response, exit source, outcome code, and timestamps. Reconcile the manifest with all results before calculating a pass rate. Use only an endpoint permitted for the Kenya test, keep missing measurements explicit, and never rotate around a refusal or other mandatory stop.

Do not call every response difference geographic. A cookie, Accept-Language value, query parameter, edge node, deployment, or stale object may explain it; the log should show which key changed and whether the control changed too. In the maintained Africa list, Nigeria records 38,692 and Mali records 17,598, placing Kenya between them by historical count. That ordering says nothing about which route is currently online or suitable for the buyer's endpoint. Keep KEN comparator rows labelled and diagnose the requested Kenya route from its own evidence rather than a neighbouring count. Record why each comparator belongs in the authorized review before using it.

Compute the buyer-defined success rate from all planned attempts, with failed and inconclusive observations visible. Compare products only when their samples used the same labels, target, timeout, and stop rule. For the KEN order, require a verified Kenya exit, a maintained client and protocol, suitable session behavior, a declared valid-response rate, finite retries, and reviewable evidence. Recalculate after any configuration change instead of carrying forward an old pass. Reject any Kenya conclusion built from an unverified exit, hidden failures, or a changed rule, and repeat KEN verification after a material configuration change.