Mobile-web experience checks
Review public or owned web experiences from one supported country or continent carrier-network context at a time.
Mobile · shared carrier-network pool
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 plansCurrent catalogue
The smallest current bandwidth order, shown before checkout.
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
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.
Review public or owned web experiences from one supported country or continent carrier-network context at a time.
Test services you control when carrier-network origin matters but a particular device or mobile operator does not.
Collect allowed public information through a carrier-network route while respecting access rules, rate limits, and destination terms.
Validate how an application reconnects when a rotating route changes or a requested sticky session ends early.
Product decision
Start with network origin, then reconcile targeting, session behaviour, and the complete entry order. No product is presented as a universal winner.
| Network product | Entry order | Route contract | Decision boundary |
|---|---|---|---|
Residential ProxiesISP-origin networkPricing and checkout | Entry order5 GB · $13.75 totalBandwidth order, not an IP lease | Route contract
| Decision boundary Granular ISP-origin targeting matters more than carrier-network origin. Shared and rotating; one selector at a time; 5 GB minimum order. |
Residential FlexResidential networkPricing and checkout | Entry order25 GB · $13.75 totalBandwidth order, not an IP lease | Route contract
| Decision boundary Country-or-continent residential targeting is enough. Less granular controls and a 30-minute maximum sticky request. |
Mobile ProxiesCarrier-network originPricing and checkout | Entry order5 GB · $17.75 totalBandwidth order, not an IP lease | Route contract
| 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. |
Datacenter ProxiesHosting-network originPricing and checkout | Entry order10 GB · $12.50 totalBandwidth order, not an IP lease | Route contract
| Decision boundary A shared hosting-network origin is acceptable. Not residential, mobile, dedicated, or static IP space. |
Connection check
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
gw.databay.co:8888ProtocolsHTTP proxying, HTTPS CONNECT, and SOCKS5USERNAME-zone-mobileSticky username fixtureUSERNAME-zone-mobile-sessionId-qa%2Dsession%2D01Keep 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.
: "${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 guideimport 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 guideimport { 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 guideLocal 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
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
No. Mobile is access to a shared rotating carrier-network pool. It does not assign a dedicated device, SIM, modem, or exclusive IP.
No. The current product supports one country or continent selector at a time; it does not expose carrier or radio-generation selection.
Mobile orders start at 5 GB. The live catalogue panel shows the current per-GB rate, payable total, and validity.
No. Rotation is tied to a new connection, and a fresh IP is not guaranteed for every connection or application request.
You can request up to 120 minutes. Continuity can end earlier, so applications should tolerate a route change.
Mobile supports HTTP proxying, HTTPS CONNECT, and SOCKS5 with dashboard-generated credentials.
No. The minimum mobile order is 5 GB. The live entry panel shows the payable total and validity before checkout.
Choose a catalogue quantity only after the network origin, controls, validity, and limitations fit the workload.