Cheap Shared Proxies from $0.20/proxy at 25

curl -x http://USER:PASS@203.0.113.42:4443 https://api.ipify.org

# SOCKS5 on the same credential
curl --socks5-hostname USER:PASS@203.0.113.42:1443 https://api.ipify.org

import requests

PROXY = "http://USER:PASS@203.0.113.42:4443"
r = requests.get("https://api.ipify.org",
                 proxies={"http": PROXY, "https": PROXY}, timeout=30)
print(r.text)

# 3 GB per proxy, pooled across the order - a busy address is covered by a quiet one
big = requests.get("https://example.com/large-file",
                   proxies={"https": PROXY}, stream=True)
print(sum(len(c) for c in big.iter_content(8192)), "bytes")

// `dispatcher` is what routes fetch. { agent } is accepted and ignored.
import { fetch, ProxyAgent } from "undici";

const dispatcher = new ProxyAgent("http://USER:PASS@203.0.113.42:4443");
const res = await fetch("https://api.ipify.org", { dispatcher });
console.log(await res.text());

How many people share each IP?

Up to five. The cap is applied when addresses are allocated, so it is a published number you can hold us to. Other customers on the address do not get access to your traffic or credentials.

Can other users see my traffic?

No. Sharing an exit address does not expose traffic between users. What is shared is the address's reputation with destination sites.

What locations are available?

The United States, Italy, Spain, or an even split between Italy and Spain, chosen at checkout. The United States is the default; Italian and Spanish stock is limited. For other markets, the residential product covers 170+ countries.

Is bandwidth limited?

Yes. The allowance is 3 GB per proxy, pooled across your order, so 100 proxies share 300 GB and a busy address is covered by a quiet one. Run low and you can add bandwidth to the pool at any time from your dashboard, without changing plan. If bandwidth rather than address count is what you need, dedicated proxies have unlimited bandwidth per IP and rotating is sold by the gigabyte.

Do you offer free proxies?

Yes. Eligible accounts get a small free allocation, with no card required.

Can I use IP whitelisting instead of a password?

Yes. IP whitelisting is available on every product: register your server's public address and connect with no credentials, or use username and password when your source IP moves. One credential works on every product your account holds a plan for.

Do shared proxies rotate?

No. These are static addresses: the list you are allocated is the list you have, and each request leaves from whichever of your addresses you connect to. Rotating client-side, iterating over your own list, is often sensible; if you want rotation as a service, with one endpoint and selection handled behind it, that is the rotating product, on the same owned blocks.

What if a website blocked my shared IP before I ever used it?

It can happen: a neighbor may have used the address against that target before you, and blocks are per target, so an address can pass an IP checker and still fail on one site. Retry from another address in your allocation first, and keep per-address request rates modest. Shared Datacenter plans include no IP replacements, so if particular addresses stay dead for one target, move that target to dedicated, whose plans can include a monthly replacement allowance. If the pattern repeats across your whole allocation on one target, the target is classifying the range or the sharing itself, and dedicated or residential is the answer.

Can I mix shared and dedicated proxies in one account?

Yes, and it is a sensible pattern. Both are static products with the same ports, protocols and credentials, so a client that works against one works against the other unchanged. Run bulk, tolerant work on shared, put the targets that punish shared history on dedicated addresses, and the only thing that changes in your code is the IP list.

Are shared proxies suitable for sneaker sites, ticketing or social platforms?

No. Those targets combine aggressive hosting-range classification with per-address history scoring, which hits shared datacenter proxies on both counts. Residential is the product in our catalog with a realistic footing there, and even residential is refused sometimes. Shared belongs on tolerant targets (development, QA, monitoring, moderate-volume scraping), where its price is the point.

Will other users slow my proxies down?

Contention is possible in principle, since you share a machine's egress address with up to four other customers, and the occupancy cap exists to keep it rare. In practice the difference you are most likely to notice against dedicated is not speed but the occasional target-side challenge inherited from a neighbor, which is a retry rather than an outage. If your workload cannot tolerate that, dedicated is the right tier.