Africa routing coverage

Benin Proxies

13,488+ residential proxy IPs in Benin. 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 · 5 ASNs

  • Benin13,488 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.
13,488+
Published IPs in Benin
1
Live network types
5
Autonomous systems
#17
Pool rank in Africa
13,488+ published IPs in Benin99.9%+ uptime targetCountry, city, GPS & ASN targetingHTTP, HTTPS & SOCKS5Databay Trust Center
Live coverage

Benin network coverage

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

Geo-targeting

Target Benin down to the city and ASN

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

  • Country routing

    One flag, countryCode-bj, requests an exit geolocated to Benin, 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 5 autonomous systems covered in Benin

  • AS37136 ETISALAT-AS
  • AS28683 SBIN
  • AS37090 ISOCEL
  • AS37424 Spacetel
  • AS328098 JENY-SAS-AS

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

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

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

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

Network performance

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

Benin coverage: scale before slogans

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

What countryCode-bj changes

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

Plan Benin sessions from the actual pool scale

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

Benin in its Africa comparison set

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

A reproducible Benin validation checklist

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

Benin proxies

Frequently asked questions

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

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

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