Country targeting
The only targeting option every product supports.
Values are ISO 3166-1 alpha-2 codes: two letters, case insensitive.
curl --proxy-header "X-Rayobyte-Country: DE" \ -x us-east.gw.rayobyte.com:8000 https://api.ipify.org| Country | Value |
|---|---|
| United States | US |
| United Kingdom | GB |
| Germany | DE |
| Japan | JP |
| Brazil | BR |
GB for the United Kingdom, not UK. UK is not an ISO code and matches
nothing.
Which countries we have
Section titled “Which countries we have”The Geolocation picker in the dashboard lists every country, state and city we currently have coverage for. It reads from the live pool, so it is the authoritative answer to “can I get an exit in X”. That answer changes as devices join and leave.
Country is not the same as entry point
Section titled “Country is not the same as entry point”Connecting through us-east.gw.rayobyte.com and asking for -country-US
gives you a US exit. The entry point only decides where your connection
lands first, which affects latency and nothing else.
This confuses almost everybody once. Entry points explains it properly.
Narrowing further
Section titled “Narrowing further”On Residential you can add state, city, ZIP and ASN.
Always send the country alongside them. A region name on its own is ambiguous. Several countries have a Georgia, a Victoria and a Santiago.
Was this page helpful?
Thanks — that helps us fix it.