Two timings
Shows TCP connect time and total request latency through the proxy separately, so you can see which leg is slow.
Before you hand a proxy to an automation tool, test it: does it connect, how long does it take and where does it exit? Results are laid out by latency, so problem proxies stand out.
Test results appear here
Shows TCP connect time and total request latency through the proxy separately, so you can see which leg is slow.
Each proxy gets a latency bar, so fast and slow ones are obvious.
Switch to IP lookup for the region and carrier of your IP or any other.
No sign-up and nothing to install.
One per line, up to 10.
SOCKS5 or HTTP is detected automatically.
Choose proxies by latency and exit region.
Not necessarily. Total latency covers our server to the proxy, the proxy to the destination, and the TLS handshake. A high connect time usually means geographic distance; a fast connect with high total latency points to the proxy's exit or upstream network.
Proxies that pass can go straight into your automation tool or antidetect browser. For accounts that need a long-term fixed exit, choose static ISP proxies and periodically re-test that the exit IP stays the same.
Congestion, TLS negotiation and the echo service all affect timing. Compare several tests under similar conditions alongside success rate and exit IP.