Check proxies in bulk: status, exit IP and latency
Updated:
This proxy checker tests up to 100 proxies per run. Paste them into the form above, one ip:port:user:pass line each, and every row comes back as working or not working, with the exit IP websites will see and the response time. Passwords are not stored. The sections below explain each result and what to do about it.
Format: ip:port or ip:port:user:pass. Passwords are only used for this check and never stored. http:// socks4:// socks5:// (max 100 lines)
Results and what to do next
A failed row is not just a red mark; the type of failure tells you which layer to look at.
| Result | Meaning | Next step |
|---|---|---|
| Working | Connected and logged in | Use it, then confirm inside your profile with my IP |
| Timeout | No reply within the wait limit | Check again later and check whether the proxy has expired; see proxy timeout |
| 407 auth failed | Username or password not accepted | Copy the credentials again and look for spaces or swapped fields; see the 407 guide |
| Connect failed | The ip:port could not be reached | Look for typos in IP and port; the proxy may be expired or down |
Exit IP and latency, explained
The exit IP is the address the outside world receives. With a static proxy it should equal the proxy's own IP, and with ProxyV4 it stays the same after renewal. If it shows something else, you are not testing the proxy you think you are.
Latency is the round trip from our checker, through the proxy, and back. Distance dominates it: a UK proxy will normally show a higher number than a Singapore one. A high value is not a fault in itself; compare proxies in the same location, or measure against real sites with the proxy speed test.
Getting a clean run
- Copy the lines from your provider's dashboard; on ProxyV4 they sit under Orders.
- Keep each line exactly
ip:port:user:pass, with no extra spaces or characters. Lists in another layout can be rewritten with the proxy format converter. - Have more than 100? Split the list and check it in batches.
Works here, fails in your app
- Check the order's status and expiry in the dashboard. An expired proxy stops accepting connections; renew before the end date to keep the same IP.
- If the checker says Working but your app fails, the app configuration is the problem. Select HTTP as the type, enter username and password, then open my IP inside that profile.
- If a ProxyV4 proxy keeps failing, open a support ticket with the failing lines. Technical failures are covered by the refund policy.
- Need to test from a server or a script instead? How to check a proxy covers browser, command-line and antidetect methods.
Frequently asked questions
Does the proxy checker cost anything?
No. It is free, with up to 100 proxies per run.
What input format does it accept?
One proxy per line as ip:port:user:pass. Other layouts may not be recognised, so convert them first.
Do you keep the passwords I paste?
No. Passwords are not stored.
The proxy passes here but fails in my antidetect browser. Why?
Usually the profile has the wrong proxy type or the login was typed incorrectly. Choose HTTP and enter the username and password again.
Why is the latency so high?
Latency rises with the distance between our checker, the proxy and the target. A distant location will show larger numbers.
Proxies that come back green
ProxyV4 private IPv4 and static ISP proxies with unlimited bandwidth, issued automatically within minutes of payment.
Check live prices