Mobile proxy pricing: what one carrier GB buys

Originally published on proxymint.

Mobile proxy pricing explained: what a carrier GB buys, how to size a job before you pay, cost per successful request, and which jobs call for mobile IPs.

TL;DR

• Mobile proxies are usually sold per GB. On proxymint they come in one-off packages, the rate falls as the package grows, and the full table is on the pricing page.
• The rate reflects carrier supply and trust. Carriers share one public address across many subscribers with CGNAT, so platforms that score network origin treat carrier ranges carefully.
• Bytes drive the bill. A full mobile page render moves roughly 80 times the bytes of its HTML, and every retry is billed again.
• Measure cost per success. Success rate and bytes per attempt on the real target decide what a job actually costs.
• Match the tier to the target. Mobile fits app-first platforms, mobile ad checks and QA on carrier routing; catalogs and price checks usually clear on residential.

Key takeaways

• Size the job first. GB needed = requests x bytes per request x a retry factor, measured on a small sample.
• Measure success on the target. A platform that scores mobile origin shows it in the success rate of a small test.
• Test both tiers on a small package. Run the same 200 to 500 permitted requests through each and record success and bytes.
• Route desk-based account work to static ISP. Fixed ISP addresses are billed per IP per month; mobile fits accounts that live in an app.
• Buy one package per job. A package sized from the test covers the whole run, with no renewal and no expiry set on the GB.

Read the full guide on proxymint, with the commands, tables and sources.