Pay as you go
5 GB+
Flexible mobile bandwidth
$3.55
per GB
Data valid 31 days
Review the published mobile carrier-network pool and source-dependent controls, then use the live rate cards for current price, quantities, order limits, and validity.
Current order options are shown on the live pricing page.
Choose flexible PAYG or prepay more data for a lower mobile rate.
Pay as you go
Flexible mobile bandwidth
$3.55
per GB
Data valid 31 days
Exclusive
High-volume mobile traffic
$3.15
per GB
Data valid 31 days
11% less than PAYGPrestige
Best rateMaximum bandwidth
$2.50
per GB
Data valid 31 days
30% less than PAYGIncluded with every option
Pay once · No auto-renewal
Custom volume
Custom volume pricing with dedicated support included.
Pay once. Top up when you are ready.
Cards, wire transfer and cryptocurrency payments. VAT invoices are available; listed prices exclude VAT.
A mobile proxy routes an application request through an IP address announced by a cellular carrier. The destination sees the carrier-network exit IP instead of your device's public IP. Databay provides access through one backconnect gateway, so you can change location and session behavior in the proxy username without maintaining a list of individual IPs.
gw.databay.co:8888 in an HTTP, HTTPS or SOCKS5-capable application and authenticate with your zone credentials.Many mobile carriers use carrier-grade NAT (CGNAT), which lets multiple subscribers share public IPv4 addresses. That can make a block based only on the public IP less precise because legitimate carrier customers may use the same address. RFC 6598 documents the shared address space used in CGN deployments.
CGNAT does not make proxy traffic invisible or guarantee access. A mobile proxy changes the network route only. Websites can still evaluate:
A mobile proxy does not automatically emulate a phone, change your user agent, supply cookies or make an automated client anonymous. Academic mobile-proxy measurement research also shows why “undetectable” is not a defensible promise.
Client
your code or browser
Databay gateway
gw.databay.co:8888
Mobile exit
carrier NAT address
Target
approved destination
credentials: USER-zone-mobile-countryCode-us:PASSWORD
Pool, country and session mode ride in the username flags, so the client configuration never changes — only the credential string does.
The product is a shared, rotating mobile pool billed by transferred data. Every self-serve plan uses the same core controls; larger one-time packages reduce the unit price.
| Mobile IP pool | 800K+ dynamic 4G/5G carrier-network IPs |
|---|---|
| Location control | One country or continent target at a time across 155+ countries; no city, ZIP, ASN or carrier selection |
| Session control | A new proxy connection may select an available exit, or a named session may request the same exit for up to 120 minutes; neither a fresh IP nor uninterrupted continuity is guaranteed |
| Protocols | HTTP proxying, HTTPS CONNECT, and SOCKS5 |
| Authentication | Username and password credentials through the Databay gateway |
| Concurrency | No fixed concurrent-connection limit applies in normal use; service safeguards may impose limits in abuse cases. |
| Access | Dashboard, REST API, integration documentation and technical support |
Current prices, orderable quantities, limits, totals, and validity are shown in the live rate card on this page. Exact terms are withheld when that catalogue snapshot is unavailable or expired.
Use 4G rotating proxies for independent connections and a sticky session when several requests must keep one network identity. “4G” describes the carrier-network route; “rotating” describes gateway session behavior. Both modes use Databay's same shared 4G/5G mobile pool and are selected through credentials rather than separate endpoints.
| Mode | IP behavior | Good fit | Important limit |
|---|---|---|---|
| Rotating | An available exit can be selected for a new connection | Independent authorized samples and localized monitoring | Persistent connections can reuse an exit; do not rotate inside a login or checkout flow |
| Sticky | A session ID requests the same exit for up to 120 minutes | Multi-step tests, authenticated sessions, repeat checks from one location | The IP can still change early if an upstream peer disconnects or availability changes |
A sticky session is not a dedicated or permanent IP. Reuse the same sessionId only for the workflow that needs continuity, and design the client to recover if the exit changes.
An LTE proxy routes through a mobile-carrier connection commonly marketed as 4G; LTE is not a separate proxy protocol. 4G/LTE and 5G describe the carrier connection behind an available exit. Databay exposes a combined 4G/5G mobile pool rather than a control for selecting one radio generation.
A “5G” label does not guarantee that an end-to-end proxy request will be faster. Destination response time, carrier congestion, radio conditions, route distance, the available peer and your own client all affect performance. Benchmark the actual country, target and request pattern instead of choosing on the generation name alone.
A mobile SOCKS5 proxy combines a carrier-network exit with the SOCKS5 transport supported by your client. These are separate controls: zone-mobile chooses the mobile pool, a country flag can request a location, SOCKS5 carries the client connection, and a session label requests sticky behavior. Omitting the session label lets the gateway select an available exit for a new connection.
| Requirement | Credential or client choice | What it does not promise |
|---|---|---|
| Mobile-carrier origin | Use zone-mobile | A particular carrier, SIM, device, radio generation or platform acceptance |
| SOCKS5 transport | Select SOCKS5 in a maintained client; use remote-DNS mode when the client offers it and the test requires it | Encryption beyond the destination protocol or a new IP for every request |
| Country route | Add a supported country code to the username | City, ZIP, ASN, coordinate or carrier precision on mobile |
| Rotation or continuity | Open a new connection without a session label, or reuse one named sticky session | Guaranteed uniqueness, permanence or uninterrupted continuity |
A SOCKS5 rotating proxy can use residential, datacenter or mobile exits; choose mobile only when the authorized workflow specifically needs a carrier-network origin. Persistent connections can reuse an exit, so verify the observed IP and connection behavior instead of assuming one request equals one rotation. See the HTTP vs SOCKS5 client tests for DNS, TLS and application-support differences.
Mobile exits make the most sense when the network origin itself matters to a lawful workflow. They are usually unnecessary for unprotected, high-volume endpoints where a faster and less expensive proxy type works.
Check localization, carrier-network behavior, regional content and mobile web flows from selected countries. A proxy supplies the network perspective; use a real device or emulator separately when the test also depends on device APIs or a mobile browser fingerprint.
Review mobile creatives, landing pages and regional campaign delivery from a carrier-network exit. Follow the advertising platform's policies and avoid generating billable impressions or clicks.
Compare public listings, prices, and brand mentions on sources that document or approve automated access. Respect rate limits, robots directives, privacy obligations, and applicable terms.
Maintain country-consistent sessions for accounts you own or are contracted to manage. An IP cannot prevent account challenges caused by cookies, device changes, rate, content or behavior. Prefer official platform tools and APIs whenever they cover the workflow.
Choose the least expensive network that reliably fits the authorized task. Mobile is a specialist option for carrier-origin workflows, not an automatic upgrade for every request.
For a deeper decision guide, compare residential and mobile proxies or datacenter and mobile proxies.
Current prices, orderable quantities, limits, totals, and validity are shown in the live rate card on this page. Exact terms are withheld when that catalogue snapshot is unavailable or expired.
The mobile pool currently advertises 155+ countries with country and continent targeting. Confirm the required country in the dashboard and validate it with a small order before committing a large workflow.
The public proxy locations directory covers Databay's residential, datacenter, and mobile origins. Its per-country IP totals are historical cross-origin counts, not mobile-only inventory, so this page intentionally does not present them as mobile supply. Buyers can compare the fresh Mobile configured-capability card, country or continent controls, and historical cross-origin count separately in the UK mobile proxy guide, Poland mobile proxy guide, and Spanish mobile proxies guide.
Current prices, orderable quantities, limits, totals, and validity are shown in the live rate card on this page. Exact terms are withheld when that catalogue snapshot is unavailable or expired.
Databay aggregates access to mobile pools managed by vetted upstream providers; it does not physically own every peer device. Exit availability, carrier routes and network performance can change. The Terms of Use explain sourcing, dynamic availability and the absence of a guarantee that any specific third-party destination will accept a proxy connection.
You can also review the Trust Center, live network status, Acceptable Use Policy and abuse-reporting process.
For Instagram-specific buying intent, the Instagram 4G proxy guide compares carrier and residential routes, session continuity, official Meta access paths, and stop conditions. The broader authorized social media management guide covers agency governance across platforms.
Replace USER and PASS with dashboard credentials. The default zone rotates; add a country or session parameter only when the workflow needs it. The cURL, Python and Node.js samples show how to rotate, select a country or keep a sticky session.
See the proxy integration documentation for current credential formats and API details. The following multi-profile browsers advertise HTTP or SOCKS5 proxy settings, but Databay does not guarantee every version; verify the vendor's current documentation and use profiles only for authorized account separation and QA:
Compatibility does not imply endorsement by those vendors.
# Rotating mobile exit
curl -x "http://USER-zone-mobile:PASS@gw.databay.co:8888" \
"https://api.ipify.org?format=json"
# Country targeting (United States)
curl -x "http://USER-zone-mobile-countryCode-us:PASS@gw.databay.co:8888" \
"https://api.ipify.org?format=json"
# Mobile SOCKS5 with proxy-side DNS in cURL
curl --proxy "socks5h://USER-zone-mobile:PASS@gw.databay.co:8888" \
"https://api.ipify.org?format=json"
# Sticky session (reuse the same session ID)
curl -x "http://USER-zone-mobile-sessionId-abc123:PASS@gw.databay.co:8888" \
"https://api.ipify.org?format=json"
import requests
username = "USER-zone-mobile-sessionId-abc123"
password = "PASS"
gateway = "gw.databay.co:8888"
proxy_url = f"http://{username}:{password}@{gateway}"
response = requests.get(
"https://api.ipify.org?format=json",
proxies={"http": proxy_url, "https": proxy_url},
timeout=30,
)
response.raise_for_status()
print(response.json())
const axios = require('axios');
const { HttpsProxyAgent } = require('https-proxy-agent');
const username = 'USER-zone-mobile';
const password = 'PASS';
const gateway = 'gw.databay.co:8888';
const proxyUrl = `http://${username}:${password}@${gateway}`;
const response = await axios.get(
'https://api.ipify.org?format=json',
{ httpsAgent: new HttpsProxyAgent(proxyUrl), timeout: 30000 },
);
console.log(response.data);
Spin up mobile proxies in minutes: dashboard, API and docs included.
Pricing, order minimums, and traffic validity vary by product.