Skip to content
bytetouristbytetourist

Targeting & geo

Before a strategy picks a node, bytetourist filters the fleet down to nodes that satisfy your constraints. Set them via the username encoding or X-Proxy-* headers (see Authentication).

Region (hierarchical)

Section titled “Region (hierarchical)”

region matches a dot-delimited prefix. eu matches eu and eu.west; eu.west does not match eu. This lets you go as broad or as narrow as you like:

Terminal window
# anywhere in the EU
-U "YOUR_API_KEY-region-eu:"
# specifically EU-West
-U "YOUR_API_KEY-region-eu.west:"

Country

Section titled “Country”

cc matches the node’s country code exactly:

Terminal window
-U "YOUR_API_KEY-cc-de:"   # Germany only

Egress class

Section titled “Egress class”

All bytetourist egress is datacenter today — fast, and backed by your own multi-cloud fleet with India-first coverage. There’s no IP-class knob to set; country and region are the targeting dimensions that matter.

Protocol

Section titled “Protocol”

protocol requires a node that advertises a given protocol (e.g. http, socks5). Most traffic doesn’t need this.

Combining constraints

Section titled “Combining constraints”

Constraints stack — the node must satisfy all of them:

Terminal window
-U "YOUR_API_KEY-region-eu.west-cc-de:"

When nothing matches

Section titled “When nothing matches”

By default (strict=false), if no node matches and a primary pick is unhealthy, bytetourist relaxes to the best available node so your request still goes out. Set strict-true to fail fast with an error instead — see Reliability & retries.