Use case
Test your API
from a US address.
See your service the way a US client does. Send requests from a US datacenter IP to check geo rules, allowlists, rate limits and what your edge returns.
$0.75/GB · US exits · new IP per connection · checked 6 Nov 2026
Example
Same request, two origins.
We ran this from a machine in the UK on 6 November 2026. Direct, the lookup returned country GB. Through the proxy, it returned US.
# From your own machine: where does the API think you are? curl -s https://ipinfo.io/json # Through a US datacenter exit: curl -s -x 'http://YOUR_KEY:[email protected]:3128' https://ipinfo.io/json # Same request, and the country field now reads US.
Good for
What this helps you check.
Things you can only see from outside your network.
Geo rules
Does a US visitor get the right price, language or block page?
Allowlists
Is your firewall or API gateway rejecting addresses it should accept?
Edge behaviour
What do your CDN and WAF return to an address that is not yours?
Limits
What it will not tell you.
Know what a datacenter origin is not.
Not a home user
Your service sees a hosting-range address. If you need to see what a residential visitor sees, use a residential tier.
One country
US only during the beta. Other countries need a residential tier.
Not for load tests
Traffic is metered per GB. Use proper load tooling for load tests.
Answers
A few things worth knowing.
Which US location do the addresses come from?+
We only promise US. Do not rely on a particular state or city.
Can I pick the country?+
The datacenter tier is US only. datacenter_country-US works and so does plain datacenter.
Check it from the outside.
Change the password to datacenter and send one request.