Colombia Proxies

Start from the documented clean state, verify the exit, navigate the same path, and capture URL, visible variant marker, response status where available, cookies created, and UTC time. Repeat from a second clean profile before calling a result stable. Give every COL attempt a stable ID and preserve the authorized endpoint, expected outcome, proxy configuration, exit observation, status class, safe response fingerprint, connection count, and time. Keep the failed IDs in the final calculation. Use only an endpoint permitted for the Colombia test, keep missing measurements explicit, and never rotate around a refusal or other mandatory stop.

Distinguish a gateway or connection failure from an HTTP redirect issued by the destination. A different final URL can also come from consent state, account data, language settings, or an experiment, so retain those inputs beside the chain. The adjacent South America catalogue entries around Colombia are Argentina (1,225,819) and Chile (325,035). These are historical totals under the same annual maintenance convention, so they are context for recorded breadth rather than substitutes for the Colombia route test. Keep COL comparator rows labelled and diagnose the requested Colombia route from its own evidence rather than a neighbouring count. Record why each comparator belongs in the authorized review before using it.

Purchase only when someone other than the operator can read the ledger and reproduce the pass/fail decision. A persuasive screenshot without configuration and response context is not sufficient evidence. The COL go/no-go record should specify product, Colombia target precision, supported client protocol, continuity or rotation need, required valid-result rate, usage basis, and cancellation rule. Keep the full denominator and a retest trigger. Reject any Colombia conclusion built from an unverified exit, hidden failures, or a changed rule, and repeat COL verification after a material configuration change.