Need your traffic to come from Mexican? IPLight's dynamic residential pool covers Mexican among 200+ countries:
add country-mx to the username and every exit IP is a Mexican household address. Billing is by traffic, not by
IP count, and the same balance also covers static ISP IPs and datacenter traffic.
Which product for Need Product Billing Rotating Mexican residential for scraping/monitoring Dynamic residential, country=country-mx $1.20/GB → $0.60/GB by tier A fixed Mexican IP for accounts & logins Static residential (ISP) - static stock varies, check console for current MX inventory $3/IP/mo, $2 from 15 IPs Bulk bandwidth against soft targets Datacenter proxy $1/GB, 100 GB min
?
| Need | Product | Billing |
|---|---|---|
| Rotating Mexican residential for scraping/monitoring | Dynamic residential, country=country-mx | $1.20/GB → $0.60/GB by tier |
| A fixed Mexican IP for accounts & logins | Static residential (ISP) - static stock varies, check console for current MX inventory | $3/IP/mo, $2 from 15 IPs |
| Bulk bandwidth against soft targets | Datacenter proxy | $1/GB, 100 GB min |
Live pool depth in Mexico
At the 5 November 2026 snapshot, IPLight's console inventory held 1,212 live Mexican exit addresses in the
rotating dynamic pool. That is a measured count of inventory as it stands - not a ceiling: the pool is
resupplied continuously and country targeting also draws on partner capacity beyond this snapshot. What
matters for your jobs is simpler: every request that adds country-mx to the username exits from a
Mexican household IP, with city-level targeting available in major metros.
Common Mexico use cases
Mexican residential exits are used for price monitoring on Mercado Libre México, Coppel and Liverpool, Spanish-language SERP tracking for the North American market, ad verification for MX-targeted campaigns, and keeping Mexican marketplace accounts on consistent local identities.
Why a local Mexican exit matters
Geo-served content is decided before the page renders: CDNs, marketplaces and ad networks look at the IP's registered country and serve prices, stock, creatives and even language accordingly. Requesting Mexico content from your office IP in another country gets you the international variant - different prices, different banners, sometimes a redirect to a global site. A Mexican residential exit removes that gap: the response you see is the response a Mexican user sees.
The same logic applies to rate scoring. Requests arriving from a foreign hosting range carry a different risk profile than requests from a Mexico household IP. That does not make scraping immune to blocks - frequency and fingerprint still matter - but it stops the origin itself from being the reason you fail.
Four steps to route traffic through Mexico
- Create an account and top up the smallest tier (100 GB, $120) - the same balance later covers static IPs or datacenter traffic if you need them.
- Set the country parameter: add
country-mxto the proxy username. Sticky sessions, city targeting and rotation mode are also controlled from the username, so one endpoint covers every layout. - Verify the exit with https://ipinfo.io/json - confirm the IP resolves to Mexico before you run real jobs.
- Measure, then scale: watch the hourly usage breakdown and the success rate on your actual targets, then move to a larger tier ($0.96/GB at 1 TB, $0.72/GB at 5 TB, $0.60/GB at 10 TB) when the numbers justify it.
Pricing for Order size Unit price Total Best for 100 GB $1.20 / GB $120 First orders, target testing 1,000 GB (1 TB) $0.96 / GB $960 Steady production crawling 5,000 GB (5 TB) $0.72 / GB $3,600 Multi-market monitoring 10,000 GB (10 TB) $0.60 / GB $6,000 High-volume operations
traffic
| Order size | Unit price | Total | Best for |
|---|---|---|---|
| 100 GB | $1.20 / GB | $120 | First orders, target testing |
| 1,000 GB (1 TB) | $0.96 / GB | $960 | Steady production crawling |
| 5,000 GB (5 TB) | $0.72 / GB | $3,600 | Multi-market monitoring |
| 10,000 GB (10 TB) | $0.60 / GB | $6,000 | High-volume operations |