Honduras 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 HND 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 Honduras 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 North America catalogue entries around Honduras are Canada (341,790) and El Salvador (51,383). These are historical totals under the same annual maintenance convention, so they are context for recorded breadth rather than substitutes for the Honduras route test. Keep HND comparator rows labelled and diagnose the requested Honduras 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 HND 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 Honduras pilot. Reject any Honduras conclusion built from an unverified exit, hidden failures, or a changed rule, and repeat HND verification after a material configuration change.