Premium residential · shared bandwidth

Residential routes with granular location control

Use an ISP-origin route when the workload needs finer location controls than country or continent. The pool is shared and rotating, with bandwidth billing and a 5 GB minimum order.

Review current plans

Current catalogue

5 GB minimum

The smallest current bandwidth order, shown before checkout.

Minimum order
5 GB
Payable total
$13.75
Unit rate
$2.75/GB
Traffic validity
186 days

Purchase unit: Bandwidth, not an IP lease.

The lowest listed rate is $0.90/GB only at 1,024 GB ($921.60 total).

No free trial. This checkout opens the smallest current catalogue order; review the terms before payment.

Workload fit

Choose Premium Residential when location precision shapes the result

This product fits authorized work that needs an ISP-origin route plus a specific geographic or network selector. Confirm that the destination permits the activity and that a shared route is acceptable before ordering.

  1. Regional experience checks

    Review public or owned web experiences from one supported country, state, city, ZIP, coordinate, or ASN context at a time.

  2. Localized public-data collection

    Collect permitted public information where the observed response depends on granular location, while respecting access rules and rate limits.

  3. Ad and brand placement review

    Inspect authorized campaigns or brand appearances from a selected regional context without presenting the route as a permanent household address.

  4. Route-sensitive integration checks

    Exercise an integration you control through rotating or requested sticky sessions before increasing traffic.

Product decision

Compare the four products without a default winner

Start with network origin, then reconcile targeting, session behaviour, and the complete entry order. No product is presented as a universal winner.

Databay proxy product decision table
Entry order5 GB · $13.75 totalBandwidth order, not an IP leaseRoute contract
Targeting
One country, state, city, ZIP, coordinate, or ASN selector at a time; route availability varies
Session request
Requested sticky sessions up to 120 minutes; continuity can end early
Rotation
Connection-based rotation; a fresh IP is not guaranteed
Protocols
HTTP proxying, HTTPS CONNECT, and SOCKS5
Decision boundary

Granular ISP-origin targeting is central to the authorized workload.

Shared and rotating; one selector at a time; 5 GB minimum order.

Entry order25 GB · $13.75 totalBandwidth order, not an IP leaseRoute contract
Targeting
One country or continent selector at a time; route availability varies
Session request
Requested sticky sessions up to 30 minutes; continuity can end early
Rotation
Connection-based rotation; a fresh IP is not guaranteed
Protocols
HTTP proxying, HTTPS CONNECT, and SOCKS5
Decision boundary

Country-or-continent residential targeting is enough and budget control matters.

Less granular targeting and a 30-minute maximum sticky request.

Entry order5 GB · $17.75 totalBandwidth order, not an IP leaseRoute contract
Targeting
One country or continent selector at a time; route availability varies
Session request
Requested sticky sessions up to 120 minutes; continuity can end early
Rotation
Connection-based rotation; a fresh IP is not guaranteed
Protocols
HTTP proxying, HTTPS CONNECT, and SOCKS5
Decision boundary

The workload specifically needs a carrier-network origin.

No carrier, radio-generation, device, SIM, or modem selection.

Entry order10 GB · $12.50 totalBandwidth order, not an IP leaseRoute contract
Targeting
One country or continent selector at a time; route availability varies
Session request
Requested sticky sessions up to 120 minutes; continuity can end early
Rotation
Connection-based rotation; a fresh IP is not guaranteed
Protocols
HTTP proxying, HTTPS CONNECT, and SOCKS5
Decision boundary

A shared hosting-network route fits the workload.

Not residential, mobile, dedicated, or static IP space.

Connection check

Validate one controlled route before scaling

Create credentials in the dashboard, apply one supported targeting selector, then choose rotating or requested sticky behavior. Test against a destination you own or are authorized to assess.

Connection manifest

One gateway · two session modes

Transport
Gatewaygw.databay.co:8888ProtocolsHTTP proxying, HTTPS CONNECT, and SOCKS5
Access boundary
Username/password or dashboard-configured source-IP allowlisting
Session identity
Rotating username fixtureUSERNAME-zone-residentialSticky username fixtureUSERNAME-zone-residential-sessionId-qa%2Dsession%2D01

Keep credentials out of source control and logs. Validate the observed route against a destination you own or are authorized to test before increasing traffic.

Both modes use the same gateway. Rotating omits sessionId; sticky adds the non-secret task fixture shown above. Either mode remains a route request, not proof of supply, a fresh exit, or uninterrupted continuity.

The generator never asks for a password. It measures deliberate client-selection and copy actions, not the generated configuration or secret value.

Three mock-tested rotating setup fixtures

Each client applies the same canonical product zone and bounded failure path differently.

cURLcURL 8.21.0 local mock trace
: "${DATABAY_PROXY_PASS:?Load DATABAY_PROXY_PASS from your secret store}"
# cURL URL-decodes --proxy-user once; %25 preserves literal % in routing values.
DATABAY_PROXY_USER='USERNAME-zone-residential'

