Compare mobile and residential proxy options for Burkina Faso. Confirm eligible routes and the required network type before adding funds. The carrier and city information below is regional reference material, not a promise of available supply.
Carrier-grade NAT means many real subscribers in Burkina Faso share each mobile IP - the network behavior platforms associate with genuine users, not datacenters.
Mobile and datacenter describe different network types. Confirm the actual exit ASN and test your target; neither type guarantees access.
Residential and cellular routes have separate inventory. A connected phone can use home Wi-Fi, so device type alone does not prove a cellular exit.
Check geolocation, ASN and protocol behavior on your actual route. A proxy does not guarantee browser identity, reputation or acceptance by a website.
Regional carrier reference only. These names do not mean we currently have routes from these carriers:
Regional city reference only. Check the dashboard for cities with eligible routes:
Mobile money dominates payments in Burkina Faso, with Orange Money and Moov Money used far more widely than card rails. Burkinabe mobile IPs let fintech and QA teams verify onboarding flows, geo-restricted promotions and USSD-adjacent web experiences exactly as local subscribers on Orange or Moov networks see them, while residential IPs cover fixed-line perspectives.
Advertisers targeting Francophone West Africa need to confirm that campaigns actually serve correctly in Ouagadougou rather than defaulting to France or Ivory Coast placements. Route through real Burkinabe mobile and residential IPs to check Google.bf results, in-app ad delivery and landing-page geo logic, with free rotation to sample many local vantage points.
Much of Burkina Faso's online activity runs through news portals such as lefaso.net and Burkina24, plus Facebook and WhatsApp-based selling and local classifieds. Burkinabe IPs let research and scraping teams collect prices, listings and sentiment from these sources without geo-blocks, using HTTP or SOCKS5 from any stack.
Rotate on every request, on a timer, or hold a sticky session - set it in the proxy username or via the API. Rotation depends on eligible routes being available and does not guarantee a new public IP.
The gateway supports HTTP, HTTPS CONNECT and SOCKS5 TCP, without SOCKS5 UDP. Check country availability before configuring scrapers or browsers (guide), and automation frameworks.
Check the live availability panel and the dashboard before adding funds. A country guide is not a stock guarantee. An unavailable or failed stock check must not be treated as a working route.
Only when that filter has eligible live stock. The carrier and city lists below describe the region; they are not an inventory list.
No. A sticky session requests the same eligible route, but reconnects and carrier networks can change the exit IP. Validate the required behavior before scaling.
The pool gateway supports HTTP, HTTPS CONNECT and SOCKS5 TCP. SOCKS5 UDP is not supported. Protocol support does not guarantee country availability or target-site acceptance.
No. Confirm your country, network type and target requirements first. Adding funds does not reserve an IP, carrier or country.
Confirm the country, network type and target requirements in the dashboard. Adding funds does not reserve a route; if stock is unavailable, wait before purchasing traffic for this country.