ISP & datacenter proxies
Dedicated static IPs, yours for the period you buy. ISP IPs sit on Tier-1 consumer ISP ASNs; datacenter IPs on Datafuel's own hardware. Unlimited bandwidth, never shared, never rotated.
ISP and datacenter proxies are dedicated static IPs. You buy a number of IPs for a period, they are yours alone for that period, and they never change unless you replace them. They do not use the rotating gateways or the username grammar of the residential and mobile networks: each IP is connected to directly.
| ISP | Datacenter | |
|---|---|---|
| IP type: | Registered to Tier-1 consumer ISPs (Comcast, AT&T, Verizon and others) | Datacenter ranges on clean ASNs, mixed /24 subnets |
| Where they run: | Datafuel’s own datacenters, routed through direct carrier agreements | Datafuel’s own hardware |
| Best for: | Account management, long sessions, targets that inspect the ASN | Speed and volume on targets that do not block datacenter ranges |
| Bandwidth: | Unlimited, see fair use below | Unlimited, see fair use below |
| Protocols: | HTTP, HTTPS, SOCKS5 over TCP and UDP | HTTP, HTTPS, SOCKS5 over TCP and UDP |
| Periods: | Daily, weekly, monthly, quarterly, semi-annual, annual; renewable | Same |
| Location choice: | Country, and US state for ISP | Country |
Connecting
Each IP comes with its own port and its own username:password. Connect to the IP directly; there is no gateway and nothing to append to the username.
curl --proxy http://USERNAME:PASSWORD@203.0.113.45:36308 https://ipinfo.io/json
⟧ The response shows the proxy’s own address as your public IP: a static proxy is its exit.
The same IP and port accept HTTP, HTTPS and SOCKS5:
curl --proxy socks5h://USERNAME:PASSWORD@203.0.113.45:36308 https://ipinfo.io/json
⟧ Python, requests
import requests
proxy = "http://USERNAME:PASSWORD@203.0.113.45:36308"
r = requests.get("https://ipinfo.io/json", proxies={"http": proxy, "https": proxy}, timeout=30)
print(r.json())
⟧ Node.js, fetch with undici
import { ProxyAgent, fetch } from "undici";
const dispatcher = new ProxyAgent("http://USERNAME:PASSWORD@203.0.113.45:36308");
const res = await fetch("https://ipinfo.io/json", { dispatcher });
console.log(await res.json());
⟧ Authentication
Two methods, chosen per plan with Set how the proxies authenticate or from the dashboard:
- Username and password, one pair per IP, returned by List a plan’s proxies. Reset the credentials issues new ones for the whole plan at once.
- IP whitelist: requests from the addresses you list are accepted without credentials.
How errors look
Static proxies behave differently from the rotating gateways: they never answer with an error status. A wrong password, a blocked port or a request to a restricted target all end the same way, with the connection closed and no response:
curl: (52) Empty reply from server
⟧ This is deliberate. A proxy that answers 407 or 403 to probes tells scanners that it is a proxy, which gets the IP flagged on the targets you bought it for. The price is that you diagnose from your side:
| You see | Check, in this order |
|---|---|
| Empty reply on every request: | The credentials: copy them again from the dashboard or the API; if the plan uses IP whitelisting, that your source IP is on the list |
| Empty reply on one site only: | The target is on the restricted list; see Limits and restrictions |
| Empty reply on one port only: | The port is blocked by default; see Limits and restrictions |
| Connection timed out: | The plan has expired, or the IP was replaced; check the plan and its proxy list |
| The target blocks or challenges you: | The IP itself is clean on delivery; a target can still have its own rules. Request a replacement from the plan |
The Status codes page applies to the rotating gateways only.
Buying
Quote and order through the User API, or from the dashboard.
- ISP: price a plan, order it, then list its proxies. Add IPs to an existing plan with price an add-on and buy an add-on.
- Datacenter: price a plan, order it, then list its proxies. Add-ons: price, buy.
An order specifies the location, the number of IPs and the period. For ISP IPs the location can be a US state, and the carrier can be chosen where inventory allows; the products and their locations are listed by List products.
Replacing an IP
If an IP is blocked on your target or unusable on delivery, replace it with Replace the IPs (datacenter) or from the dashboard. The old IP is withdrawn and a new one in the same location, and on the same carrier where possible, is assigned with new credentials. Replacements are limited per plan and period; the remaining allowance is shown with the plan. An IP that is unusable on delivery, because it is blocked, misrouted or in the wrong location, is replaced without counting against the allowance.
Bandwidth and fair use
There is no traffic cap and no per-IP bandwidth limit. Sustained very high throughput is rate-limited to protect the hardware the IP shares, and support contacts you directly before that happens. If you need guaranteed throughput, from 300 Mbit/s up to 100 Gbit/s, that is a custom plan: write to sales@datafuel.ai with the location and the throughput you need.
Renewal and expiry
Plans renew automatically unless you turn renewal off from the dashboard or with Turn auto-renew on or off, with notices 7, 3 and 1 days before the charge. When a plan expires, its IPs stop accepting connections and return to the pool after a cooling-off period; they are not reassigned to you later, so renew before expiry if the IPs themselves matter to you.