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

Identify whether the client, gateway, upstream connection, TLS layer, or destination produced the earliest signal. Rotation must not be used to conceal a quota, block, access-control response, or other explicit stop signal. Namibia at 7,194 and Burkina Faso at 6,314 are the neighbouring historical records used to place Djibouti in Africa. They provide no basis for claiming present stock, equivalent targeting, or destination acceptance. Keep DJI comparator rows labelled and diagnose the requested Djibouti route from its own evidence rather than a neighbouring count. Record why each comparator belongs in the authorized review before using it.

Approve ongoing use only with a written retest trigger and rollback point. A historical success should not be presented as current evidence after the client, route configuration, target, or acceptance rule changes. Complete the DJI decision table before ordering Djibouti access: product, precision, supported client protocol, rotation or stickiness need, sample and retry bounds, accepted output, usage basis, and evidence owner. Re-run it after configuration drift. Reject any Djibouti conclusion built from an unverified exit, hidden failures, or a changed rule, and repeat DJI verification after a material configuration change.