Locations

ISP geo targeting works differently from the gateway products: country (and city, in select markets) is picked at order time. Each IP in your list has a fixed location for its lifetime.

Coverage

Tier	Countries	City selection
Tier 1 (deep pools, city-level)	US, GB, DE, FR, JP, KR, BR, CA, AU, IN, NL, SG	Yes
Tier 2 (country only)	30+ additional countries	No

Live coverage and per-city availability are visible on the order page; the API returns the same data:

curl -H "Authorization: Bearer API_KEY" \
     https://api.helodata.com/v1/isp/inventory

Returns per-country quantity available, monthly price, and the cities offered.

How to pick

At order time you choose:

1. Country — required
2. City — optional, only in tier-1 countries
3. Quantity — min 1, max 5,000 per order

Mixed batches (e.g. 50 US + 50 DE) require placing two orders. Each batch tracks its country independently.

Once an IP is provisioned, its location is fixed

The IP keeps the same country, city, ASN, and carrier until it's released. The metadata is visible in the dashboard and the CSV/JSON downloads:

{
  "ip": "198.51.100.42",
  "country": "US",
  "city": "New York",
  "asn": 7922,
  "carrier": "Comcast"
}

If you need different cities later, place a new order. There is no "change location" operation.

City fallback when ordering

If a city is over-subscribed at order time, the dashboard offers two choices:

• Wait — your order queues until inventory frees up (typically <24h)
• Substitute — automatically pick the next-closest city with inventory

Substitutions are flagged in the order email and in the dashboard so you can audit them.

ASN at order time (tier-1 only)

In tier-1 countries you can additionally request a specific ASN — Comcast vs Charter, Deutsche Telekom vs Vodafone, etc. Pricing varies by ASN: premium carriers cost ~20% more.

curl -H "Authorization: Bearer API_KEY" \
     "https://api.helodata.com/v1/isp/inventory?country=us&asn=7922"

ASNs available per country are returned by the inventory endpoint above.

What about subnets?

helodata avoids issuing more than 4 IPs from the same /24 subnet to a single customer's batch. This keeps the IPs harder for target sites to correlate. If you specifically want a contiguous subnet (e.g. for testing CDN edge behavior), contact [e-mail] — /29 blocks can be reserved on annual contracts.