Singapore Mobile Proxy

Point a browser profile at Singapore Mobile Proxy mobile proxies. Three steps, no plugin, no proxy-auth extension.

Singapore Mobile Proxy sells Singapore only: each port is one physical modem with one Singtel or M1 SIM, used by one customer, with its own HTTP and SOCKS5 port and a rotation link. Nothing about targeting rides in the credential. Measured on a live M1 test port, not read off a docs page.

https://singaporemobileproxy.com/

1. Get the credentials

In your Singapore Mobile Proxy dashboard, open the mobile product and copy the gateway host, the port, and the username and password. Everything below assumes those four values.

2. Build the proxy URL

One string, credentials included. Targeting and session options go in whichever half this provider puts them in - the table below says which.

http://<port login, e.g. proxy_xxxxxx>:<port password>@sg.veerlane.com:8221

3. Launch

Timezone, locale and WebRTC are derived from the exit address, so a US exit does not arrive with your own timezone attached.

await ab.launch({
  profile: 'acc-01',
  proxy: 'http://<port login, e.g. proxy_xxxxxx>:<port password>@sg.veerlane.com:8221',
})

launch(
    profile="acc-01",
    proxy="http://<port login, e.g. proxy_xxxxxx>:<port password>@sg.veerlane.com:8221",
)

Prefer not to run an account at all? Managed residential proxies are included on paid plans.

Parameters

Read off Singapore Mobile Proxy's own documentation on 2026-10-15. Ports and endpoints differ by plan and by zone, so where this table and your dashboard disagree, the dashboard is right.

Gateway	sg.veerlane.com on the port tested, and the same host in the API docs' example. Copy it from the dashboard line for your port rather than assuming it.
Ports	Every port gets its own pair: 8221 for HTTP and 5221 for SOCKS5 on the port tested (the API docs' example shows 8101 and 5101). They are not interchangeable - SOCKS5 on 8221 and HTTP on 5221 both failed.
Protocols	HTTP and SOCKS5 with the same login and password. Both were measured in AntiBrow and both reached the same exit. The vendor also offers SOCKS5 UDP and a per-port OpenVPN config; neither was tested here.
Options ride in	the line you bought, not the credential
Country targeting	Singapore only - the vendor sells no other country. The carrier, Singtel (AS45143) or M1 (AS4773), is picked at checkout and can be swapped later from the dashboard. The port tested was M1 and every exit resolved to *.unknown.m1.com.sg on AS4773 MobileOne, Singapore.
Sticky session	The port holds one mobile IP until something rotates it: the rotation link, the auto-rotate timer in the dashboard (minutes, 0 = off), or the modem reconnecting. Measured: the same exit, 119.56.16.17, came back in an HTTP profile, a SOCKS5 profile and the first profile relaunched. Calling the rotation link took 28.5 seconds to answer and the next request already left from 119.56.16.66, in the same /24.
Session length	One IP at a time per port; 30 simultaneous IPs means 30 ports. The rotation link refused a second call 46 seconds after the first with HTTP 429, saying the line rotates at most once every 4 minutes. The API docs give 5 minutes for their change-ip call and as the auto-rotate minimum.
Source	https://singaporemobileproxy.com/api-docs

Worth knowing

The dashboard prints each line as host:port:user:pass (sg.veerlane.com:8221:<login>:<password>). AntiBrow wants a URL, so rewrite it as http://<login>:<password>@sg.veerlane.com:8221, or socks5:// with the SOCKS5 port.
Measured on 2026-10-15 with AntiBrow, one profile per case: launch 6.4-10.8s, first page 1.0-1.6s, ipinfo.io 0.95-1.4s, over both HTTP and SOCKS5. Both exits were M1 mobile addresses in Singapore, not datacenter ones.
The browser timezone followed the exit on every run - Asia/Singapore, offset -480 - while the locale stayed at the profile's configured en-US. Timezone follows the exit; language does not, so set it on the profile if the site should see a local one.
No WebRTC leak on any run: the host candidate was an mDNS .local name and the srflx candidate carried the exit address itself, over HTTP and SOCKS5 alike. After the rotation the srflx candidate moved to the new address together with the page.
A wrong password on the HTTP port comes back as a clean 407 Proxy Authentication Required, so an auth mistake is easy to tell apart from a dead line.
Per the vendor's FAQ a port has one IP at a time and every connection through it leaves from that IP, so rotating moves every profile currently on the port at once - rotate between sessions, not under an open one. The dashboard also has an OS fingerprint setting on the port (Android, iOS, macOS, Windows variants, off by default); it was left off for these runs.
There is a free 24-hour trial with 10 GB on a dedicated port, no card required. Paid ports are $40 per 30 days with 200 GB, $50 with 500 GB or $85 with 1 TB, and $4 buys a single day, per the vendor's FAQ on 2026-10-15.