French Polynesia Proxies
8,191+ residential proxy IPs in French Polynesia. City-level geo-targeting, rotating and sticky sessions, HTTP, HTTPS & SOCKS5. Plans from $0.90/GB.
Pay as you go from 1 GB. Dataset updated June 2026; live availability varies by network type.
Oceania relay chain
- Australia458,747
- Fiji11,572
- New Caledonia11,212
- French Polynesia8,191
- Papua New Guinea7,904
- New Zealand7,517
- Vanuatu6,860
- American Samoa6,401
1 ASNs published for French Polynesia.
French Polynesia network coverage
The proxy networks reported for French Polynesia, with global catalogue size, network origin, and volume-plan entry price.
ISP-origin IPs for authorized regional sampling and workflows that require a consumer-network route.
- Global pool
- 34M+ IPs
- Network origin
- ISP-classified
- From
- $0.90/GB (1 TB plan)
A network shows as Live only when it is currently serving traffic in French Polynesia. Global pool sizes are catalog-wide; browse the live community proxy list for French Polynesia to sample real endpoints.
Target French Polynesia down to the city and ASN
Set countryCode-pf in your proxy username, then layer city, ZIP, GPS, or AS number on top at no extra cost.
Country routing
One flag,
countryCode-pf, requests an exit geolocated to French Polynesia, subject to live availability.City, ZIP & GPS requests
Request a narrower residential location, then verify the observed exit because live supply and geolocation can vary.
ASN targeting request
Request an autonomous system by AS number, subject to network support and current eligible exits.
Rotating or sticky
Request gateway-selected exits or a sticky target up to 120 minutes; connections and availability affect reuse.
- Country, city, ZIP, GPS, and ASN targeting included on every plan
- Gateway-selected exits or sticky session targets, subject to availability
- HTTP, HTTPS, and SOCKS5 on one gateway, no allowlisting
- Every flag set in the proxy username, no code changes
Sample of 1 autonomous systems covered in French Polynesia
- AS9471 ONATI-AS-AP ONATI
Select any country, city, or AS number directly in the proxy username. ASN availability varies by network type and real-time device counts.
# Rotating residential proxy in French Polynesia
curl -x http://USER-zone-residential-countryCode-pf:PASS@gw.databay.co:8888 \
https://databay.com/cdn-cgi/trace
# Sticky session (30 minutes) in French Polynesia
curl -x http://USER-zone-residential-countryCode-pf-sessionId-abc123:PASS@gw.databay.co:8888 \
https://databay.com/cdn-cgi/trace
# Datacenter proxy in French Polynesia
curl -x http://USER-zone-datacenter-countryCode-pf:PASS@gw.databay.co:8888 \
https://databay.com/cdn-cgi/tracePricing for French Polynesia: residential from $0.90/GB (PAYG $2.75/GB), datacenter from $0.50/GB (volume), mobile from $2.50/GB. All tiers include French Polynesia country targeting at no extra cost. See documentation.
Network-wide operating targets for French Polynesia routes
These catalogue-wide figures describe the service target, not a country-specific guarantee. Measure the exact route and workload before relying on it.
- Uptime target
- 99.9%+
- Network-wide availability
- Residential latency
- ~1.1s
- Median response time
- Datacenter latency
- ~780ms
- Median response time
- Max sticky target
- 120 min
- Subject to live exit availability
Latency and uptime are network-wide medians and targets. See how Databay benchmarks its network.
What French Polynesia proxies are used for
Authorized workflows where a documented French Polynesia network-origin sample can answer a defined question.
Web scraping
Collect permitted public fields from approved French Polynesia sources with a documented request budget and validation plan.
ExploreAd verification
Compare authorized campaign rendering from a French Polynesia network origin while holding account, device, and locale state constant.
ExploreMarket research
Add a French Polynesia network-origin sample while recording account, language, delivery, tax, and personalization limits.
ExploreSEO monitoring
Record permitted French Polynesia search observations with the query, language, device, timestamp, and observed exit documented.
ExploreE-commerce tracking
Validate permitted French Polynesia price and availability observations against feeds, APIs, or another authorized source.
ExploreSocial media
Operate authorized client accounts using platform-approved tools and stable sessions where the platform permits proxy access.
Explore
Other proxy locations
Compare published catalogue counts and then check live network and targeting availability for the exact location you need.
Largest pools worldwide
Need rotating IPs with city and ASN targeting? Get residential proxies in French Polynesia (34M+ IPs from $0.90/GB). Testing first? You can browse the live community proxy list for French Polynesia (refreshed every 5 minutes).
How French Polynesia compares in the proxy catalogue
Databay's June 9, 2026 paid-network catalogue assigns 8,191 addresses to French Polynesia. That places French Polynesia number 146 of 195 locations worldwide and number 4 of 8 in Oceania. The French Polynesia allocation represents <0.05% of the global catalogue and 1.6% of the Oceania total. For French Polynesia, those figures describe catalogue breadth, not a count of exits guaranteed online at one moment. The French Polynesia count also does not establish address ownership, consent, residential status, latency, reputation, city accuracy, or acceptance by a destination. Use the live French Polynesia coverage panel on this page to see which Databay network types currently report service, then confirm the observed exit before relying on a result. French Polynesia pricing is determined by network and plan rather than by inflating the country count into a performance promise.
Isolate the French Polynesia network-origin variable
The gateway flag countryCode-pf requests an exit geolocated to French Polynesia, subject to current supply and the selected network. For French Polynesia, it changes one input: the apparent network origin seen by the destination. A French Polynesia exit does not set a browser language, currency, time zone, delivery address, tax jurisdiction, account country, cookie history, device profile, or legal eligibility. For a useful French Polynesia comparison, write down the hypothesis first and hold those other inputs constant. Check the French Polynesia exit with a diagnostic endpoint you trust, save the timestamp and effective settings, and compare the observation with a direct or controlled reference. If a French Polynesia city, ZIP, coordinate, or ASN matters, validate that narrower result separately; country success does not prove subnational accuracy.
Plan French Polynesia sessions from the actual pool scale
French Polynesia has a limited but material published allocation. Design French Polynesia work for repeat exits: pace requests, use sticky sessions for multi-step authorized flows, and avoid multiplying concurrency merely because the gateway can rotate. If a narrow French Polynesia filter returns no suitable exit, broaden the test or stop rather than claiming unavailable coverage. French Polynesia pool depth also cannot authorize collection: the destination's terms, robots guidance, contracts, authentication boundaries, rate controls, and applicable law remain the controlling constraints. Treat a block, CAPTCHA, quota, or explicit denial as a stop or review signal across the whole French Polynesia pool rather than rotating around it. Record French Polynesia failures as data; do not hide them with unlimited retries.
French Polynesia in its Oceania comparison set
The immediately larger undefined catalogue entry than French Polynesia is New Caledonia at 11,212 addresses, and the next smaller is Papua New Guinea at 7,904. In the French Polynesia comparison set, the regional leader is Australia with 458,747. These French Polynesia capacity comparisons are useful only when the workload could legitimately run from more than one country. Choose French Polynesia when the research question specifically needs a French Polynesia network-origin observation. Choose a different country from French Polynesia only when it is a valid control or a separate market in the study. Combining French Polynesia observations with other countries in one unlabeled dataset makes regional differences impossible to interpret. Preserve the requested French Polynesia route, observed exit country, network type, timestamp, source, response class, and validation outcome on every retained record.
A reproducible French Polynesia validation checklist
Before using a French Polynesia result, capture five things: the canonical source URL and permission basis; the Databay network and countryCode-pf setting; the observed exit IP, ASN, and geolocation source; the browser, account, language, currency, address, cookie, and device state; and the UTC timestamp plus response evidence. Repeat the French Polynesia check from a controlled reference and label missing, blocked, challenged, stale, or personalized responses instead of treating them as ordinary content. For a consequential French Polynesia price, availability, advertising, search, compliance, or product decision, obtain a second authorized source or local review. This French Polynesia workflow makes the 8,191-address catalogue figure useful as coverage context without pretending it proves a resident's experience.
Frequently asked questions
How many proxy IPs does Databay have in French Polynesia?
What types of proxies are available in French Polynesia?
Which networks and ASNs are covered in French Polynesia?
How do I authenticate with Databay proxies?
Which protocols are supported?
Is there an API?
How do I get started?
Do you offer reseller or volume plans?
Start using French Polynesia proxies
Review live French Polynesia coverage and access the published pool under the selected plan and service limits.
Pricing, order minimums, and traffic validity vary by product.