Sudan Proxies

Measure bytes or other billed units from the same authorized workload used for the response test. Keep failed, repeated, and inconclusive attempts visible and calculate cost only after the acceptance rule is applied consistently. A complete SDN sample links authorization, hypothesis, unchanged controls, proxy settings, observed exit, response evidence, failure boundary, and decision. Retain the direct reference and any incomplete Sudan rows until the review is finished. Use only an endpoint permitted for the Sudan 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 Africa record immediately on either side of Sudan is represented by Burkina Faso at 6,314 and Central African Republic at 5,290. This is a historical-count comparison. It is not a recommendation to substitute countries or a measurement of current service. Keep SDN comparator rows labelled and diagnose the requested Sudan route from its own evidence rather than a neighbouring count. Record why each comparator belongs in the authorized review before using it.

Buy country-targeted access only when the pilot meets the required observed-country rate under a declared geolocation source and sample rule. Leave narrower precision out of the promise unless separately proven. The SDN purchase gate combines confirmed Sudan routing with the selected product, maintained protocol, required session behavior, accepted-response definition, finite sample, retries, and cost measure. Repeat the gate after material change rather than relying on catalogue rank. Reject any Sudan conclusion built from an unverified exit, hidden failures, or a changed rule, and repeat SDN verification after a material configuration change.