Africa routing coverage

Uganda Proxies

3,317+ residential and mobile proxy IPs in Uganda. 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

2 network types · 9 ASNs

  • Uganda3,317 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.
3,317+
Published IPs in Uganda
2
Live network types
9
Autonomous systems
#47
Pool rank in Africa
3,317+ published IPs in Uganda99.9%+ uptime targetCountry, city, GPS & ASN targetingHTTP, HTTPS & SOCKS5Databay Trust Center
Live coverage

Uganda network coverage

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

Geo-targeting

Target Uganda down to the city and ASN

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

  • Country routing

    One flag, countryCode-ug, requests an exit geolocated to Uganda, 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 9 autonomous systems covered in Uganda

  • AS20294 MTN-
  • AS328727 KAMPALA-SITI-CABLE
  • AS329415 Savanna-Fibre-Limited
  • AS37063 RTL-AS
  • AS37075 ZAINUGAS
  • AS37113 tangerine-ug-as
  • AS37273 BCS
  • AS327687 RENU
  • AS328198 BLUECRANE

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

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

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

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

Network performance

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

Uganda proxy coverage, in numbers

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

What countryCode-ug changes

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

Plan Uganda sessions from the actual pool scale

Uganda is one of the catalogue's smallest allocations. Use the Uganda pool for focused country-origin checks, not broad rotation. Expect repeat Uganda exits, validate availability before a long run, keep concurrency low, and retain a controlled comparison from another route. A zero-result Uganda filter is evidence to stop or redesign the test, not a reason to increase pressure. Uganda 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 Uganda pool rather than rotating around it. Record Uganda failures as data; do not hide them with unlimited retries.

Uganda in its Africa comparison set

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

A reproducible Uganda validation checklist

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

Uganda proxies

Frequently asked questions

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

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

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