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

Compare each stage with the single-request baseline. Rising timeouts or denials may reflect target controls, client pooling, gateway behavior, or upstream conditions, so lower pressure and isolate the layer before assigning a cause. The nearest South America count references are Peru with 293,255 and Bolivia with 53,084. They help locate Venezuela in the historical catalogue; they cannot validate today's route or replace country-specific testing. Keep VEN comparator rows labelled and diagnose the requested Venezuela route from its own evidence rather than a neighbouring count. Record why each comparator belongs in the authorized review before using it.

Choose the route for multi-step work only if the authorized flow completes within the stated window often enough for the buyer-defined threshold. Re-test after changing the client or session rule; do not silently change both. The buyer's VEN acceptance sheet should state required protocol, product, country observation rate, continuity or rotation rule, maximum retries, and valid-response evidence. The Venezuela plan advances only when the pilot meets that sheet without excluding failures. Reject any Venezuela conclusion built from an unverified exit, hidden failures, or a changed rule, and repeat VEN verification after a material configuration change.