Skip to content
IPRelay

Network

Infrastructure, explained plainly

How requests move through IPRelay, without inflated numbers.

Residential versus datacenter routing

Residential

Traffic exits through residential connections sourced from consenting participants. Best for location-sensitive public content. Billed per GB.

Datacenter

Traffic exits through IPs hosted in data centres. Best for throughput and stable addressing. Billed per IP and per GB.

Rotating versus sticky sessions

Rotating sessions select a new route for each request. Sticky sessions pin a route to a session identifier you choose, so multi-step workflows see a consistent origin. Datacenter IPs are static by design.

Session lifecycle

  1. 01

    Create

    First request with a session ID allocates a route.

  2. 02

    Reuse

    Requests with the same ID reuse that route.

  3. 03

    Expire

    Idle sessions end after their time window.

  4. 04

    Release

    A new ID, or expiry, releases the route.

Location availability

Pools change over time, so we don't publish static counts. Available locations are shown during configuration.

Maintenance and status notifications

Planned maintenance is announced in advance by email to account contacts and in the dashboard. Incidents are communicated as they are investigated, with follow-up notes once resolved.

Responsible capacity management

We monitor aggregate load, apply per-account concurrency limits, and may throttle or suspend traffic that breaches the Acceptable Use Policy or puts other customers or destination sites at risk.