Nicaragua Proxies

Treat the route as the only planned variable. Alternate reference and proxied observations, preserve their order, and compare status, redirect destination, response marker, and observed exit country instead of relying on a single screenshot. Create one NIC row per planned attempt: source permission, client version, network, protocol, redacted selector, observed exit, UTC time, response class, and decision. Keep the sample finite, preserve missing values, and stop on the declared control signal. Use only an endpoint permitted for the Nicaragua test, keep missing measurements explicit, and never rotate around a refusal or other mandatory stop.

A local refusal, proxy authentication error, SOCKS handshake problem, TLS error, and destination denial belong to different owners. Preserve the earliest failing boundary and correct that layer before repeating the country test. Nicaragua sits beside Guatemala (40,402) and Panama (21,420) in the North America historical-count ordering. Preserve the country labels. Combining their observations would erase the distinction the buyer is trying to validate. Keep NIC comparator rows labelled and diagnose the requested Nicaragua route from its own evidence rather than a neighbouring count. Record why each comparator belongs in the authorized review before using it.

Approve the requested country only from its own verified pilot. A successful regional control can explain the experiment, but it cannot replace missing evidence for the route the buyer intends to use. Nicaragua buyers should reject any NIC result that lacks exit verification, protocol compatibility, session evidence, a stable acceptance rule, failed-attempt accounting, or a bounded retry policy. Approve only the configuration that passed the recorded pilot. Reject any Nicaragua conclusion built from an unverified exit, hidden failures, or a changed rule, and repeat NIC verification after a material configuration change.