Yemen 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 YEM 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 Yemen test, keep missing measurements explicit, and never rotate around a refusal or other mandatory stop.

Classify every difference before explaining it. Separate origin-dependent output from cookies, personalization, cache state, authentication, and ordinary page changes; an unexplained difference stays inconclusive rather than becoming evidence of country behavior. Yemen is bracketed in Asia by Cambodia at 6,662 and Myanmar at 4,485 historical IPs seen so far. The bracket compares annual records only. It predicts neither present routing, geo precision, latency, nor destination acceptance. Keep YEM comparator rows labelled and diagnose the requested Yemen 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 YEM buying rule should combine product eligibility, verified country, maintained-client protocol, required session mode, accepted response, finite retry budget, and cost basis. Retest the Yemen workflow after a material change and reject a result whose denominator omits failures. Reject any Yemen conclusion built from an unverified exit, hidden failures, or a changed rule, and repeat YEM verification after a material configuration change.