Skip to content
Status · Latency · Exit

Proxy speed and connectivity tester

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.

  • Proxy speed test
  • Connectivity check
  • Exit IP location
  • SOCKS5 / HTTP
One per line, up to 10 per run
Protocol

Test results appear here

Two timings

Shows TCP connect time and total request latency through the proxy separately, so you can see which leg is slow.

Latency at a glance

Each proxy gets a latency bar, so fast and slow ones are obvious.

Location lookup included

Switch to IP lookup for the region and carrier of your IP or any other.

How it works

No sign-up and nothing to install.

  1. Paste proxies

    One per line, up to 10.

  2. Run the test

    SOCKS5 or HTTP is detected automatically.

  3. Compare results

    Choose proxies by latency and exit region.

Does high latency always mean a slow proxy?

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.

Using results in automation

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.

Still deciding? Start here.

A few things to know before you connect.

Visit the help center

Congestion, TLS negotiation and the echo service all affect timing. Compare several tests under similar conditions alongside success rate and exit IP.

Your next move. Connected.

Start with the right proxy. Take your work further.