A mobile proxy sends traffic through an address that a mobile operator assigns to a phone or a modem. Apps that trust carrier ranges treat that exit as a handset on a cell network.
Take this type when the target is strict about hosting and home-broadband flags. If the job is ordinary scraping on a site that already accepts household IPs, residential proxies are usually enough.
How to choose
Confirm what “rotation” means on a mobile plan. Some products keep one modem and change the public IP when the carrier NAT refreshes. Others move you across a pool of carrier addresses on a timer. Those behaviors are not interchangeable when an app pins a session to a subnet.
Compare per-port and per-GB billing with the way you hold connections. Anti-detect browsers often sit on a port for hours, so a port fee is easier to forecast. Short bursts of API calls may fit metered traffic instead. Ask what happens if you idle on a port all day.
Check country and carrier targeting. A country filter is the minimum. A named operator matters when an app treats two carriers in the same country as different reputations. If the provider cannot name the operator, assume you will get a mix.
Ask how many customers share a modem or a carrier IP. A dedicated modem is simpler for account work. A shared mobile pool is cheaper and noisier. If the listing does not say, treat sharing as unknown and test before you scale.