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

Separate local resolver errors, proxy-side lookup failures, connection timeouts, and destination responses. A country-targeted exit does not by itself establish the resolver path, and a successful lookup does not prove the requested exit country. The South America record immediately on either side of Guyana is represented by Falkland Islands at 16,525 and French Guiana at 13,586. This is a historical-count comparison. It is not a recommendation to substitute countries or a measurement of current service. Keep GUY comparator rows labelled and diagnose the requested Guyana route from its own evidence rather than a neighbouring count. Record why each comparator belongs in the authorized review before using it.

Purchase only for a documented use that remains within source permissions and operational controls. Technical reachability is not an acceptance criterion by itself. GUY decision review should answer whether the Guyana pilot met product support, country observation, protocol, session, valid-response, usage, and evidence requirements. If a necessary field is absent or the success rule moved, do not approve volume. Reject any Guyana conclusion built from an unverified exit, hidden failures, or a changed rule, and repeat GUY verification after a material configuration change.