Somalia Proxies

Run a documented cold request, one immediate repeat, and one request after the chosen wait interval. Keep query strings and headers fixed unless the planned step changes exactly one cache key, and label rather than discard cache misses. The SOM worksheet needs a direct-control identifier, proxy configuration hash, observed country, exit IP, connection identifier, status or error class, safe content marker, and UTC timestamp. Store rejected outcomes instead of repeating until a preferred response appears. Use only an endpoint permitted for the Somalia test, keep missing measurements explicit, and never rotate around a refusal or other mandatory stop.

An observation without an exit check, timestamp, configuration, or acceptance result cannot support the country claim. Mark it incomplete and repeat only if the authorization and stop rule still permit another request. In Africa, Somalia's historical figure falls beside Tunisia (3,820) and Uganda (3,317). Use the relationship to discuss recorded scale, never to promise live availability, comparable precision, or interchangeable outcomes. Keep SOM comparator rows labelled and diagnose the requested Somalia 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 SOM acceptance sheet should state required protocol, product, country observation rate, continuity or rotation rule, maximum retries, and valid-response evidence. The Somalia plan advances only when the pilot meets that sheet without excluding failures. Reject any Somalia conclusion built from an unverified exit, hidden failures, or a changed rule, and repeat SOM verification after a material configuration change.