Network
North America: two regions, honestly described
us-east (AWS us-east-1, northern Virginia) and us-west (AWS us-west-2, Oregon). Both are egress nodes in our own AWS account with stable Elastic IPs, and both are verified serving real fetches. That is the North American footprint — two regions, not a map of pins.
What we do not offer
No state, city or zip-code targeting, no Canadian or Mexican exits, and no residential or mobile addresses. An earlier version of this page offered every US state, Canadian province and Mexican region over millions of home IPs; none of that existed here. A datacenter exit in Virginia or Oregon is what we sell, and for most country-level work it is exactly enough.
What two US regions actually buy you
Most North American collection work needs a US exit, not a particular street: US-priced pages, US-gated content, feeds and APIs that refuse foreign traffic. Either region answers that.
Having two of them matters for a different reason — independence. They are separate machines in separate AWS regions with unrelated addresses, so a target rate-limiting one address does not slow the other, and you can split a workload or A/B the same fetch from two exits.
us-east
AWS us-east-1, northern Virginia. Lowest latency to US-east-coast and many default-region targets.
us-west
AWS us-west-2, Oregon. West-coast targets, and the second, independent US exit.
Pick per request
region is a query parameter on every fetch — no account-level lock-in, mix freely.
When a datacenter US exit is not enough
Content that varies by state (regional pricing, local inventory, geo-fenced media) is served against a finer location signal than a region-level exit provides, and targets that block cloud address ranges will block ours. We would rather you rule those cases out here than after integrating. If you need city-level residential exits, that is a different product than the one we sell.
Verify, do not assume
GET /v2/proxy/regions is the live, health-gated list. Every fetch response carries public_ip and region_used, so you can assert which exit actually served — including the failover case, where a fully-failed region is served from another and region_used says so.
Questions
- Can I choose a specific US state or city?
- No. You choose us-east or us-west; the exits are in northern Virginia and Oregon respectively. If your work needs a specific state's address, we are not the right tool for it.
- Do you have exits in Canada or Mexico?
- No. Adding a region is a scripted provision and deploy, so if your workload needs one, email support@roamingproxy.com and we will give you a straight answer about whether and when.
Get a key
Create an account and mint an API key in the dashboard. The full endpoint reference — request shapes, parameters and error codes — is published at https://api.roamingproxy.com/v2/docs.