All about proxies
All about datacenter proxies
Datacenter proxies are assigned from hosting networks. They are a good fit for internal APIs, documentation sites, and other targets that do not block hosting ranges.
When to use them
Pick datacenter when latency and cost matter more than looking like home or mobile traffic, and a test URL still returns the real page.
When to switch
If you receive block pages, empty bodies, or the wrong geo view, move that job to residential or mobile and re-run the same URL.
Quantity
Datacenter plans are sold by IP count. Keep a simple map of which IP is used for which job so failures are easy to isolate.
Instructions
1. Validate on one IP
Configure one datacenter endpoint and fetch a known-good URL.
2. Measure
Record status codes and time-to-first-byte against the same target you will use in production.
3. Add IPs only after the parser is stable
Do not scale concurrency until error rates stay low.
curl -x http://USERNAME:PASSWORD@HOST:PORT https://example.comRelated sections
High-speed fetches on datacenter proxies
Throughput first, but only after the canary page is real — not a block.
How to check your proxy address
Confirm credentials and the exit IP before you put a job into production.
HTTP 522 connection timed out
522 means the edge or origin did not complete the connection in time. Isolate where it stalled.
All about residential proxies
ISP-style IPs for research, collection, and market checks that need geographic coverage.
If you still need help, message us on Telegram or email. Include your account email and, if you have one, your order ID.
Message us
Reach support on Telegram, email, phone, or the contact form. Include your account email and, if you have one, your order ID.