195 Published Paid-Location Routes
The June 9, 2026 snapshot totals 34,873,599 historical IPs across 194 country records with published values; 1 record has its historical count explicitly unavailable. Residential Flex is not counted as a fourth origin, and these values are not live inventory.
See each product pricing page for current plan terms.
Largest historical country totals
The twelve largest country records in the June 9, 2026 snapshot, shown as historical comparison context rather than a quality or availability ranking.
- #1United States3,203,665 historical IPs
- #2Brazil2,858,324 historical IPs
- #3Indonesia2,664,464 historical IPs
- #4India1,980,646 historical IPs
- #5Mexico1,552,484 historical IPs
- #6Italy1,299,820 historical IPs
- #7Spain1,238,826 historical IPs
- #8Argentina1,225,819 historical IPs
- #9UK1,205,913 historical IPs
- #10Vietnam1,183,202 historical IPs
- #11Germany1,162,084 historical IPs
- #12France916,416 historical IPs
Each location below has a data-bounded guide and either a dated historical count or an explicit unavailable label. A count does not prove current routing. Jump to the full directory.
Which paid product fits your project?
All four products share a gateway and the documented proxy modes. They differ in pool size, network origin, targeting precision, configured coverage, session limits, and price.
| Network | Pool size | Network origin | Best for | Current terms | Targeting controls |
|---|---|---|---|---|---|
| Residential | 34M+ IPs · cumulative catalogue total, not live availability | ISP-classified | Authorized tests requiring an ISP-origin route | View current pricing | Selected source capability |
| Residential Flex | 9M+ IPs · cumulative catalogue total, not live availability | ISP-classified | Authorized workloads using the Flex network | View current pricing | Selected source capability |
| Datacenter | 80K+ IPs · cumulative catalogue total, not live availability | Hosting network | Shared hosting-network routes with country or continent control | View current pricing | Selected source capability |
| Mobile | 800K+ IPs · cumulative catalogue total, not live availability | Mobile carrier | Authorized app and mobile-network QA | View current pricing | Selected source capability |
Available targeting controls depend on the active source capabilities for the selected network. See the full proxy comparison
Proxy locations by country
Select a country for its available June 9, 2026 historical count (or an explicit unavailable label), plus fresh configured-product state and product-specific targeting guidance. Counts are not live inventory.
Europe
46 records · 8,251,275 known historical IPs
Asia
50 records · 12,762,145 known historical IPs
North America
27 records · 5,483,677 known historical IPs
Africa
50 records · 2,568,139 known historical IPs
Oceania
8 records · 512,003 known historical IPs · 1 count unavailable
South America
14 records · 5,296,360 known historical IPs
Evidence-led route decisions
Open the country guide that matches the control you need
These priority guides turn a country name into a bounded test plan. Each page checks current product reporting at request time; inclusion here does not claim that an exit is available.
- Local-web controlsAudit a United States route for local-web QASeparate the observed network origin from store, address, tax, language, account, and device controls.Review route evidence
- Storefront matrixReview India route evidence for storefront localizationKeep PIN, language, currency, shipping, account, and handset inputs explicit before comparing results.Review route evidence
- Language matrixCheck Vanuatu evidence for trilingual public-service QACompare Bislama, English, and French cases independently without inferring island or city precision.Review route evidence
- .km route checkCompare a Comoros route for an authorized .km checkPair one direct control with one routed observation and retain DNS, response, and timestamp evidence.Review route evidence
- City-state boundaryTest Monaco without inventing city-level precisionTreat a verified country result as the full geographic result for this city-state.Review route evidence
- Bilingual checkoutReview Jordan evidence for Arabic–English storefront QAHold language direction, JOD display, account, address, and device state constant across the comparison.Review route evidence
- .bi canaryCheck a Burundi route before .bi service monitoringRecord DNS, TLS, redirects, status, bytes, and a safe body digest for the authorized endpoint.Review route evidence
- Identity fixturesVerify Eritrea evidence for +291 and .er localizationKeep calling code, domain, time zone, browser clock, and account state as separate fixtures.Review route evidence
- Record integrityCompare a Chad route for bilingual public recordsTrack the French and Arabic record identifier, date, URL, media type, bytes, and digest.Review route evidence
- Locale releaseAudit a Turkmenistan route for tk-TM release QAValidate Turkmen letters, TMT formatting, fonts, and cache keys directly before adding a routed case.Review route evidence
- WS identityCheck Samoa route identity before registry deadline QAKeep Samoa distinct from American Samoa and separate Pacific/Apia time from network origin.Review route evidence
- Territory releaseVerify FO territory evidence for a Faroese releaseKeep FO, any separate Denmark control, language, currency, and network origin independently labelled.Review route evidence
- Checkout controlReview FK route evidence for owned checkout QACompare one synthetic cart or delivery quote without inferring city, island, currency, or delivery policy.Review route evidence
- Identity ledgerKeep CF, CAF, and XAF distinct in route QAAudit country code, catalogue identity, hostname, currency fixture, and network origin as separate fields.Review route evidence
Why proxy location matters
Network origin can affect an authorized observation, but it does not reproduce a local user. Keep language, currency, account, address, device, cookies, and timestamp explicit.
Source-advertised geo controls
Use country, continent, city, ZIP, coordinate, or ASN controls only when the selected network source advertises the corresponding capability.
195 countries
The historical catalogue spans every major region. Open a country page to see which paid products have a fresh configured-routing observation, then verify the exit.
Rotating or sticky
A named session can request continuity for up to 120 minutes when the selected source advertises it. Availability can end continuity earlier.
Source-advertised ASN controls
An ASN can appear in coverage evidence without implying that ASN targeting is enabled. Check the selected source capability and verify the exit.
Username-flag control
Use only documented flags that the selected source capability advertises; this directory does not imply unsupported credential syntax.
Documented proxy modes
Confirm the current gateway protocols and authentication format in the dashboard or documentation before configuring a client.
Proxy location FAQ
How do I geo-target a specific country?
Can I target a city, ZIP code, or ASN instead of a whole country?
Does geo-targeting cost extra?
Which protocols do location-targeted proxies support?
Do all 195 location records have all four paid products?
How fresh are the IP counts on this page?
Compare routing across 195 location records
Open a country to see its fresh configured-product state, then create a general pool account and verify the observed exit. A location CTA does not preselect or reserve a target country.
Pricing, order minimums, and traffic validity vary by product.