South Africa Proxies

Use the same endpoint, timeout, and acceptance rule for the pilot. Preserve raw status and a safe evidence marker beside the assigned class, and review ambiguous cases without relabeling them merely to improve the reported result. The ZAF result table should expose the denominator: planned attempts, valid responses, explicit failures, unresolved rows, and retries. Attach route and client configuration, exit evidence, response class, and time to each row so the calculation can be repeated. Use only an endpoint permitted for the South Africa test, keep missing measurements explicit, and never rotate around a refusal or other mandatory stop.

Distinguish a gateway or connection failure from an HTTP redirect issued by the destination. A different final URL can also come from consent state, account data, language settings, or an experiment, so retain those inputs beside the chain. The adjacent Africa catalogue entries around South Africa are Morocco (646,631) and Egypt (524,973). These are historical totals under the same annual maintenance convention, so they are context for recorded breadth rather than substitutes for the South Africa route test. Keep ZAF comparator rows labelled and diagnose the requested South Africa route from its own evidence rather than a neighbouring count. Record why each comparator belongs in the authorized review before using it.

Buy volume only if an authorized canary identifies a conservative operating range that meets the acceptance rule. The catalogue total must never be converted into a concurrency estimate. Buy South Africa access only after the ZAF canary satisfies the documented precision, protocol, session, response, usage, and evidence rules at the intended operating level. Stop if meeting the threshold would require undeclared retries or discarded failures. Reject any South Africa conclusion built from an unverified exit, hidden failures, or a changed rule, and repeat ZAF verification after a material configuration change.