Search docs

Search the documentation

Dashboard
For LLMs

Shared ISP Proxies (US)

ISP-hosted US IPs that combine residential authenticity with datacenter-grade ~39 ms latency — built for ad verification, SEO, sneakers, and any workflow that needs residential trust at near-datacenter speed.

Specs

  • Pool: 22,000+ USA IPs
  • Coverage: US only (country-level targeting)
  • Typical response time: ~39 ms
  • Protocols: HTTP, SOCKS5 (SOCKS5 UDP ASSOCIATE supported)
  • Sessions: rotating or sticky (up to 2 hours)
  • Concurrency: up to 9,000 concurrent connections — higher on request
  • Best for: ad verification, SEO monitoring, sneakers

Connect

Gateway: beta.flashproxy.io — port 30 (HTTP) / 31 (SOCKS5).

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

Request parameters

Shared ISP (US) 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]:30" https://api.ipify.org
# Sticky — hold the same IP for 30 minutes
curl -x "http://USERNAME-time-30-session-a1b2c3d4:[email protected]:30" https://api.ipify.org
# Pin one exact IP
curl -x "http://USERNAME-ip-0_0_0_0:[email protected]:30" 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 Shared ISP pricing.

Quickstart

  1. Buy a Shared ISP (US) plan in the dashboard.
  2. Copy your username and password.
  3. Use the connection string above.