Datacenter proxies. 10× cheaper per GB.
Direct backbone routing across 13+ regions via standard HTTP/HTTPS proxy. Sub-second responses, unlimited concurrency, sticky sessions on demand. Billed by bandwidth — from $0.42/GB at scale.
Pay only for bandwidth · unlimited concurrency · cancel anytime
# Connect via datacenter proxy, US exit
$ curl --proxytunnel \
--proxy "https://datacenter.scrapingant.com" \
--proxy-user "customer-USER-country-us:PASS" \
"https://target-site.com"import requests
proxy = (
'http://customer-USER-country-us:'
'PASS@datacenter.scrapingant.com:8080'
)
r = requests.get(
'https://target-site.com',
proxies={'http': proxy, 'https': proxy},
verify=False,
)
print(r.text)import { HttpsProxyAgent } from 'https-proxy-agent';
const agent = new HttpsProxyAgent(
'http://customer-USER-country-us:' +
'PASS@datacenter.scrapingant.com:8080',
);
const res = await fetch(
'https://target-site.com',
{ agent, dispatcher: agent },
);
console.log(await res.text());Why datacenter.
When the target doesn't aggressively block cloud IPs, datacenter proxies are dramatically cheaper, faster, and easier to scale.
Standard HTTP proxy. No SDK, no API client.
Point any HTTP library at datacenter.scrapingant.com:8080 (or :443 for HTTPS) and pack country / session into the username. Password is your datacenter key. Same syntax as the residential proxy pool — easy to switch products without rewriting client code. Want managed Headless Chrome rendering and retries on top? Use the Web Scraping API with proxy_type=datacenter.
- Drop into curl, requests, axios, fetch — anywhere
- HTTP on
:8080, HTTPS on:443 - Username syntax matches residential — swap host to switch product
Sub-second on the happy path.
Datacenter exits ride backbone fiber from major cloud regions to the open internet — no last-mile residential hop, no consumer ISP variance. For non-aggressive targets, that means typical p50 round-trips around 700ms and predictable tail latency.
- Direct routing — no last-mile latency
- Predictable p99 — fewer slow tail requests
- Fast enough to power realtime SERP and price-comparison APIs
13+ regions, pick your exit.
Datacenter footprints across the US, UK, Canada, Germany, France, Italy, Spain, Austria, Romania, Hong Kong, Singapore, Brazil, India — and growing. Pin a country with country-us in the proxy username to route through that region.
- 13+ datacenter regions worldwide
- ISO country pinning via
country-usin the username - Same syntax across all regions — easy to switch
Burst hundreds of connections in parallel.
No concurrency cap on the datacenter plan — there's no per-IP rate limit you have to manage from your code. Push your queue at the cluster and we distribute exits across the 50K+ IP pool. Crank your worker pool until your bandwidth tier is the limit, not the proxy. Hitting walls on tougher targets? Switch to rotating residential proxies for the same flat-username scheme at consumer-ISP exit points.
- No client-side IP rotation logic to maintain
- Sticky sessions via
sessionid-anythingwhen you need them - Failed connections never count against bandwidth
What teams use datacenter proxies for.
High-volume targets where speed and cost matter more than residential disguise.
SEO & SERP at scale
Daily keyword tracking, rank monitoring, SERP feature audits — millions of queries, low cost per GB.
Talk to sales →Broken-link & SEO audits
Crawl every URL on a site, check status codes, validate redirects — burst hundreds of parallel connections.
Talk to sales →Public data archival
Historical snapshots, news monitoring, government records — non-aggressive sites, high request volume.
Talk to sales →Content & price mirrors
Mirror catalog data, syndication feeds, public APIs — predictable targets, predictable cost.
Talk to sales →AI training datasets
Bulk fetch open-web pages for fine-tuning corpora — concurrency-friendly, cost-friendly.
Talk to sales →Internal QA & monitoring
Synthetic checks across regions — verify your own site renders correctly from US, EU, APAC.
Talk to sales →Bandwidth tiers, no request metering.
Pay only for the bandwidth you use. Unlimited concurrency, no setup fees, no per-request math. Cancel anytime.
- Unlimited concurrency
- 100 GB bandwidth
- Email support
- Unlimited concurrency
- 200 GB bandwidth
- Priority support queue
…and custom plans for higher volume.
- Unlimited concurrency
- 400 GB bandwidth
- Priority support
- Unlimited concurrency
- 800 GB bandwidth
- Account manager
- Unlimited concurrency
- 1200 GB bandwidth
- Account manager
- Unlimited concurrency
- 2400 GB bandwidth
- Account manager
What teams are saying.
From solo developers shipping side projects to enterprise pipelines at Fortune 500s.
★★★★★ 5.0 on Capterra →★★★★★“Onboarding and API integration was smooth and clear. Everything works great. The support was excellent.”
★★★★★“Great communication with co-founders helped me to get the job done. Great proxy diversity and good price.”
★★★★★“This product helps me to scale and extend my business. The setup is easy and support is really good.”
Frequently asked questions.
Still curious? Get in touch with our team — we usually reply within hours.
What is a datacenter proxy?
A datacenter proxy is an HTTP/HTTPS proxy whose exit IPs come from cloud / hosting providers, not consumer ISPs. Because the bandwidth runs through backbone fiber from a cloud region, datacenter proxies are fast and cheap ($0.44–$0.60 / GB) but easier for anti-bot systems to flag than residential proxies. ScrapingAnt's rotating datacenter pool spans 50K+ IPs across 13+ regions and is the right primitive for non-aggressive targets — public APIs, news, SEO crawls, internal monitoring, and most B2B scraping.
When should I use datacenter proxies vs residential?
Use datacenter for non-aggressive targets — public APIs, news sites, government records, SEO crawls, broken-link audits, internal monitoring. They're ~10× cheaper per GB ($0.44–$0.60 vs $3.50–$6) and faster, and you can burst hundreds of concurrent connections.
Switch to residential proxies when the target uses Cloudflare / Akamai / PerimeterX or actively blocks cloud IP ranges (Amazon, ticketing, sneakers, social). Same proxy username syntax — just point at residential.scrapingant.com instead.
How do I connect to the rotating datacenter proxy?
Point your HTTP client at datacenter.scrapingant.com:8080 (HTTP) or :443 (HTTPS). Username encodes parameters: customer-USER-country-us; password is your datacenter proxy key from app.scrapingant.com/datacenter. Works with curl, requests, axios, or any standard HTTP / proxy library — no SDK. Every request gets a fresh datacenter IP from the pool by default.
Which countries and regions can I target?
Datacenter exits in US, UK, CA, HK, SG, ES, FR, IT, DE, AT, RO, BR, IN — list grows over time. Pick the country that fits your target with customer-USER-country-us; without a country parameter, requests route through the default pool. For city / state targeting at the consumer-ISP level (e.g. state-us_california, city-us_los_angeles), use the residential proxy pool.
Do sticky sessions work the same on datacenter as residential?
Yes. Append -sessionid-anything to the username and we pin the same datacenter exit for that string until idle expiry (~10 min). Useful when a target site bakes IP into a cookie or login session — change the value to rotate, drop it for per-request rotation.
Are concurrent connections limited on the datacenter pool?
No. Run as many parallel connections as your worker pool can manage — there's no per-account concurrency cap, no per-IP rate limit you have to enforce. Push your queue at the cluster and we distribute exits across the 50K+ IP pool. Datacenter is the natural choice for high-concurrency batch scrapes.
How are datacenter proxies billed — per request or per GB?
Per GB of bandwidth used, same scheme as residential — but at much lower per-GB rates. Plans start at 50 GB for $30 ($0.60/GB) and scale to 2.4 TB for $1056 ($0.44/GB). No per-request fees, no setup costs. Bandwidth pricing is separate from the credit-based Web Scraping API — proxies bill by GB, the API bills per request. Contact us for higher volume.
When should I use the datacenter proxy directly vs the Web Scraping API?
Use the datacenter proxy when you already have your own scraper / browser stack and just need clean, fast exits. Use the Web Scraping API when you also want managed Headless Chrome rendering, retries, and a single endpoint that accepts a URL and returns rendered HTML / Markdown. The proxy is the primitive; the API is the managed layer on top — same datacenter pool underneath when you set proxy_type=datacenter.
Need a custom datacenter plan?
Higher monthly bandwidth, dedicated regions, custom SLA, or private IP pools — drop us a line and a real human gets back within a few hours.
“Our clients are pleasantly surprised by the response speed of our team.”
