Mobile · shared carrier-network pool

Carrier-network routes with honest product boundaries

Choose Mobile when carrier-network origin is a real workload requirement. The product is a shared rotating bandwidth pool, not a device, SIM, modem, dedicated IP, or selectable carrier, and orders start at 5 GB.

Review current plans

Current catalogue

5 GB minimum

The smallest current bandwidth order, shown before checkout.

Minimum order
5 GB
Payable total
$17.75
Unit rate
$3.55/GB
Traffic validity
31 days

Purchase unit: Bandwidth, not an IP lease.

The lowest listed rate is $2.50/GB only at 512 GB ($1,280.00 total).

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

Workload fit

Choose Mobile for carrier origin, not device ownership

This product fits authorized checks where a carrier-network route matters and country-or-continent control is enough. It does not fit workflows that require a specific carrier, radio generation, handset, SIM, modem, or exclusive address.

  1. Mobile-web experience checks

    Review public or owned web experiences from one supported country or continent carrier-network context at a time.

  2. Authorized app-service validation

    Test services you control when carrier-network origin matters but a particular device or mobile operator does not.

  3. Permitted public-data review

    Collect allowed public information through a carrier-network route while respecting access rules, rate limits, and destination terms.

  4. Session-recovery testing

    Validate how an application reconnects when a rotating route changes or a requested sticky session ends early.

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 matters more than carrier-network origin.

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.

Less granular controls 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

Carrier-network origin is required without a specific carrier or device requirement.

No carrier, radio-generation, device, SIM, modem, or exclusive IP 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 origin is acceptable.

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

Connection check

Test the carrier route and the reconnect path

Create dashboard credentials, apply one country or continent selector, and choose rotating or requested sticky behavior. Verify a destination you own or are authorized to test before scaling traffic.

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-mobileSticky username fixtureUSERNAME-zone-mobile-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-mobile'

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-mobile", 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-mobile';
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

Pay for carrier-network origin only when the workload needs it

Mobile differs by network origin, not by an ownership claim over hardware or an address. Premium Residential offers finer geographic and ASN controls from an ISP-origin pool; Flex offers broader residential controls; Datacenter uses a hosting-network pool. All four products are shared and bandwidth-billed.

Buyer FAQ

Questions buyers ask before ordering

Do I receive a dedicated phone, SIM, or modem?

No. Mobile is access to a shared rotating carrier-network pool. It does not assign a dedicated device, SIM, modem, or exclusive IP.

Can I select a carrier or mobile generation?

No. The current product supports one country or continent selector at a time; it does not expose carrier or radio-generation selection.

What is the minimum mobile order?

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

Will every request use a fresh mobile 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 mobile session last?

You can request up to 120 minutes. Continuity can end earlier, so applications should tolerate a route change.

Which proxy protocols are available?

Mobile supports HTTP proxying, HTTPS CONNECT, and SOCKS5 with dashboard-generated credentials.

Can I place a mobile order below 5 GB?

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

Review the current mobile proxies order options

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

Compare current plans