Mozambique Proxies

Start from the documented clean state, verify the exit, navigate the same path, and capture URL, visible variant marker, response status where available, cookies created, and UTC time. Repeat from a second clean profile before calling a result stable. Give every MOZ attempt a stable ID and preserve the authorized endpoint, expected outcome, proxy configuration, exit observation, status class, safe response fingerprint, connection count, and time. Keep the failed IDs in the final calculation. Use only an endpoint permitted for the Mozambique test, keep missing measurements explicit, and never rotate around a refusal or other mandatory stop.

When a result changes, compare versions, headers, session behavior, connection reuse, endpoint deployment, and evidence source before blaming the country route. Unknown drift makes the comparison inconclusive. Mozambique's annual record is nearest to Lesotho with 7,938 and Côte d'Ivoire with 7,485 in Africa. This ordering verifies catalogue placement only. Test each requested country separately for current routing and buyer acceptance. Keep MOZ comparator rows labelled and diagnose the requested Mozambique route from its own evidence rather than a neighbouring count. Record why each comparator belongs in the authorized review before using it.

Base the purchase decision on responses that pass the written schema and business acceptance rule, not on raw request count. Include failed and inconclusive calls in the denominator used for provider comparison. Write the MOZ purchase threshold before seeing results: required product and precision, supported protocol, rotation or continuity behavior, sample count, maximum retries, valid-output test, and usage measure. Apply it unchanged to the complete Mozambique pilot. Reject any Mozambique conclusion built from an unverified exit, hidden failures, or a changed rule, and repeat MOZ verification after a material configuration change.