North America routing coverage

Aruba Proxies

12,116+ residential and mobile proxy IPs in Aruba. 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
12,116
Regional pool
5,483,677
Network types
2
Covered ASNs
1
Region leaders: United States · Mexico · Canada
Published North America pool counts from the locations dataset, updated . Live availability can change.
12,116+
Published IPs in Aruba
2
Live network types
1
Autonomous systems
#14
Pool rank in North America
12,116+ published IPs in Aruba99.9%+ uptime targetCountry, city, GPS & ASN targetingHTTP, HTTPS & SOCKS5Databay Trust Center
Live coverage

Aruba network coverage

The proxy networks reported for Aruba, 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)
  • 4G 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 Aruba. Global pool sizes are catalog-wide; browse the live community proxy list for Aruba to sample real endpoints.

Geo-targeting

Target Aruba down to the city and ASN

Set countryCode-aw in your proxy username, then layer city, ZIP, GPS, or AS number on top at no extra cost.

  • Country routing

    One flag, countryCode-aw, requests an exit geolocated to Aruba, 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 Aruba

  • AS11816 SERVICIO DI TELECOMUNICACION DI ARUBA SETAR N.V.

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 Aruba
curl -x http://USER-zone-residential-countryCode-aw:PASS@gw.databay.co:8888 \
     https://databay.com/cdn-cgi/trace

# Sticky session (30 minutes) in Aruba
curl -x http://USER-zone-residential-countryCode-aw-sessionId-abc123:PASS@gw.databay.co:8888 \
     https://databay.com/cdn-cgi/trace

# Datacenter proxy in Aruba
curl -x http://USER-zone-datacenter-countryCode-aw:PASS@gw.databay.co:8888 \
     https://databay.com/cdn-cgi/trace

Pricing for Aruba: 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 Aruba at no extra cost. See documentation.

Network performance

Network-wide operating targets for Aruba 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.

Field guide

Need rotating IPs with city and ASN targeting? Get residential proxies in Aruba (34M+ IPs from $0.90/GB). Testing first? You can browse the live community proxy list for Aruba (refreshed every 5 minutes).

Aruba proxy coverage, in numbers

Databay's June 9, 2026 paid-network catalogue assigns 12,116 addresses to Aruba. That places Aruba number 116 of 195 locations worldwide and number 14 of 27 in North America. The Aruba allocation represents <0.05% of the global catalogue and 0.22% of the North America total. For Aruba, those figures describe catalogue breadth, not a count of exits guaranteed online at one moment. The Aruba count also does not establish address ownership, consent, residential status, latency, reputation, city accuracy, or acceptance by a destination. Use the live Aruba coverage panel on this page to see which Databay network types currently report service, then confirm the observed exit before relying on a result. Aruba pricing is determined by network and plan rather than by inflating the country count into a performance promise.

Isolate the Aruba network-origin variable

The gateway flag countryCode-aw requests an exit geolocated to Aruba, subject to current supply and the selected network. For Aruba, it changes one input: the apparent network origin seen by the destination. An exit geolocated to Aruba 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 Aruba, write down the hypothesis first and hold those other inputs constant. Check the Aruba 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 Aruba matters, validate that narrower result separately; country success does not prove subnational accuracy.

Plan Aruba sessions from the actual pool scale

Aruba has a limited but material published allocation. Design Aruba 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 Aruba filter returns no suitable exit, broaden the test or stop rather than claiming unavailable coverage. Aruba 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 Aruba pool rather than rotating around it. Record Aruba failures as data; do not hide them with unlimited retries.

Aruba in its North America comparison set

The immediately larger North America catalogue entry than Aruba is Saint Lucia at 13,395 addresses, and the next smaller is Puerto Rico at 11,072. In the Aruba comparison set, the regional leader is United States of America with 3,203,665. These Aruba capacity comparisons are useful only when the workload could legitimately run from more than one country. Choose Aruba when the research question specifically needs a network-origin observation from Aruba. Choose a different country from Aruba only when it is a valid control or a separate market in the study. Combining Aruba observations with other countries in one unlabeled dataset makes regional differences impossible to interpret. Preserve the requested Aruba route, observed exit country, network type, timestamp, source, response class, and validation outcome on every retained record.

A reproducible Aruba validation checklist

Before using a Aruba result, capture five things: the canonical source URL and permission basis; the Databay network and countryCode-aw 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 Aruba check from a controlled reference and label missing, blocked, challenged, stale, or personalized responses instead of treating them as ordinary content. For a consequential Aruba price, availability, advertising, search, compliance, or product decision, obtain a second authorized source or local review. This Aruba workflow makes the 12,116-address catalogue figure useful as coverage context without pretending it proves a resident's experience.

Aruba proxies

Frequently asked questions

How many proxy IPs does Databay have in Aruba?
Databay offers 12,116+ residential and mobile proxy IPs in Aruba, with city-level and ASN geo-targeting.
What types of proxies are available in Aruba?
Databay provides residential and mobile proxies in Aruba, all with rotating and sticky sessions over HTTP, HTTPS, and SOCKS5.
Which networks and ASNs are covered in Aruba?
Coverage in Aruba spans 1 autonomous systems across 2 network types, selectable by ASN in the proxy username.
How do I authenticate with Databay proxies?
Authentication is by username and password over the gateway. Country, city, ASN, and session are all selected with flags in the username, so no IP allowlisting is required.
Which protocols are supported?
HTTP, HTTPS, and SOCKS5 are supported on the same gateway, with both rotating and sticky sessions.
Is there an API?
Yes. Proxies are delivered through a single gateway endpoint; pool, geo, and session are controlled entirely through the username flags, so any HTTP client or scraping framework works unchanged.
How do I get started?
Create an account, choose a plan, and the dashboard issues gateway credentials you can use immediately.
Do you offer reseller or volume plans?
Yes. Volume and reseller pricing is available for larger commitments. Contact sales for a quote.

Start using Aruba proxies

Review live Aruba coverage and access the published pool under the selected plan and service limits.

Pricing, order minimums, and traffic validity vary by product.