Search docs

Search the documentation

Dashboard
For LLMs

Datacenter Proxies

High-throughput US datacenter proxies at ~30 ms response — built for fast scraping and price monitoring on non-sensitive targets where speed and cost matter most.

Specs

  • Pool: 6,000+ USA IPs
  • Coverage: US only (country-level targeting)
  • Typical response time: ~30 ms
  • Protocols: HTTP, SOCKS5 (SOCKS5 UDP ASSOCIATE supported)
  • Sessions: rotating or sticky (up to 2 hours)
  • Concurrency: up to 50,000 concurrent connections (per-GB); 9,000 on the time-based Unlimited tier — higher on request
  • Best for: fast scraping and e-commerce price monitoring

Connect

Gateway: dc.flashproxy.io — port 777 (HTTP) / 666 (SOCKS5).

# Rotating — a fresh IP on every request
curl -x "http://USERNAME:[email protected]:777" https://api.ipify.org
# SOCKS5
curl -x "socks5://USERNAME:[email protected]:666" https://api.ipify.org

Request parameters

Datacenter is US-only, so there's no country parameter to set. Two options are still available, encoded into the username:

ParameterFormatExampleNotes
Sticky sessiontime-<minutes>-session-<id>time-30-session-a1b2c3d4Up to 120 min; omit for a rotating IP
Pin a specific IP-ip-<address>-ip-0_0_0_0Target one exact IP from the pool — see Geo-targeting

For the complete reference — every accepted value — see the API reference.

Examples

# Rotating — a fresh US IP each request
curl -x "http://USERNAME:[email protected]:777" https://api.ipify.org
# Sticky — hold the same IP for 30 minutes
curl -x "http://USERNAME-time-30-session-a1b2c3d4:[email protected]:777" https://api.ipify.org
# Pin one exact IP
curl -x "http://USERNAME-ip-0_0_0_0:[email protected]:777" https://api.ipify.org

Sessions

Use rotating for maximum IP diversity or sticky to keep the same IP across a session — see Rotating & sticky.

Pricing

Per-GB, with volume discounts as you scale, and a time-based Unlimited tier. See Datacenter pricing.

Quickstart

  1. Buy a Datacenter plan in the dashboard.
  2. Copy your username and password.
  3. Use the connection string above.