Africa routing coverage

Cape Verde Proxies

10,764+ residential proxy IPs in Cape Verde. 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.

Africa coverage field

1 network types · 1 ASNs

  • Cape Verde10,764 IPs
  • Morocco646,631 IPs
  • South Africa592,536 IPs
  • Egypt524,973 IPs
  • Algeria309,306 IPs
  • Nigeria38,692 IPs
Published Africa pool counts from the locations dataset, updated . Live availability can change.
10,764+
Published IPs in Cape Verde
1
Live network types
1
Autonomous systems
#26
Pool rank in Africa
10,764+ published IPs in Cape Verde99.9%+ uptime targetCountry, city, GPS & ASN targetingHTTP, HTTPS & SOCKS5Databay Trust Center
Live coverage

Cape Verde network coverage

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

Geo-targeting

Target Cape Verde down to the city and ASN

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

  • Country routing

    One flag, countryCode-cv, requests an exit geolocated to Cape Verde, 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 Cape Verde

  • AS37517 CVTS1

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

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

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

Pricing for Cape Verde: residential from $0.90/GB (PAYG $2.75/GB), datacenter from $0.50/GB (volume), mobile from $2.50/GB. All tiers include Cape Verde country targeting at no extra cost. See documentation.

Network performance

Network-wide operating targets for Cape Verde 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 Cape Verde (34M+ IPs from $0.90/GB). Testing first? You can browse the live community proxy list for Cape Verde (refreshed every 5 minutes).

Reading the published Cape Verde address count

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

Build a controlled Cape Verde location test

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

Plan Cape Verde sessions from the actual pool scale

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

Cape Verde in its Africa comparison set

The immediately larger undefined catalogue entry than Cape Verde is Congo at 11,281 addresses, and the next smaller is Cameroon at 10,444. In the Cape Verde comparison set, the regional leader is Morocco with 646,631. These Cape Verde capacity comparisons are useful only when the workload could legitimately run from more than one country. Choose Cape Verde when the research question specifically needs a Cape Verde network-origin observation. Choose a different country from Cape Verde only when it is a valid control or a separate market in the study. Combining Cape Verde observations with other countries in one unlabeled dataset makes regional differences impossible to interpret. Preserve the requested Cape Verde route, observed exit country, network type, timestamp, source, response class, and validation outcome on every retained record.

A reproducible Cape Verde validation checklist

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

Cape Verde proxies

Frequently asked questions

How many proxy IPs does Databay have in Cape Verde?
Databay offers 10,764+ residential proxy IPs in Cape Verde, with city-level and ASN geo-targeting.
What types of proxies are available in Cape Verde?
Databay provides residential proxies in Cape Verde, all with rotating and sticky sessions over HTTP, HTTPS, and SOCKS5.
Which networks and ASNs are covered in Cape Verde?
Coverage in Cape Verde spans 1 autonomous systems across 1 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 Cape Verde proxies

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

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