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

Treat authentication errors, blocks, CAPTCHAs, rate limits, robots guidance, and explicit refusals as review signals rather than obstacles to rotate around. Record the signal and resolve authority before any retry. For Ghana, the nearest stored totals in Africa belong to Equatorial Guinea at 16,685 and Sierra Leone at 15,889. Their historical records are useful controls for data interpretation only, not evidence of equivalent service. Keep GHA comparator rows labelled and diagnose the requested Ghana route from its own evidence rather than a neighbouring count. Record why each comparator belongs in the authorized review before using it.

Approve the route only if the buyer-required DNS behavior is supported by the actual client and verified in the pilot. Prefer the simpler supported configuration when both modes produce equivalent accepted results. The GHA buying rule should combine product eligibility, verified country, maintained-client protocol, required session mode, accepted response, finite retry budget, and cost basis. Retest the Ghana workflow after a material change and reject a result whose denominator omits failures. Reject any Ghana conclusion built from an unverified exit, hidden failures, or a changed rule, and repeat GHA verification after a material configuration change.