How we measured Google access
Each provider got the same Google searches from our three servers (USA, Germany, Singapore) twice a day on 24–27 October 2026, with a new exit IP on every request.
- The request. google.com/search for 'weather' with the exit country set, 20 searches per provider and country, 12 countries. The client looks like a phone browser: curl_cffi with the Chrome 131 Android TLS fingerprint, without JavaScript.
- Success. HTTP 200 and not the /sorry/ page: the results, the 'turn on JavaScript' page or the consent page. All three mean Google let the IP in; a blocked IP gets the CAPTCHA first.
- Who shares first place. Each rate has a Wilson 95% confidence interval. Providers whose interval overlaps the leader's share first place.
Limits
- No JavaScript. A real browser runs JavaScript and keeps cookies, so its numbers differ; the comparison between providers does not change.
- One query. Every search was the same simple query. Heavy automated querying gets blocked sooner at every provider.
- Raw data and scripts. The anonymized request logs, the test scripts and the results workbook are on GitHub, so every number here can be recomputed.
More from the benchmark
- The full benchmark. All 11 providers on every metric: mobile IP share, success rate, latency, Google and Instagram, sticky sessions, TCP fingerprint, IP quality and cost.
- Cheapest mobile proxies. Cheapest Mobile Proxies: Cost per Successful Request, Tested
- Mobile proxies with the least shared IPs. Mobile Proxies with the Least Shared IPs: Pool Overlap Tested