Why is my proxy slow, and how do I measure it?
In short: A proxy adds a detour, and the slowest leg of it sets the pace: distance, the target site and your own connection all count. We make no speed promise. The one number in our terms is 2 Mbit/s: an IP below it within 24 hours of payment is refunded once we confirm it.
Speed and latency are two different things, and people often mean one while measuring the other. Latency is how long a request takes to start answering. Speed, or throughput, is how much data moves per second once it has started. A proxy changes both, because your traffic takes an extra stop.
What decides it
| Factor | Why it matters |
|---|---|
| Distance | A request goes from you to the proxy and from the proxy to the site. A proxy far from you, or far from the site, adds delay on one leg or the other. |
| The target site | A slow or busy site is slow through any address. Test against more than one site before blaming the proxy. |
| Your own connection | The proxy cannot move data faster than your line, and Wi-Fi in a weak spot is a common limit. |
| The client | A browser extension, a VPN left on, or a tool that opens many connections can slow a test. |
| Load and routes | Terms of Service, section 2, says availability, speed and performance vary with technical, provider and network factors. |
Static ISP addresses run on server infrastructure, which is the subject of ISP versus datacenter proxies. We have not measured a figure for you, so take the number from your own test.
Measure it through the proxy
Run a speed test in a browser that uses the proxy, and run the same test without it, from the same place and time. The difference is the cost of the detour. Keep a screenshot of the result through the proxy.
For latency, one curl request prints where the time goes. Replace the four values with the
ones from My Proxies in your dashboard:
curl -x http://HOST:PORT -U LOGIN:PASSWORD -o /dev/null -s \
-w "connect %{time_connect}s, first byte %{time_starttransfer}s, total %{time_total}s\n" \
https://example.com
Run it three or four times and compare, because one reading says little. If it hangs or fails instead of printing times, see proxy connection timed out. Without a terminal, our proxy checker times one request through the proxy in milliseconds, which is a latency reading, not a throughput test.
The one number we commit to
Section 1 of the Refund Policy lists low speed as a defect: below 2 Mbit/s, shown by a speed test run through the proxy, which we repeat on our side. The IP must show it within 24 hours of payment, and we must confirm it. A slow target site, your own network or a client setting is your side, and section 2 gives no refund for it. A confirmed IP is refunded to your balance, not replaced.
If it is slow but above 2 Mbit/s
That is not a listed defect, but it is worth a message. Write to support@proxyjam.com with the order number, the two speed test results and the time of the test. If the page still does not load, work through proxy not working first. The ISP proxies page describes what you are connecting to.
