Outcomes on this exact host, updated as traffic lands. An exit that just tripped a block on one site leaves that site's rotation — and no other. google.com and amazon.com are separate surfaces with separate scores.
Edge Proxy · how it works1 GB free
Not a pool.
A decision, per request.
For every request, to every site, Edge Proxy already knows which exit will land — the scoring runs in the background, all the time. Heavy work behind the scenes; nothing you can feel.
01 · Your app
Sends a requestbooking.com
like to any proxy — one endpoint, one login02 · Edge Proxyalways on
Tests IPs for every website, all the time- amazon.combest IP ready
- booking.combest IP ready
- google.combest IP ready
03 · Website
Answers first time200 OK · 0.29s
booking.com · no block, no retryWhat happens on every request.
A normal proxy does one thing: hand you an IP. The edge does four, in the time a normal proxy takes to do one.
- 01Authenticate & meterUsername, password, and the country or -rotate suffix if you sent one. Quota and rate limits are checked before a byte leaves — fail-closed.
- 02Look up the best exit for this targetEvery exit already carries a fresh score for this host — reputation, geography, egress class, health — kept current by probes that never stop.
- 03Dial the winnerThe request leaves through the exit most likely to land. Nothing is injected, rewritten or cached — it is your traffic.
- 04Absorb the failure, if anyA transport-level block is re-run through the next exit before your client hears about it. The failed attempt costs $0.
What the scorer weighs.
Four signals, per exit, per targetThe country you asked for, and only that. Locale, timezone and language of the exit line up with the place it claims to be, because a mismatch is what gets a clean IP flagged.
Residential, mobile or datacenter — the cheapest class that actually lands on this target. Some hosts accept anything; some accept only a phone. The edge knows which is which.
End-to-end probes on every upstream network, continuously. An exit that stops answering is out of every rotation before a request could reach it.
Why you don't feel any of it.
Scoring is not on the request path. Reputation, health and class are computed continuously, between requests, as traffic lands and probes return — so at connect time the choice is a lookup, not a computation. The only thing added to your request is the decision. The thing removed is your retry loop.
0.31smedian time to first byte
0retries in your code
$0for attempts re-run inside the edge
Same 32 requests. Same second.
A normal proxy hands you a random IP and hopes. Edge Proxy scores every exit against your target first.
Run it on your target — freesimulation · run 1
Normal proxy0 blocked
Edge Proxy0 blocked
A rotating pool, and the edge.
Compare providers by price →Rotating pool
Edge Proxy
Which IP you get
Random, from a shared pool
Scored for this exact target
When an exit is blocked
You retry — and pay for it
Re-run inside the edge, unbilled
Choosing a country
Separate hostnames or plans
A suffix on the username
Residential, mobile, datacenter
Separate products
One credential, the class that lands
What your code sees
403 · 429 · CAPTCHA
One 200
Run your own target through it.
1 GB free · no card · if it doesn't beat your provider, you've lost a minute.
Get 1 GB free