Libya Proxies

Disable automatic redirect following for the first pass, label each hop, and repeat with the same cookies and headers. Re-enable normal following only after the raw chain is stored so loops, cross-host moves, and transient failures remain visible. Number the LBY observations before starting. For each number, retain the authorized URL, route configuration, connection policy, exit check, response marker, elapsed time, and pass, fail, or inconclusive label. Do not manufacture extra attempts after the stop rule fires. Use only an endpoint permitted for the Libya 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. Tanzania at 8,244 and Lesotho at 7,938 are the neighbouring historical records used to place Libya in Africa. They provide no basis for claiming present stock, equivalent targeting, or destination acceptance. Keep LBY comparator rows labelled and diagnose the requested Libya route from its own evidence rather than a neighbouring count. Record why each comparator belongs in the authorized review before using it.

Approve a larger purchase only when the paired result repeats under the same written procedure. A one-off success, an unverified exit, or a result that changes with browser state does not establish a dependable country route. LBY purchase review should name the product, required country precision, protocol, session rule, sample size, accepted-result definition, retry ceiling, and retained proof. Verify support and count every scheduled Libya observation before accepting the offer. Reject any Libya conclusion built from an unverified exit, hidden failures, or a changed rule, and repeat LBY verification after a material configuration change.