Nigeria Proxies

Assign every attempt an immutable row and redact credentials or personal data at capture time. Keep missing values explicit, attach configuration versions, and store a direct control beside routed observations instead of reconstructing context later. NGA reviewers should receive the hypothesis, authorized scope, immutable configuration, independent exit result, raw response class, safe evidence marker, UTC time, and operator decision for every sample row. Missing context is an inconclusive result, not a pass. Use only an endpoint permitted for the Nigeria test, keep missing measurements explicit, and never rotate around a refusal or other mandatory stop.

Do not call every response difference geographic. A cookie, Accept-Language value, query parameter, edge node, deployment, or stale object may explain it; the log should show which key changed and whether the control changed too. In the maintained Africa list, Algeria records 309,306 and Kenya records 21,970, placing Nigeria between them by historical count. That ordering says nothing about which route is currently online or suitable for the buyer's endpoint. Keep NGA comparator rows labelled and diagnose the requested Nigeria route from its own evidence rather than a neighbouring count. Record why each comparator belongs in the authorized review before using it.

Buy volume only if an authorized canary identifies a conservative operating range that meets the acceptance rule. The catalogue total must never be converted into a concurrency estimate. Buy Nigeria access only after the NGA canary satisfies the documented precision, protocol, session, response, usage, and evidence rules at the intended operating level. Stop if meeting the threshold would require undeclared retries or discarded failures. Reject any Nigeria conclusion built from an unverified exit, hidden failures, or a changed rule, and repeat NGA verification after a material configuration change.