Puerto Rico Proxies
11,072+ residential and mobile proxy IPs in Puerto Rico. 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.
North America market board
- Published IPs
- 11,072
- Regional pool
- 5,483,677
- Network types
- 2
- Covered ASNs
- 7
Puerto Rico network coverage
The proxy networks reported for Puerto Rico, 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)
Mobile Proxies
Live4G and 5G carrier-network IPs for authorized app testing and mobile-network checks.
- Global pool
- 800K+ IPs
- Network origin
- Mobile carrier
- From
- $2.50/GB (512 GB plan)
A network shows as Live only when it is currently serving traffic in Puerto Rico. Global pool sizes are catalog-wide; browse the live community proxy list for Puerto Rico to sample real endpoints.
Target Puerto Rico down to the city and ASN
Set countryCode-pr in your proxy username, then layer city, ZIP, GPS, or AS number on top at no extra cost.
Country routing
One flag,
countryCode-pr, requests an exit geolocated to Puerto Rico, 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 7 autonomous systems covered in Puerto Rico
- AS11992 LIBERTY-MOB-PR - Liberty Mobile Puerto Rico Inc.
- AS14979 AERONET-WIRELESS - Aeronet Wireless
- AS53764 DMWIRELESS - DM Wireless LLC
- AS10396 COQUI-NET - DATACOM CARIBE, INC.
- AS21559 OSNET - OSNET
- AS23114 CRITICALHUBNET - Critical Hub Networks
- AS396082 COSOT - COSOTNET INC
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 Puerto Rico
curl -x http://USER-zone-residential-countryCode-pr:PASS@gw.databay.co:8888 \
https://databay.com/cdn-cgi/trace
# Sticky session (30 minutes) in Puerto Rico
curl -x http://USER-zone-residential-countryCode-pr-sessionId-abc123:PASS@gw.databay.co:8888 \
https://databay.com/cdn-cgi/trace
# Datacenter proxy in Puerto Rico
curl -x http://USER-zone-datacenter-countryCode-pr:PASS@gw.databay.co:8888 \
https://databay.com/cdn-cgi/tracePricing for Puerto Rico: residential from $0.90/GB (PAYG $2.75/GB), datacenter from $0.50/GB (volume), mobile from $2.50/GB. All tiers include country targeting for Puerto Rico at no extra cost. See documentation.
Network-wide operating targets for Puerto Rico 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 Puerto Rico proxies are used for
Authorized workflows where a documented Puerto Rico network-origin sample can answer a defined question.
Web scraping
Collect permitted public fields from approved sources in Puerto Rico with a documented request budget and validation plan.
ExploreAd verification
Compare authorized campaign rendering from a Puerto Rico network origin while holding account, device, and locale state constant.
ExploreMarket research
Add a Puerto Rico network-origin sample while recording account, language, delivery, tax, and personalization limits.
ExploreSEO monitoring
Record permitted Puerto Rico search observations with the query, language, device, timestamp, and observed exit documented.
ExploreE-commerce tracking
Validate permitted Puerto Rico 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 Puerto Rico (34M+ IPs from $0.90/GB). Testing first? You can browse the live community proxy list for Puerto Rico (refreshed every 5 minutes).
Reading the published Puerto Rico address count
Databay's June 9, 2026 paid-network catalogue assigns 11,072 addresses to Puerto Rico. That places Puerto Rico number 125 of 195 locations worldwide and number 15 of 27 in North America. The Puerto Rico allocation represents <0.05% of the global catalogue and 0.20% of the North America total. For Puerto Rico, those figures describe catalogue breadth, not a count of exits guaranteed online at one moment. The Puerto Rico count also does not establish address ownership, consent, residential status, latency, reputation, city accuracy, or acceptance by a destination. Use the live Puerto Rico coverage panel on this page to see which Databay network types currently report service, then confirm the observed exit before relying on a result. Puerto Rico pricing is determined by network and plan rather than by inflating the country count into a performance promise.
Isolate the Puerto Rico network-origin variable
The gateway flag countryCode-pr requests an exit geolocated to Puerto Rico, subject to current supply and the selected network. For Puerto Rico, it changes one input: the apparent network origin seen by the destination. An exit geolocated to Puerto Rico 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 comparison involving Puerto Rico, write down the hypothesis first and hold those other inputs constant. Check the Puerto Rico exit with a diagnostic endpoint you trust, save the timestamp and effective settings, and compare the observation with a direct or controlled reference. If city, ZIP, coordinate, or ASN precision in Puerto Rico matters, validate that narrower result separately; country success does not prove subnational accuracy.
Plan Puerto Rico sessions from the actual pool scale
Puerto Rico has a limited but material published allocation. Design Puerto Rico 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 Puerto Rico filter returns no suitable exit, broaden the test or stop rather than claiming unavailable coverage. Puerto Rico 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 Puerto Rico pool rather than rotating around it. Record Puerto Rico failures as data; do not hide them with unlimited retries.
Puerto Rico in its North America comparison set
The immediately larger North America catalogue entry than Puerto Rico is Aruba at 12,116 addresses, and the next smaller is Bermuda at 11,037. In the Puerto Rico comparison set, the regional leader is United States of America with 3,203,665. These Puerto Rico capacity comparisons are useful only when the workload could legitimately run from more than one country. Choose Puerto Rico when the research question specifically needs a network-origin observation from Puerto Rico. Choose a different country from Puerto Rico only when it is a valid control or a separate market in the study. Combining Puerto Rico observations with other countries in one unlabeled dataset makes regional differences impossible to interpret. Preserve the requested Puerto Rico route, observed exit country, network type, timestamp, source, response class, and validation outcome on every retained record.
A reproducible Puerto Rico validation checklist
Before using a Puerto Rico result, capture five things: the canonical source URL and permission basis; the Databay network and countryCode-pr 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 Puerto Rico check from a controlled reference and label missing, blocked, challenged, stale, or personalized responses instead of treating them as ordinary content. For a consequential Puerto Rico price, availability, advertising, search, compliance, or product decision, obtain a second authorized source or local review. This Puerto Rico workflow makes the 11,072-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 Puerto Rico?
What types of proxies are available in Puerto Rico?
Which networks and ASNs are covered in Puerto Rico?
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 Puerto Rico proxies
Review live Puerto Rico coverage and access the published pool under the selected plan and service limits.
Pricing, order minimums, and traffic validity vary by product.