Mobile proxies
Mobile proxies route your requests through real 3G/4G/5G devices on carrier networks. Target sites see them as ordinary phones on cellular data — the highest-trust signal on the public internet.
At a glance
Type code
mob
Delivery
Gateway, username-encoded
Endpoint
gate.helodata.io:7777
Billing
Pay per GB
Pool size
10M+ mobile IPs
Geo targeting
Country, ASN (carrier) — most countries do not expose state/city for mobile
Session length
Rotating (per connection) or sticky (up to 60 min)
Protocols
HTTP, HTTPS, SOCKS5
Authentication
User+password or IP whitelist
KYC required
Not by default (may be requested based on risk)
When to use mobile
Sites that score mobile-vs-desktop or carrier IP as a strong trust signal
Social platforms (DM flows, account integrity checks)
Apps and APIs that gate features behind carrier networks
Anti-bot bypass when residential is still being detected
Mobile is the slowest and most expensive of the helodata products. Use it where residential has already failed — not as a default.
Username grammar
state and city are accepted but, for most countries, the resulting pool is too small to be useful. Carrier targeting via asn is the primary geo refinement on mobile.
Full reference: Username format.
Five-second example
(That username pins KDDI in Japan.)
On this page
Quick start — first request in five minutes
Authentication — password vs IP whitelist
Endpoints & ports — host, port, TLS
Locations & carriers — country coverage and major carriers
Protocols — HTTP / HTTPS / SOCKS5
Sessions & rotation — sticky up to 60 minutes
ASN targeting — the most important mobile filter
Error definitions — what each status code means
Statistics — dashboards and traffic API
Last updated
Was this helpful?