curl --disable --silent --show-error --fail-with-body \
  --proxy 'http://gw.databay.co:8888' \
  --proxy-basic \
  --proxy-user "${DATABAY_PROXY_USER}:${DATABAY_PROXY_PASS}" \
  --connect-timeout 10 \
  --max-time 30 \
  'https://databay.com/what-is-my-ip/json'

cURL receives proxy credentials through --proxy-user and URL-decodes them once.

An HTTPS destination uses CONNECT through this HTTP proxy; it does not require an https:// proxy URL.

Read the cURL setup guide
Python RequestsRequests 2.34.2 pinned local mock fixture
import os
import sys
from urllib.parse import quote
import requests

username = quote("USERNAME-zone-residential", safe="")
password = quote(os.environ["DATABAY_PROXY_PASS"], safe="")
proxy_url = f"http://{username}:{password}@gw.databay.co:8888"
proxies = {"http": proxy_url, "https": proxy_url}

try:
    response = requests.get(
        "https://databay.com/what-is-my-ip/json",
        proxies=proxies,
        timeout=(10, 20),
    )
    response.raise_for_status()
    print(response.json())
except requests.exceptions.Timeout:
    print("Proxy check timed out within the configured request budget.", file=sys.stderr)
    raise SystemExit(1)
except requests.exceptions.RequestException:
    print("Proxy check failed; verify credentials, route availability, and destination permission.", file=sys.stderr)
    raise SystemExit(1)

Requests proxy authentication lives in a percent-encoded proxy URL assembled at runtime.

The mapping keys select destination schemes. Both can use the same HTTP proxy URL; the read timeout is an inactivity limit, not a total download deadline.

Read the Python Requests setup guide
Node.js / UndiciNode 24.14.0 with installed Undici 8.9.0 local mock trace
import { fetch, ProxyAgent } from 'undici';

const password = process.env.DATABAY_PROXY_PASS;
if (!password) throw new Error('DATABAY_PROXY_PASS is required');

const username = 'USERNAME-zone-residential';
const dispatcher = new ProxyAgent({
  uri: 'http://gw.databay.co:8888',
  token: `Basic ${Buffer.from(`${username}:${password}`).toString('base64')}`,
});

try {
  const response = await fetch('https://databay.com/what-is-my-ip/json', {
    dispatcher,
    signal: AbortSignal.timeout(30_000),
  });
  if (!response.ok) throw new Error(`Unexpected HTTP status ${response.status}`);
  console.log(await response.json());
} catch (error) {
  const message = error instanceof Error && error.name === 'TimeoutError'
    ? 'Proxy check exceeded the 30 second deadline.'
    : 'Proxy check failed; verify credentials, route availability, and destination permission.';
  console.error(message);
  process.exitCode = 1;
} finally {
  await dispatcher.close();
}

ProxyAgent receives a Basic token assembled in memory; the proxy URL contains no credential.

Use fetch and ProxyAgent from the same pinned Undici package; built-in Node fetch may expose a different Undici version.

Read the Node.js / Undici setup guide

Local mocks verify authentication, request shape, status failure, and timeout behavior. A real Databay credential and an authorized live preflight are still required to verify current route availability.

Product boundary

Buy the control depth, not the idea of a permanent address

Premium Residential adds state, city, ZIP, coordinate, and ASN controls beyond Flex. Choose Flex when country-or-continent targeting and a shorter sticky window are enough; choose Datacenter for a hosting-network origin or Mobile for a carrier-network origin. None of these shared products is a dedicated IP allocation.

Buyer FAQ

Questions buyers ask before ordering

Are these static ISP proxies?

No. Premium Residential is a shared rotating ISP-origin pool. It does not provide a static ISP allocation or reserve an address for one buyer.

What is the minimum residential order?

Residential orders start at 5 GB. The live catalogue panel shows the current per-GB rate, payable total, and validity before checkout.

Which targeting controls are available?

You can request one country, state, city, ZIP, coordinate, or ASN selector at a time. Every selection is subject to live route availability.

Does every request receive a fresh IP?

No. Rotation is tied to a new connection, and a fresh IP is not guaranteed for every connection or application request.

How long can a sticky session last?

You can request a sticky session for up to 120 minutes. Route continuity can end earlier, so applications should tolerate reconnection.

Which proxy protocols are supported?

The catalogue supports HTTP proxying, HTTPS CONNECT, and SOCKS5. Use the dashboard-generated credentials and current setup documentation.

Can I place a residential order below 5 GB?

No. The minimum residential order is 5 GB. The live entry panel shows the payable total and validity before checkout.

Review the current residential proxies order options

Choose a catalogue quantity only after the network origin, controls, validity, and limitations fit the workload.

Compare current plans