The short answer
- 1 NodeMaven Long mobile sessions Visit site
- 2 Decodo (ex Smartproxy) Broad mobile coverage Visit site
- 3 AnyIP.io Carrier-aware sticky sessions Visit site
16 best proxies for Android, compared
| # | Provider | Fit | From | Readers | Protocols | Links |
|---|---|---|---|---|---|---|
| 1 | 4.7/5 | $2.20 / GB | 88% | SOCKS5, HTTP, HTTPS | ||
|
Record lists SOCKS5, 250K mobile IPs, 190+ countries and sticky sessions up to 24 hours for mobile-first Android setups. Good for this job
Watch out
|
||||||
| 2 | 4.6/5 | $0.08 / GB | 100% | HTTP(S), SOCKS5 | ||
|
HTTP(S)/SOCKS5, mobile proxies from $2.25/GB, 195+ locations and 30-minute sticky sessions fit Android app and carrier use. Good for this job
Watch out
|
||||||
| 3 | 4.5/5 | $2 / GB | 80% | HTTPS, SOCKS5 | ||
|
SOCKS5, mobile and residential on one plan, Smart Sessions keep the same carrier and area, 7-day sticky, but only 38+ countries. Good for this job
Watch out
|
||||||
| 4 | 4.5/5 | $0.35 / GB | 90% | HTTP, HTTPS, SOCKS5, HTTP/2 | ||
|
SOCKS5, 4M+ mobile IPs across 170+ countries, mobile country/city/carrier targeting, though dedicated mobile is 5+ countries. Good for this job
Watch out
|
||||||
| 5 | 4.4/5 | $0.63 / GB | 86% | SOCKS5, HTTP, HTTPS | ||
|
SOCKS5, mobile proxies, 195 countries and rotating traffic from $1.00/GB; mobile 120 GB tier is $2.07/GB. Good for this job
Watch out
|
||||||
| 6 | 4.3/5 | $0.30 / GB | 96% | HTTP, HTTPS, SOCKS5 | ||
|
SOCKS5, mobile proxies in 20+ countries on Vodafone, T-Mobile and Orange with 5G/4G/LTE and IP whitelisting. Good for this job
Watch out
|
||||||
| 7 | 4.2/5 | ₽490 / day | 83% | SOCKS5, HTTP | ||
|
SOCKS5 and HTTP mobile proxies with unlimited traffic, 53 provider countries and 1-day minimum rental; coverage is narrower than global pools. Good for this job
Watch out
|
||||||
| 8 | 3.9/5 | $0.40 / GB | 100% | — | ||
|
Mobile proxies with 195 locations and $7.5/GB entry, but the record does not list SOCKS5 support, which Android per-app tools expect. Good for this job
Watch out
|
||||||
| 9 | 3.8/5 | $0.50 / GB | 88% | HTTP(S) | ||
|
2M+ mobile IPs and 120+ carriers across 195+ countries, but protocol support is listed as HTTP(S) only, with no SOCKS5. Good for this job
Watch out
|
||||||
| 10 | 3.6/5 | $0.02 / month | 100% | — | ||
|
HTTP/SOCKS5 endpoints and IP authorisation suit Android helper apps, and a free 10-proxy plan exists, but there are no mobile addresses. Good for this job
Watch out
|
||||||
| 11 | 3.4/5 | $0.06 / GB | 100% | HTTP, HTTPS, SOCKS5 | ||
|
HTTP/HTTPS/SOCKS5 and 200+ residential countries, but the record lists no mobile proxy product for carrier-style Android use. Good for this job
Watch out
|
||||||
| 12 | 3.3/5 | $5 / proxy | 85% | — | ||
|
Mobile proxies at $15/proxy across 150+ locations, but no SOCKS5 or phone-friendly authentication is stated in the record. Good for this job
Watch out
|
||||||
| 13 | 3.2/5 | $1 | 82% | — | ||
|
SOCKS5 and a mobile product family, but the record gives no mobile country count or pool size, and a $10 minimum order applies. Good for this job
Watch out
|
||||||
| 14 | 3.1/5 | — | 81% | SOCKS5, HTTP, HTTPS | ||
|
SOCKS5 and 80M+ residential IPs across 190+ regions, but no mobile product and no free trial are listed. Good for this job
Watch out
|
||||||
| 15 | 3.0/5 | $2 / GB | 88% | SOCKS4, SOCKS5, HTTP, HTTPS | ||
|
SOCKS5 and sticky IPs up to 72 hours, but mobile coverage is only Poland and Ukraine, too narrow for most Android country needs. Good for this job
Watch out
|
||||||
| 16 | 2.8/5 | $2 | 82% | HTTP/S | ||
|
Mobile rotation with 30-minute sticky sessions, but SOCKS5 is B2B-only and country coverage is uncounted, weakening Android app use. Good for this job
Watch out
|
||||||
Ordered by how well each provider fits this job, from the figures the providers publish, our review scores and reader votes — see our methodology.
How Android handles proxies
Android has no system-wide proxy switch the way a desktop does. There is no single setting that pushes every byte from every app through one address. What exists instead is a proxy field attached to each saved Wi-Fi network, plus a VPN service API that an app can use to intercept traffic lower down the stack. Everything awkward about proxies on Android follows from those two facts.
The Wi-Fi field is read by the platform's proxy selector. Apps built on OkHttp, HttpURLConnection or a standard WebView pick it up without any code of their own, provided the developer has not disabled proxy use. Apps with a bundled networking library, a games engine, or a hard-coded connection pool often never consult it. So the same phone can be proxied in one app and completely direct in another, and nothing on screen tells you which is which.
The second route is a VPN client. Android's VPN service API lets an app claim the device's routing table, which means it captures traffic from apps that ignore the Wi-Fi proxy entirely, and it keeps working when the phone moves from Wi-Fi to cellular. This is why nearly every so-called android proxy app is really a VPN client with a proxy sitting behind it: the VPN part is what makes the coverage complete.
What Android never does is proxy mobile data at the operating system level. There is no proxy field for a carrier connection. If you set a Wi-Fi proxy and then walk out of range, the phone hands the connection to the carrier and the proxy is gone — silently, often mid-request.
System-wide against per-app routing
System-wide means one address for everything the device sends. On Android that is realistically achieved only with a VPN-based client, because the Wi-Fi field is per-network and leaky by design. The advantage is coverage; the disadvantage is that you cannot exempt anything, including the banking app you would rather not route through a rented address.
Per-app routing is the opposite trade. Android has supported per-app VPN split tunnelling since version 5, exposed in the VPN client's own settings as an allow-list or a block-list of applications. If your tool offers it, that is the cleanest way to send one app through a proxy and leave the rest of the phone alone. It requires no root.
Rooted devices have a third option: redirecting traffic per UID with iptables or nftables, which catches even apps that build raw sockets. It is more complete and considerably more fragile — a mis-typed rule can blackhole the phone's connectivity, and over-the-air updates occasionally reset the rule set.
Choose per-app when the job is testing one application, checking what a specific app sees, or keeping a work profile separate. Choose system-wide when the job is the whole device: app store region checks, ad verification across several apps, or anything where you cannot enumerate what will make a request.
Why the Wi-Fi setting cannot use a password
The manual proxy screen in Android settings takes a hostname, a port and a bypass list. That is the entire form. There is no field for a username and no field for a password, because the stored value is a bare host-and-port pair attached to the network configuration, not a credential store.
The practical consequence is that the built-in setting only works with proxies that do not ask for credentials: open proxies, or endpoints that authenticate you by source IP because you have registered your address with the provider. Most paid pools authenticate with a username and password, which is exactly why the criteria for this page put weight on authentication a phone can actually perform.
If you paste credentials into the hostname field, nothing useful happens — the phone tries to resolve a string like user:pass@host as a hostname and fails. If the proxy does demand authentication and you have no way to supply it, every request returns 407 Proxy Authentication Required, and the app usually reports it as a generic network error.
The workarounds are: put the credentials in a helper or VPN app that supports them, ask the provider for an IP-allowlisted endpoint, or use a proxy that is bound to your address by token in the URL — which most Android system apps will not accept either. There is no fourth option that keeps you inside the stock settings screen.
How to set up a proxy on Android, step by step
For an HTTP proxy on a Wi-Fi network with no authentication:
- Open Settings, then Network & internet, then Internet (older builds label this Wi-Fi).
- Tap the gear or long-press the network you are joined to and choose Modify network.
- Expand Advanced options and change Proxy from None to Manual.
- Enter the hostname and port exactly as the provider gives them. Leave the PAC option alone unless you have a PAC URL.
- Fill the bypass list with anything that should stay direct, for example
localhost,127.0.0.1,*.local. - Save, then toggle Wi-Fi off and on so apps that cached the old configuration reconnect.
This setting is tied to that one network. Join a different SSID and you are direct again.
For SOCKS5, the stock settings screen is not the tool: there is no SOCKS option in the Wi-Fi proxy form. Use a client that speaks SOCKS5 and routes through the VPN service, or push a global setting over ADB from a development machine:
adb shell settings put global http_proxy 192.0.2.10:1080
That value is read by the same proxy selector as the Wi-Fi field, so the same apps honour it and the same apps ignore it. To clear it:
adb shell settings put global http_proxy :0
Some apps only re-read the setting after a restart. On an emulator, the host machine's loopback is reachable at 10.0.2.2, which is useful when the proxy is running on your laptop.
After configuring either route, confirm what the outside world sees with what is my IP, then check the endpoint is alive and not transparently forwarding your real address using the proxy checker. A proxy that responds but reports your home address is worse than no proxy, because you will trust it.
Which address type suits a phone
Datacentre addresses are cheap and fast and immediately identifiable as not-a-phone. If the app you are using applies any risk scoring, whether that is a bank, a retailer or a streaming service, a datacentre range is the first thing that gets flagged. They are fine for fetching public pages and useless for anything that expects a real device.
Residential addresses look like home broadband. They are the default for web work, but on a phone they are a mismatch: the app sees a handset User-Agent and a screen size arriving from a fixed line, and some apps cross-check the carrier against the connection type.
Mobile carrier addresses are the configuration that matches what Android apps expect. They sit behind carrier-grade NAT, which means many subscribers share one visible address, and that shared reputation is the reason mobile ranges survive longer than any other type — blocking them breaks real customers. The costs are real: mobile is the most expensive category, latency rises with radio state, and sessions can drop when the device changes cell.
For app-store region checks, regional content testing and anything that depends on being treated as a normal handset, mobile is the honest choice. For plain page fetching, a datacentre or residential address will do the job for a fraction of the cost. The trade-off is not subtle and no provider's marketing removes it.
Free proxies and what they see
An HTTP proxy terminates your connection and opens its own to the destination. Anything sent over plain HTTP — full URLs, cookies, form bodies, session tokens — is visible to whoever runs it. HTTPS limits that to the hostname and the TLS server name, not the contents, unless the operator installs a certificate and intercepts. On Android 7 and later, apps targeting the modern API level do not trust user-installed certificate authorities by default, so interception is harder than it once was, but browsers and older apps remain exposed.
Free lists are also unreliable in a duller way: endpoints die within hours, throughput is shared with everyone else using the same address, and a meaningful share of entries are honeypots or injection points that rewrite responses. None of that is a reason to avoid them entirely — a disposable address is genuinely useful for checking how a page renders in another country.
Treat a free proxy as public. Never log into anything that matters through one, never send a card number, and assume every request is recorded. Our live free SOCKS5 list is checked continuously precisely because an unverified list is mostly dead entries. If you need a stable address for a long session, a paid pool is the only realistic option, and the provider reviews cover what each one actually sells.
Mistakes that leak traffic around the proxy
Most people who think they are proxied and are not have hit one of the following.
- The Wi-Fi drop. The phone loses the network, cellular takes over, and the proxy vanishes without a notification. Anything the app retries goes out direct from the carrier address. If you need continuity, a VPN client with a kill switch is the only reliable answer.
- DNS outside the tunnel. A SOCKS5 proxy resolves names itself only if the client asks it to —
socks5hrather thansocks5in most tools. Get this wrong and the hostname lookup goes to your carrier's resolver while the content goes through the proxy. - IPv6. An IPv4-only proxy configuration does nothing about an IPv6-capable network. Requests over IPv6 route around the proxy entirely.
- Apps with their own network stack. Push notifications, some social apps and most games never consult the proxy selector. They will keep talking to the network directly and you will not see it in the app's UI.
- Split tunnelling set too wide. A per-app list that includes the browser but not the app you actually care about gives a false sense of coverage.
- Battery optimisation. Android suspends background VPN apps aggressively. If the client is not exempted from battery optimisation, the tunnel dies when the screen goes off and traffic falls back to the raw connection.
- Captive portals. Hotel and airport networks rewrite traffic until you sign in. The proxy appears broken, you disable it, and then you forget to re-enable it.
Check the exit address from inside the app that matters, not from a browser tab. That is the only test that tells you whether the app you are worried about is actually using the proxy.
What to look for
- SOCKS5 support
- Android's per-app proxy tools and most tunnelling apps expect SOCKS5 rather than an HTTP proxy.
- Authentication that a phone can do
- Android's built-in Wi-Fi proxy setting cannot send a username and password, which rules out most paid pools without a helper app.
- Mobile addresses
- An Android device on a carrier address is the configuration that matches what the apps expect.
- Stability on a moving connection
- A phone changes network, and a proxy that does not survive the switch is worse than none.
- Country coverage
- App availability and regional content are the usual reasons for doing this at all.
Free SOCKS5 proxies, live right now
These are from our own list, checked around the clock. They are free, which also means they are shared, short-lived and wrong for anything that holds a login — but they are the cheapest way to see whether a proxy fixes your problem at all before you pay for one.
| Ip Address:Port | Type | Country | Anonymity | Speed | Uptime | Response | Updated |
|---|---|---|---|---|---|---|---|
| SOCKS5 |
United States
|
Elite | 0.09% |
2%
|
2830.37 ms | 2s ago | |
| SOCKS5 |
United States
|
Elite | 0.07% |
38%
|
4462.88 ms | 2s ago | |
| SOCKS5 |
United States
|
Elite | 0.08% |
21%
|
2945.48 ms | 2s ago | |
| SOCKS5 |
United States
|
Elite | 0.08% |
13%
|
2899.66 ms | 2s ago | |
| SOCKS5 |
United States
|
Elite | 0.05% |
17%
|
4433.23 ms | 2s ago | |
| SOCKS5 |
United States
|
Elite | 0.06% |
16%
|
4069.15 ms | 2s ago | |
| SOCKS5 |
United States
|
Elite | 0.06% |
16%
|
4363.48 ms | 2s ago | |
| SOCKS5 |
United States
|
Elite | 0.08% |
19%
|
3067.57 ms | 2s ago | |
| SOCKS5 |
United States
|
Elite | 0.08% |
25%
|
2747.72 ms | 2s ago | |
| SOCKS5 |
United States
|
Elite | 0.09% |
13%
|
2861.44 ms | 2s ago |
Every provider, in order
1. NodeMaven — Long mobile sessions
4.7 / 5 for this job · from $2.20 / GB
NodeMaven sits first because of one number: sticky sessions quoted at up to 24 hours, with unlimited concurrent sessions. Android apps that hold a session open across a network change are the reason that matters. When the handset drops Wi-Fi and picks up cellular, a short-lived session hands the app a new address and whatever it was doing usually breaks. A mobile address held for a day does not.
The protocol and location side is present too. SOCKS5 is supported alongside HTTP and HTTPS, which is what per-app proxy tools and tunnelling apps on Android expect, and geo-targeting reaches 190+ countries across 195+ locations. Residential, mobile and ISP proxies sit under one account, so you can move between address types without a second subscription. The provider quotes average mobile speed at under 0.6 seconds and a 99.99% uptime figure for the service generally.
The catch is cost and the way you get in. There is no free trial: $3.50 buys a 750 MB demo, and a third-party write-up says the free-trial route is limited to registered companies that pass KYC. Per-GB billing gets expensive once long mobile sessions start consuming traffic, and mobile pool size is reported differently depending on who you ask — 250K from the provider, 295K+ in third-party records. Smaller locations are reported as uneven in depth, and refunds are pro-rated rather than full.
Key features
- SOCKS5, HTTP and HTTPS support
- Sticky sessions quoted at up to 24 hours with unlimited concurrent sessions
- 250K mobile IPs per the provider; 295K+ in third-party records
- 190+ countries for geo-targeting, ZIP level claimed by the provider
- No free trial; $3.50 for a 750 MB demo
- Pro-rated refunds rather than full
Best suited for: Android work that needs one mobile address held for hours rather than minutes
2. Decodo (ex Smartproxy) — Broad mobile coverage
4.6 / 5 for this job · from $0.08 / GB
Smartproxy — now trading as Decodo — earns second place on the depth of its location list rather than on session length. Its 195+ locations and continent, country, state, city, ZIP and ASN targeting are the widest set on this page, and app availability checks usually live or die on getting the right country. Mobile proxies are sold from $2.25/GB, and HTTP(S) and SOCKS5 are both supported, so a client that will only speak SOCKS5 still works.
The residential side is the part with published numbers: 115M+ IPs from a 125M+ total pool, per the provider, with country examples such as 16M+ in the United States, 11M+ in India and 5M+ in the United Kingdom. Response time for residential is quoted under 0.5 seconds with a 99.92% success rate. There is also a genuine free entry point — a 3-day, 100 MB trial — and a 14-day money-back option on paid plans.
Two things to weigh. Sticky sessions run for up to 30 minutes, which is short for an Android app holding a logged-in state across a commute. And the trial and the refund are mutually exclusive: use the trial and refund eligibility goes. Refunds are first-purchase only, must be requested inside 14 days, and are capped well below the full amount. Pay-as-you-go is wallet-only, one gigabyte at a time, and cannot be mixed with a subscription. Note also that Decodo.com is the official site; Smartproxy.org is an impersonator with no connection to the company.
Key features
- 195+ locations; continent, country, state, city, ZIP and ASN targeting
- HTTP(S) and SOCKS5 support
- Sticky sessions held for up to 30 minutes
- Mobile proxies from $2.25/GB
- 3-day, 100 MB free trial; 14-day money-back on paid plans, mutually exclusive
- Residential success rate quoted at 99.92%
Best suited for: country and city-level app availability checks where breadth of locations beats session length
3. AnyIP.io — Carrier-aware sticky sessions
4.5 / 5 for this job · from $2 / GB
AnyIP.io is third because of Smart Sessions. A Smart Session keeps the address inside the same carrier and the same area, and sticky sessions can run for up to 7 days. On a phone that changes network through the day, that is the behaviour you want: the app sees a mobile address that looks like it belongs to one subscriber in one place, not a rotating pool. Filtering reaches country, ISP, region and precise GPS coordinates, which is more than most of the list offers for regional app checks.
Another point in its favour for Android specifically: residential and mobile proxies come on one plan at one price, with only bandwidth metered. You do not have to decide in advance whether a target wants a carrier address. Unlimited rotation and unlimited concurrent requests are included rather than charged as extras, IP collision prevention and change-IP-by-link are there, and unused data rolls over. Authentication is username and password or IP whitelist — worth noting because Android's built-in Wi-Fi proxy field cannot send credentials, so you will need a helper app or whitelisting.
The weaknesses are real. Coverage is only 38+ countries, which is thin if the job is app availability across many regions. The advertised $2/GB is the Enterprise rate; the Micro plan is $25 for 5 GB with extra traffic at $5/GB, and Basic is $4/GB extra. There is no free trial — Micro is the paid entry point — and crypto payments fall outside the refund policy, which covers card purchases only.
Key features
- Sticky sessions up to 7 days; Smart Sessions stay within the same carrier and area
- Filtering by country, ISP, region and precise GPS coordinates
- Residential and mobile on one plan, bandwidth the only meter
- HTTPS and SOCKS5; username/password or IP whitelist authentication
- 38+ countries only
- $2/GB is the Enterprise rate; Micro is $25 for 5 GB
Best suited for: carrier-consistent mobile sessions with GPS-level targeting in a limited country set
4. ProxyEmpire — Carrier-level mobile targeting
4.5 / 5 for this job · from $0.35 / GB
ProxyEmpire is the card for anyone whose Android target cares which carrier the address belongs to. Mobile targeting runs to country, city and carrier, across 170+ countries with 4M+ rotating mobile IPs on the provider's figures. That is a wider mobile country list than most here, and the carrier layer is the part that matters when an app checks the network operator as part of its risk score.
Session control is flexible in the way a phone-based workflow needs: time-based, session-based, or a new IP on request. Bandwidth rolls over, and unused gigabytes are stated never to expire — useful when a test period is interrupted and you come back to it weeks later. Protocols are HTTP, HTTPS, SOCKS5 and HTTP/2. Plans are prepaid with no contracts or monthly minimums, and there is a $1.97 trial with 150 MB that does not auto-convert into a subscription.
The catches are coverage shape and the trial's limits. Dedicated mobile reaches only 5+ countries and 50+ locations, and drops to country, city and carrier targeting; the 170+ figure is the rotating pool. The $1.97 trial excludes static ISP and datacenter, and covers unlimited residential only on request. EMPIRE50 does not apply to static, unlimited bandwidth or other flat-rate plans, and unlimited bandwidth starts at $200/day with no rollover. Coverage is uneven across products — 62 datacenter countries and 24 static ISP countries.
Key features
- Mobile targeting by country, city and carrier
- 4M+ rotating mobile IPs across 170+ countries, per the provider
- HTTP, HTTPS, SOCKS5 and HTTP/2
- Rollover bandwidth that the provider says never expires
- $1.97 trial with 150 MB, no auto-conversion
- Dedicated mobile limited to 5+ countries and 50+ locations
Best suited for: Android checks that depend on which carrier network the address belongs to
5. Floppydata — Cheap mobile bandwidth
4.4 / 5 for this job · from $0.63 / GB
Floppydata is fifth because it is the cheapest way onto a mobile address on this page. Rotating traffic starts at $1.00/GB and covers residential, mobile and datacenter on the same meter, and the published bulk tiers bring mobile down to $2.07/GB at 120 GB and $2.36/GB at 96 GB. For long-running Android sessions that burn bandwidth steadily, that arithmetic is the whole argument.
The rest of the setup is workable. SOCKS5, HTTP and HTTPS are supported; targeting runs to country, city, ASN and IP type across 190+ locations; and static residential and ISP options sit under the same account if you later need a fixed address for a login. There is a 100 MB free trial for each of residential, datacenter and mobile, cards go through Stripe and 50+ cryptocurrencies are accepted, and the client API is reachable at api.floppydata.net with an X-Api-Key header. A 95% clean IP rate is claimed.
The awkward parts. The business dates from April 2024, so the track record is short, and documentation is thin for anything beyond standard rotation logic. There is no phone support — live chat, email and Telegram only. The 100 MB trial is a connectivity check, not a load test, and figures like 99.99% uptime and sub-0.3-second responses are the provider's own claims with no independent test behind them.
Key features
- Rotating traffic from $1.00/GB covering residential, mobile and datacenter
- Mobile at $2.07/GB on the 120 GB tier, $2.36/GB at 96 GB
- SOCKS5, HTTP and HTTPS; targeting by country, city, ASN and IP type
- 100 MB free trial for each of residential, datacenter and mobile
- No phone support; live chat, email and Telegram only
- Founded April 2024; provider-claimed uptime and response figures
Best suited for: high-volume Android mobile sessions where bandwidth cost outweighs a short track record
6. Proxy-Seller — Named carrier mobile IPs
4.3 / 5 for this job · from $0.30 / GB
Proxy-Seller comes last of the six for Android specifically, and the reason is visible in its own figures: mobile coverage reaches 20+ countries against 220+ residential locations. If the job needs a carrier address in a specific country outside that short list, this is not the provider. If it needs one of the named networks, the picture changes.
Those networks are Vodafone, T-Mobile and Orange, on 5G, 4G and LTE. For app testing that hinges on a recognisable operator, that specificity is worth more than a longer list of unnamed carriers. HTTP, HTTPS and SOCKS5 are all supported, so per-app proxy tools on Android have something to talk to, and the residential pool of 47M+ rotating IPs across 220+ locations covers the country-level app availability work that mobile cannot. Entry pricing is published per unit: $0.30/GB residential, $0.49/IP IPv4, $0.02/IP IPv6, mobile from $10/IP.
Compliance is unusually well documented for a provider at this price — ISO/IEC 27001:2022 and ISO 9001:2015, GDPR, CCPA and ePrivacy stated, DPA/SCC readiness and an EWDCI trust seal. Uptime is quoted at 99.7% and connection success at 99.5%+, both the provider's own numbers with no independent test cited. Support is advertised as 24/7 human with a 30-second median reply.
Key features
- Mobile in 20+ countries only, against 220+ residential locations
- Named carriers: Vodafone, T-Mobile, Orange on 5G/4G/LTE
- HTTP, HTTPS and SOCKS5 support
- 47M+ rotating residential IPs across 220+ locations
- Mobile from $10/IP; residential from $0.30/GB
- Uptime 99.7% and success rate 99.5%+, provider figures
Best suited for: Android testing against a named carrier network rather than a long country list
7. MobileProxy.Space — Unlimited mobile traffic
4.2 / 5 for this job · from ₽490 / day
Seventh, and the highest entry in this table that sells mobile addresses on a flat rental rate rather than by the gigabyte. That matters more on Android than on a desktop: a phone left on a proxy keeps syncing in the background, and a metered pool charges for every megabyte of it. MobileProxy.Space bills mobile plans by rental period with unlimited traffic, with a one-day minimum rental, so a short test costs a day's ₽490 rather than a top-up.
The Android-specific fit is in the authorisation. The record lists login and password or authorisation by main IP. The second option is the one that survives Android's stock Wi-Fi proxy dialog, which cannot send a username and password and has no way to pass credentials to a per-app tunnel. SOCKS5 is listed alongside HTTP, so tools that expect SOCKS5 rather than an HTTP proxy have something to connect to. Rotation runs on a timer or by hitting an API link, with an IP change quoted at 2–7 seconds, and up to 250 simultaneous connections are allowed per mobile proxy.
The catch is the numbers, and there are several. Third-party records and the provider's own disagree on pool size, country count, operator count and server count — 30+ countries against 53, 130+ operators against 223 — and trial length is given as two hours in one record and three by the provider. Third-party write-ups call the prices relatively high, and there are reports of laggy proxies, geographical location problems and late-night maintenance. The declared performance is not quick either: 348 ms average ping and 10 Mbps down, with the provider itself noting that a remote device runs at up to about 4 Mb/s. Nothing in the record says how a session survives the phone switching between Wi-Fi and a carrier.
Key features
- Mobile plans billed by rental period with unlimited traffic, not per gigabyte
- SOCKS5 and HTTP listed as supported protocols
- Authorisation by main IP or by login and password
- Minimum rental period of one day
- IP rotation on a timer or via API link; quoted IP change time 2–7 seconds
- Up to 250 simultaneous connections per mobile proxy
Best suited for: keeping an Android device on a carrier address all day without metered billing, once you have worked out which country figure to trust
8. Oxylabs.io — High-coverage mobile pool
3.9 / 5 for this job · from $0.40 / GB
Eighth, and the widest country footprint in this table: the provider claims 177M+ IPs in total, 175M+ of them residential, across 195 locations. When the reason you are proxying a phone at all is app availability or regional content, that coverage is the argument. Mobile traffic is priced at $7.5/GB on the free welcome credits and Starter, $6.67/GB on Basic, $5/GB on Flexible and $3.5/GB at enterprise level, with the rates published per tier so a budget can be modelled before anyone has to talk to sales.
On a phone the billing unit is the awkward part. Metered mobile traffic punishes an Android device that idles with background sync and push notifications, and the free entry point is $5 in welcome credits — the record puts that at up to 0.7 GB of mobile traffic, which a single app session can eat. The cheapest paid plan is $30/month, so there is no small commitment that is not also a real one. VAT may apply on Starter, Basic and Flexible, and Bitcoin is not accepted.
Two other things are worth checking before you buy for this job. The record lists no protocol detail for the proxy products, so SOCKS5 support is not something that can be assumed from these pages; if your per-app tooling expects SOCKS5 rather than HTTP, confirm it first. And the compliance story, which is the provider's strongest card elsewhere — ISO/IEC 27001:2022 and SOC 2 Type II — is scoped per product, not company-wide, with the certificates naming specific products rather than the whole catalogue.
Key features
- 177M+ IPs in total, 175M+ residential, across 195 locations, per the provider
- Mobile proxies from $7.5/GB on Starter down to $3.5/GB at enterprise level
- $5 welcome credits, quoted as up to 0.7 GB of mobile traffic
- Published per-tier rates for every product
- ISO/IEC 27001:2022 and SOC 2 Type II, each scoped to named products
- Payment by card, wire in USD or EUR, AliPay and PayPal; no Bitcoin
Best suited for: regional app-availability work where the country list matters more than the cost of a gigabyte
9. Novada — Carrier-heavy HTTP pool
3.8 / 5 for this job · from $0.50 / GB
Ninth, on the strength of carrier breadth. Novada presents mobile inventory separately from the residential pool: 2M+ 3G/4G/5G addresses and 120+ carriers inside 195+ countries with city-level precision. If you are matching a phone's apparent network to the carrier the app expects, that is the widest carrier count in this table, and mobile traffic starts at $1.5/GB.
The obstruction is the protocol. The record lists HTTP(S) support and nothing else. Android per-app proxy tools and most tunnelling apps ask for a SOCKS5 endpoint, and the stock Wi-Fi proxy dialogue is an HTTP proxy with no credential fields — so an HTTP-only pool means adding a helper app on the device and accepting whatever that app does with authentication, or routing through a local client that converts the protocol. Either is work, and neither is in the record as a supported configuration. The session window is stated, at 1–120 minutes on residential and 360-minute sticky sessions on rotating ISP, which is useful information but does not fix the transport question.
Other caveats sit around the edges. Unlimited Proxies, IPv6 Proxies and Datasets have no published price and go through an account manager. The headline 99.99% success rate is not uniform — rotating datacenter is quoted at 99%. The free trial covers the Scraper API only; the general offer is a $10 credit, which is a different thing. Compliance is stated as GDPR and CCPA with a consent-based sourcing claim, and there is no third-party audit in the record alongside those self-reported figures.
Key features
- 2M+ mobile IPs across 120+ carriers and 195+ countries, per the provider
- Mobile proxies from $1.5/GB
- HTTP(S) support only; no SOCKS5 listed
- 1–120 minute sessions on residential; 360-minute sticky sessions on rotating ISP
- $10 credit without a card; free trial limited to the Scraper API
- Unlimited Proxies, IPv6 Proxies and Datasets priced only through an account manager
Best suited for: carrier-matched work where you control the client stack and can put a protocol converter in front of an HTTP pool
10. Webshare.io — IP-auth SOCKS5 entry
3.6 / 5 for this job · from $0.02 / month
Tenth, and the one that lines up most cleanly with what an Android device can actually do on its own. Webshare lists HTTP and SOCKS5 endpoints on the same credentials, and IP authorisation as an alternative to username and password. That pair is what the stock Android Wi-Fi proxy setting needs: it can take a host, a port and a protocol, but it has no field for a username and password, so an IP-authorised SOCKS5 endpoint is the configuration that works without installing anything else on the phone.
It is also the cheapest way to find out whether any of this works on your device. There is a permanent free plan with 10 proxies and no credit card, and paid datacenter proxies start at $2.99/month for 100 proxies, quoted at $0.0299 per proxy, falling to $0.0179 as volume grows; yearly billing takes another 30% off, per the provider. Three pools are sold separately — datacenter, static residential (ISP) and rotating residential — with the rotating pool targetable by country, state, city, ZIP code and ASN, and a Chrome extension for people who would rather not script the request.
The catch for this job is that the cheap and free layers are datacenter addresses, not carrier ones, so they do not put the phone on the network the apps expect — the static residential pool names Comcast and AT&T and then says "& more", which means a specific carrier cannot be checked before buying. The unlimited bandwidth claim carries an asterisk pointing at a Fair Usage Policy. The provider's own pages give both 195 countries and 50+ locations, and the 99.7% success rate and 99.97% uptime are unaudited provider figures.
Key features
- HTTP and SOCKS5 endpoints on the same credentials
- IP authorisation offered as an alternative to username and password
- Permanent free plan with 10 proxies, no card required
- Datacenter proxies from $2.99/month, $0.0299 per proxy falling with volume
- Rotating residential targetable by country, state, city, ZIP and ASN
- Unlimited bandwidth subject to a Fair Usage Policy
Best suited for: proving out an IP-authorised SOCKS5 setup on a phone before spending anything, accepting datacenter addresses at the free tier
11. ProxySale.com — SOCKS5 residential only
3.4 / 5 for this job · from $0.06 / GB
Eleventh, and the entry to reach for when the protocol question is settled but the budget is not. Proxy-Sale lists HTTP, HTTPS and SOCKS5 on the residential product, so the per-app tools that want SOCKS5 have a real endpoint, and residential pricing starts at $0.5/GB with usage-based billing. The pool is 86M+ addresses across 200+ countries by the provider's count, with country, state and city targeting.
What it does not sell is mobile. There is no carrier inventory in the record — the products are residential, static residential at $5/IP, static datacenter at $3/IP and the API lines — so an Android device here sits on a residential address rather than a carrier one. That is a different configuration from the one apps tend to expect, and it is the main reason this sits below the mobile-first providers. The unlimited residential plan removes the IP and traffic caps for $69.68 a day, which suits a device that idles but is awkward billing for anything that runs for weeks.
The rest of the caveats are about verification. Uptime, success rate and response time are provider-declared — 99.9%, 99.5% and under 0.6s — with no third-party audit shown in the record. The service is not available in mainland China, by the provider's own policy, which rules out testing from there. The 30-day zero-setup trial applies to the Web Scraper API, not the proxy network, so trying the proxies means paying for them. Web Scraper API billing is on successfully delivered results only, which is a fairer arrangement than most.
Key features
- HTTP, HTTPS and SOCKS5 on the residential product
- 86M+ residential IPs across 200+ countries, per the provider
- Residential pricing from $0.5/GB with usage-based billing
- Unlimited Residential at $69.68/day with no IP or traffic cap
- Static residential at $5/IP and static datacenter at $3/IP
- Trial covers the Web Scraper API only, not the proxy network
Best suited for: SOCKS5 residential work on a phone where a residential address is acceptable and per-gigabyte billing suits the traffic pattern
12. ASocks.com — Per-proxy mobile billing
3.3 / 5 for this job · from $5 / proxy
Twelfth, and the one to look at if a monthly-per-proxy invoice is easier to justify than a meter. ASocks prices mobile at $15 per proxy per month, against $5 per proxy per month for residential and corporate, with volume discounts of 5% from 10 proxies, 10% from 50 and 15% from 100. For an Android device that is left on for hours at a time, a flat per-proxy rate removes the anxiety of background sync quietly running up a per-gigabyte bill — the cost is the same whether the phone is idle or busy.
The footprint is put at 150+ locations and 7M+ IP addresses, with the provider running its own infrastructure and linking that to cleaner addresses and fewer bans. Support is quoted 24/7 with an average response under 10 minutes, and there are three product lines — mobile, residential and corporate — so the same account can hold a phone on a carrier address and a desktop on something cheaper.
The catch is that every figure here is the provider's own and unaudited: the 99.7% connection success rate, the 150+ locations, the 7M+ IPs, the 100,000+ clients, the G2 ranking. None of it comes with independent verification in the record. Mobile also costs three times the residential rate, which is defensible for carrier addresses but worth stating plainly. Most importantly for this job, the record lists no supported protocols and no authentication method — so whether the mobile endpoints speak SOCKS5, and whether they can be locked to an IP rather than a password, are questions to put to support before paying, because they decide whether the phone can use them at all.
Key features
- Mobile proxies at $15 per proxy per month; residential and corporate at $5
- Volume discounts of 5%, 10% and 15% from 10, 50 and 100 proxies
- 150+ locations and 7M+ IP addresses, per the provider
- Own proxy infrastructure, described by the provider as clean addresses
- 24/7 support with a quoted average response under 10 minutes
- No protocols or authentication methods listed in the record
Best suited for: a phone kept online for long stretches where a predictable monthly per-proxy charge beats metered traffic, once protocol and auth are confirmed
13. ChangeMyIP.com — Protocol-heavy mobile option
3.2 / 5 for this job · from $1
ChangeMyIP.com sits at 13 because the parts that suit an Android handset are spread across its catalogue rather than sold as one mobile product with a location list. What it does have is the widest protocol menu on this page: HTTP, SOCKS5, ShadowSocks, Trojan, DNS proxy and Wireguard VPN, each priced separately. Shared tiers sit at $1.00, SOCKS5 at $2.20, ShadowSocks at $2.20, Trojan at $3.00 and Wireguard at $4.00. For a phone that menu matters more than pool size, because Android's built-in Wi-Fi proxy field takes a host and a port and nothing else — it cannot send a username or password. A Wireguard profile or a ShadowSocks client sidesteps that entirely by moving the tunnel below the app layer, and few providers here sell either.
Mobile is listed as a product family alongside residential, datacenter, reseller and affiliate lines, with unlimited bandwidth and 1Gb/s ports stated. The record gives no mobile location count, so treat "mobile" as a category rather than a promise of a specific country. The network is described as sitting on multiple IP subnets, and activation is stated as instant.
The awkward parts are real. A $10 minimum order applies even if you want a single $1.00 shared address. Shared proxies put multiple users on the same IP, and the provider itself warns bandwidth can suffer on busy servers — on a phone that shows up as a page that half-loads. Torrents and paypal.com are blocked at the proxy level on every product. The 30-day guarantee does not apply once the service has been used, and refunds are limited to bugs or slow performance. The "fully anonymous and undetectable" wording is unverified marketing with no published independent test behind it.
Key features
- SOCKS5, ShadowSocks, Trojan, DNS proxy and Wireguard VPN sold as separate products
- Shared tiers at $1.00; SOCKS5 at $2.20, Trojan at $3.00, Wireguard VPN at $4.00
- Unlimited bandwidth, 1Gb/s ports and 1Gb/s-plus dedicated connections, as stated
- Mobile listed as a product family alongside residential, datacenter and reseller
- $10 minimum order even for one shared proxy
- Torrents and paypal.com blocked at proxy level on every product
Best suited for: best suited for Android users who need a tunnel below the app layer, such as Wireguard or ShadowSocks, rather than a plain HTTP proxy
14. Nsocks — SOCKS5 residential pool
3.1 / 5 for this job
Nsocks is on the list because SOCKS5 is offered on the residential pool and the pool is large. The provider's own home page quotes 80M+ residential IPs in one place and 90M+ across 190+ country and city-level regions in another. Both figures are sitting there side by side, which is worth knowing before either is treated as exact. Stated uptime is 99.95%, targeting is country and city, and the protocol set is HTTP, HTTPS and SOCKS5.
For Android, SOCKS5 is the half that matters. The platform's Wi-Fi proxy screen carries a host and port with no credentials, so a pool that authenticates per request needs a client that can hold those credentials itself — a tunnelling app or a per-app proxy tool with SOCKS5 support. Product lines are billed separately: rotating residential per GB in packs from 10 GB to 500 GB, static residential per IP on a monthly basis, plus datacenter and ISP tiers. A personal dashboard with traffic statistics and an API are listed, and support runs 24/7 by live chat and email.
The catch is that you cannot check any of it before paying. There is no free trial, and the provider states it does not refund products sold. If the first thing you want to do is confirm that a particular app opens from a particular city on a phone, an untestable and unrefundable pool is a poor first purchase. Third-party records put the founding date at 26 August 2024, so the operating history is short. Note too that mobile appears in the provider's sourcing wording rather than as a separate mobile product line on this record, so an Android device expecting a carrier address should not assume one.
Key features
- SOCKS5 alongside HTTP and HTTPS on the residential side
- 80M+ residential IPs claimed in one place, 90M+ across 190+ country and city-level regions in another
- Country and city targeting; 99.95% uptime, both stated by the provider
- Rotating residential billed per GB from 10 GB to 500 GB; static residential billed per IP monthly
- No free trial and no refunds on products sold, per the provider
- Founded 26 August 2024 per third-party records
Best suited for: best suited for Android work that needs SOCKS5 against residential addresses in a named city, where pool size outweighs being able to trial it first
15. GonzoProxy — Two-country mobile
3.0 / 5 for this job · from $2 / GB
GonzoProxy is the only provider in this group selling mobile addresses on an unlimited-traffic daily rate: $7 for three days, $15 for seven, $45 for 30, and $135 for a single-country line. That is a shape an Android user can actually evaluate — a short, cheap window on a carrier address rather than a month's commitment or a per-GB meter that drains while the phone sits idle. Protocols include SOCKS4, SOCKS5, HTTP and HTTPS, and the record lists both IP and user:pass authentication, so a client that can carry credentials has something to carry.
Sticky sessions run up to 72 hours by the provider's statement, which is the detail that matters on a handset. A phone drops from Wi-Fi to cellular and back; a session that resets on every switch breaks logins halfway through. Rotating and sticky are both offered, residential targeting goes down to country, city, state, continent, ZIP code and ASN, concurrent connections are unlimited on every plan, and pay-per-GB traffic never expires and rolls over. Access is stated as live in about 30 seconds with no KYC.
The catch is coverage. Mobile proxies cover Poland and Ukraine only as of writing. If the app you want is locked to the US, UK or Germany, this is not the provider for it, whatever the residential side advertises — 20M+ IPs across 190 countries is the residential figure, not the mobile one. Nor is there a free trial: the demo is $1.99 for 0.3 GB and a 1 GB trial is $4.50. Two published residential plan ladders quote different per-GB rates for the same volumes, the dashboard lacks detailed per-request logs, and the speed and success-rate numbers on the site are the provider's own and not independently verified there.
Key features
- Mobile proxies in Poland and Ukraine only
- Mobile at $7 for 3 days, $15 for 7 days, $45 for 30 days, unlimited traffic
- SOCKS4, SOCKS5, HTTP and HTTPS; IP and user:pass authentication
- Sticky sessions up to 72 hours and rotating sessions, per the provider
- Pay-per-GB traffic never expires and rolls over to the next plan
- Demo is $1.99 for 0.3 GB; no free trial
Best suited for: best suited for Android work that needs a real carrier address in Poland or Ukraine and can do without any other mobile country
16. Live Proxies — B2B-only SOCKS5
2.8 / 5 for this job · from $2
Live Proxies lands last here because the piece an Android setup usually needs — SOCKS5 — sits behind its B2B tier. The record lists HTTP/S as the general connection protocol and HTTP with SOCKS5 for B2B. On the B2C side a phone is left with an HTTP proxy, which is precisely the case where Android's built-in Wi-Fi proxy field, unable to carry a username and password, becomes the obstacle.
There is a mobile product, and it is not trivial: rotating mobile IPs with 30-minute sticky sessions, examples being 50 IPs with 4 GB for $70 across 30 days and 100 IPs with 8 GB for $120 across 45 days. Private IP allocation is stated, as are no concurrency limit, unlimited threads and unlimited requests, with unused bandwidth rolling over to the standby plan. Dashboard access, API access and IP whitelisting come included, and the B2B enterprise tier runs on a 10M+ IP pool at $2K a month with tailored plans.
The catches stack up quickly for a handset. Thirty minutes of stickiness is short for a device that changes network mid-session, and whitelisting is awkward when the carrier hands your phone a different address on every reconnect. Geography is described as available countries or state-level options with no count, and state IPs are US only. Static residential is priced at $65.00 a plan on the home page and marked permanently unavailable on the pricing page; the $45.00, $65.00 and $55.00 starting prices do not reconcile with "B2C plans starting from $70" quoted elsewhere. The free trial goes to custom plan users after an agreement, with B2C buyers told to buy a small plan instead.
Key features
- SOCKS5 on the B2B tier; HTTP/S on the standard connection
- Rotating mobile with 30-minute sticky sessions; rotating residential at 60 minutes
- Mobile at 50 IPs with 4 GB for $70 over 30 days; 100 IPs with 8 GB for $120 over 45 days
- No concurrency limit, unlimited threads and unlimited requests, per the provider
- Unused bandwidth rolls over to the standby plan
- Static residential marked permanently unavailable on the pricing page
Best suited for: best suited for business buyers needing SOCKS5 across a mixed residential and mobile estate rather than for a single handset
Android proxies: questions we get
Can I use a SOCKS5 proxy in the Android Wi-Fi settings?
No. The manual proxy form on a Wi-Fi network is an HTTP proxy entry: hostname, port and bypass list, with no protocol selector. SOCKS5 needs either a client app that routes through the VPN service or a global setting pushed over ADB, and neither of those is a SOCKS5 option in the stock settings screen.
What does '407 Proxy Authentication Required' mean on Android?
It means the proxy wants a username and password and did not get one. The stock Wi-Fi proxy field has nowhere to put credentials, so this is what you see when a paid pool is pointed at by an app using the system proxy. You need a client app that supports authentication, or a provider endpoint that authorises you by IP address instead.
Why does my Android proxy stop working when I leave the house?
The proxy is stored against one Wi-Fi network, so it applies only while you are on that network. When the phone hands over to cellular there is no proxy configuration for the mobile connection at all, and traffic goes out directly from the carrier address. A VPN-based client survives the switch; the built-in setting cannot.
Do I need to root my phone for per-app proxy routing?
Generally no. Per-app split tunnelling is a standard feature of Android's VPN service and most proxy clients expose it as an allow-list or block-list of apps. Root is only needed if you want to redirect traffic per UID with firewall rules, which catches apps that a VPN client cannot see.
Will a proxy change the GPS location my phone reports?
No. A proxy changes the address other servers see. Location from GPS, Wi-Fi scanning or cell towers comes from the device's own sensors and is unaffected, so an app that requests a location fix will still get your real one unless you also change the device's location settings.
Does a proxy work on mobile data?
Not through Android's built-in settings — there is no proxy field for a carrier connection. A VPN-based proxy client does work over mobile data, because it claims the routing table rather than configuring a network. That is the usual reason people install a client app instead of using the Wi-Fi setting.
Which apps ignore the Android proxy setting?
Any app that does not consult the platform proxy selector. In practice that includes many games, apps with bundled networking libraries, and some push-notification channels. Chrome for Android has no proxy settings of its own and its handling of the system proxy has varied by version, so a browser is the worst place to verify that the setting is working.
How do I check what IP address my phone is showing?
Load /what-is-my-ip/ in whatever app you are testing, or check inside the app itself if it displays connection details. Test from within the app that matters rather than the browser, because coverage differs per app on Android and the browser result tells you nothing about the rest.
Is using a proxy on Android legal?
Running a proxy is legal in most countries and using one is generally legal too. What is not legal is using one to commit fraud, to access accounts that are not yours, or to evade sanctions. Separately, many services prohibit proxies in their terms of service — breaking those gets your account closed rather than the police involved, and the two things should not be confused.
Why is a proxy so slow on a phone?
Three usual causes: the exit address is geographically far from the destination, the proxy is a shared free endpoint with a queue of users, or the radio has to wake from idle for each request. Mobile carrier addresses add latency of their own. A paid endpoint near your target and a client that keeps a persistent connection fixes most of it.
Do free Android proxy apps work?
The apps generally do, but many are ad-supported clients pointed at free public pools, which are slow, frequently dead and run by unidentified operators. They are fine for a quick glance at a page from another country. They are not appropriate for anything involving a login, payment or personal data, because the operator can see every plaintext request.
Other jobs people buy proxies for
- Web scraping
- SEO and rank tracking
- Ad verification
- Price monitoring
- Multi-account management
- Antidetect browsers
Some links on this page are affiliate links: if you buy through them we may earn a commission, at no cost to you. It does not change the order above — see our monetisation policy.