Put your traffic in the right place.

Choose the geographic signal your workflow needs, then keep the rest of the connection predictable.

Globe with connected location pins and route arcs

Coverage, with context

Location depth is part of the product.

Coverage is broad, but the useful question is always more specific: which country, which city, which session, and which IP class?

190+Countries

CityTargeting on eligible routes

ZIPDepth on supported plans

Control the signal

Make regional testing feel deliberate.

Country targeting is the first filter. When your plan supports it, add region, city, or ZIP depth to match the market your browser or collector needs to understand.

Use sticky sessions for a consistent multi-step experience. Use rotation when the job benefits from a wider sample of exits.

See the setup flow →

A useful mental model

Four layers of location control.

Country

Start with the market your traffic should represent.

Region

Narrow the route when a broader country pool is not enough.

City

Test local experiences and region-specific content.

Session

Decide how long the selected identity should remain intact.

Good to know

Coverage can change by proxy type.

Inventory and location depth depend on the product and market. Your account and purchase flow are the source of truth for what is available now.

◎

Residential

Broad, trust-sensitive routes with geographic options designed for real-user context.

⌁

Mobile

Carrier routes where mobile network identity is part of the test.

▣

ISP

Stable static exits when the session needs consistency more than breadth.

Ready to route

Find the location your workflow needs.

Choose a product, open your workspace, and configure the route from there.

Create account