Uruguay Proxies
12,473+ residential and mobile proxy IPs in Uruguay. 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.
- Brazil 2,858,324
- Argentina 1,225,819
- 372,203 Colombia
- 325,035 Chile
2 network types · 3 ASNs
Uruguay network coverage
The proxy networks reported for Uruguay, 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 Uruguay. Global pool sizes are catalog-wide; browse the live community proxy list for Uruguay to sample real endpoints.
Target Uruguay down to the city and ASN
Set countryCode-uy in your proxy username, then layer city, ZIP, GPS, or AS number on top at no extra cost.
Country routing
One flag,
countryCode-uy, requests an exit geolocated to Uruguay, 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 3 autonomous systems covered in Uruguay
- AS19422 Telefonica Moviles del Uruguay SA
- AS20255 Tecnowind S.A.
- AS6057 Administracion Nacional de Telecomunicaciones
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 Uruguay
curl -x http://USER-zone-residential-countryCode-uy:PASS@gw.databay.co:8888 \
https://databay.com/cdn-cgi/trace
# Sticky session (30 minutes) in Uruguay
curl -x http://USER-zone-residential-countryCode-uy-sessionId-abc123:PASS@gw.databay.co:8888 \
https://databay.com/cdn-cgi/trace
# Datacenter proxy in Uruguay
curl -x http://USER-zone-datacenter-countryCode-uy:PASS@gw.databay.co:8888 \
https://databay.com/cdn-cgi/tracePricing for Uruguay: residential from $0.90/GB (PAYG $2.75/GB), datacenter from $0.50/GB (volume), mobile from $2.50/GB. All tiers include Uruguay country targeting at no extra cost. See documentation.
Network-wide operating targets for Uruguay 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 Uruguay proxies are used for
Authorized workflows where a documented Uruguay network-origin sample can answer a defined question.
Web scraping
Collect permitted public fields from approved Uruguay sources with a documented request budget and validation plan.
ExploreAd verification
Compare authorized campaign rendering from a Uruguay network origin while holding account, device, and locale state constant.
ExploreMarket research
Add a Uruguay network-origin sample while recording account, language, delivery, tax, and personalization limits.
ExploreSEO monitoring
Record permitted Uruguay search observations with the query, language, device, timestamp, and observed exit documented.
ExploreE-commerce tracking
Validate permitted Uruguay 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 Uruguay (34M+ IPs from $0.90/GB). Testing first? You can browse the live community proxy list for Uruguay (refreshed every 5 minutes).
Reading the published Uruguay address count
Databay's June 9, 2026 paid-network catalogue assigns 12,473 addresses to Uruguay. That places Uruguay number 113 of 195 locations worldwide and number 12 of 14 in South America. The Uruguay allocation represents <0.05% of the global catalogue and 0.24% of the South America total. For Uruguay, those figures describe catalogue breadth, not a count of exits guaranteed online at one moment. The Uruguay count also does not establish address ownership, consent, residential status, latency, reputation, city accuracy, or acceptance by a destination. Use the live Uruguay coverage panel on this page to see which Databay network types currently report service, then confirm the observed exit before relying on a result. Uruguay pricing is determined by network and plan rather than by inflating the country count into a performance promise.
Isolate the Uruguay network-origin variable
The gateway flag countryCode-uy requests an exit geolocated to Uruguay, subject to current supply and the selected network. For Uruguay, it changes one input: the apparent network origin seen by the destination. A Uruguay 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 Uruguay comparison, write down the hypothesis first and hold those other inputs constant. Check the Uruguay 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 Uruguay city, ZIP, coordinate, or ASN matters, validate that narrower result separately; country success does not prove subnational accuracy.
Plan Uruguay sessions from the actual pool scale
Uruguay has a limited but material published allocation. Design Uruguay 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 Uruguay filter returns no suitable exit, broaden the test or stop rather than claiming unavailable coverage. Uruguay 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 Uruguay pool rather than rotating around it. Record Uruguay failures as data; do not hide them with unlimited retries.
Uruguay in its South America comparison set
The immediately larger undefined catalogue entry than Uruguay is French Guiana at 13,586 addresses, and the next smaller is Ecuador at 6,017. In the Uruguay comparison set, the regional leader is Brazil with 2,858,324. These Uruguay capacity comparisons are useful only when the workload could legitimately run from more than one country. Choose Uruguay when the research question specifically needs a Uruguay network-origin observation. Choose a different country from Uruguay only when it is a valid control or a separate market in the study. Combining Uruguay observations with other countries in one unlabeled dataset makes regional differences impossible to interpret. Preserve the requested Uruguay route, observed exit country, network type, timestamp, source, response class, and validation outcome on every retained record.
A reproducible Uruguay validation checklist
Before using a Uruguay result, capture five things: the canonical source URL and permission basis; the Databay network and countryCode-uy 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 Uruguay check from a controlled reference and label missing, blocked, challenged, stale, or personalized responses instead of treating them as ordinary content. For a consequential Uruguay price, availability, advertising, search, compliance, or product decision, obtain a second authorized source or local review. This Uruguay workflow makes the 12,473-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 Uruguay?
What types of proxies are available in Uruguay?
Which networks and ASNs are covered in Uruguay?
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 Uruguay proxies
Review live Uruguay coverage and access the published pool under the selected plan and service limits.
Pricing, order minimums, and traffic validity vary by product.