Germany Proxies

Use the same endpoint, timeout, and acceptance rule for the pilot. Preserve raw status and a safe evidence marker beside the assigned class, and review ambiguous cases without relabeling them merely to improve the reported result. The DEU result table should expose the denominator: planned attempts, valid responses, explicit failures, unresolved rows, and retries. Attach route and client configuration, exit evidence, response class, and time to each row so the calculation can be repeated. Use only an endpoint permitted for the Germany 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. United Kingdom at 1,205,913 and France at 916,416 are the neighbouring historical records used to place Germany in Europe. They provide no basis for claiming present stock, equivalent targeting, or destination acceptance. Keep DEU comparator rows labelled and diagnose the requested Germany route from its own evidence rather than a neighbouring count. Record why each comparator belongs in the authorized review before using it.

Compute the buyer-defined success rate from all planned attempts, with failed and inconclusive observations visible. Compare products only when their samples used the same labels, target, timeout, and stop rule. For the DEU order, require a verified Germany exit, a maintained client and protocol, suitable session behavior, a declared valid-response rate, finite retries, and reviewable evidence. Recalculate after any configuration change instead of carrying forward an old pass. Reject any Germany conclusion built from an unverified exit, hidden failures, or a changed rule, and repeat DEU verification after a material configuration change.