Cameroon Proxies

Treat the route as the only planned variable. Alternate reference and proxied observations, preserve their order, and compare status, redirect destination, response marker, and observed exit country instead of relying on a single screenshot. Create one CMR row per planned attempt: source permission, client version, network, protocol, redacted selector, observed exit, UTC time, response class, and decision. Keep the sample finite, preserve missing values, and stop on the declared control signal. Use only an endpoint permitted for the Cameroon test, keep missing measurements explicit, and never rotate around a refusal or other mandatory stop.

A successful connection can still carry an application error, while a valid JSON body can be stale or personalized. Retain response identifiers and timestamps and avoid turning any difference into a geographic claim without a matching control. The maintained Africa ordering places Cameroon next to Cape Verde, recorded at 10,764, and Seychelles, recorded at 10,185. Catalogue adjacency describes the annual dataset only and cannot supply missing route evidence. Keep CMR comparator rows labelled and diagnose the requested Cameroon route from its own evidence rather than a neighbouring count. Record why each comparator belongs in the authorized review before using it.

Compare offers on the same workload, sample size, valid-result rule, metering basis, and minimum commitment. Reject a headline unit price that depends on hiding failed observations or assuming the historical pool is live inventory. Before purchasing Cameroon, make the CMR threshold reproducible: state product, country precision, protocol, session mode, representative workload, valid-result rule, retries, evidence, and retest trigger. Include every planned outcome when applying it. Reject any Cameroon conclusion built from an unverified exit, hidden failures, or a changed rule, and repeat CMR verification after a material configuration change.