Skip to main content
Mobile proxies route through real mobile carrier networks. Format and targeting rules differ slightly from Residential: read the rules below.

​
Gateway

mobile.eclipseproxy.com

​
Ports

PortProtocol
5555HTTP
6666SOCKS5

​
Format

mobile.eclipseproxy.com:5555:emob_yourname:your_password_here_country-AO_city-luanda_region-tashkent
Or URL form: 
http://emob_yourname:your_password_here_country-AO_city-luanda_region-tashkent@mobile.eclipseproxy.com:5555

​
Username segments: note the _ separator

Mobile uses _ between segments (Residential uses -): 
emob_yourname                  ← mobile account prefix (note the emob_)
your_password_here          ← password
_country-AO                   ← country
_city-luanda                  ← city
_region-tashkent              ← region (can coexist with city)

​
Targeting rule: city AND region are both allowed

Unlike Residential (state OR city, not both), Mobile lets you target city AND region at the same time. This is because mobile network topology has both:
  • City: where the cell tower is
  • Region: carrier’s administrative area
_country-AO_city-luanda_region-tashkent   ← valid (mobile only)

​
Available targeting

TargetingSupported
Country✓
State / region✓ (_region-NAME)
City✓ (_city-NAME)
ISP✓ (_isp-NAME)
City + region together✓

​
Authentication

User:pass only. No IP whitelist option on Mobile.

​
Sessions

Sticky session syntax follows the _ separator pattern: 
emob_yourname:password_country-US_session-abc123_lifetime-30
Same _session-abc123 returns the same IP. Different session IDs return different IPs. Lifetime in minutes.

​
Rotating via API

Force a new IP by changing the session ID in the username. Same session ID returns the same IP.

​
Things to watch for

  • “What are mobile proxies, like an eSIM?”, Not exactly. They route through real mobile devices on cellular networks. To a target site, you appear as a normal mobile user on AT&T / Vodafone / etc.
  • “Why are my mobile proxies formatted emob_user:pass_country-X@host:port and not user:pass@ip:port?”, That’s our mobile format. The geo and session settings live in the username, joined with _.
  • “Mobile proxy not working in Octo / Potatso / AdsPower”: set port explicitly (5555 for HTTP, 6666 for SOCKS5). Some tools default to a different port.
  • “Can I use IP whitelist?”, No on Mobile. Use credentials.