Ping test for gateways and websites
Standard ICMP ping can’t run from a website, so this tool times the TCP handshake instead: four connections from our server to the address and port you give it, then the average.
Reading the results as a team
Ping is most useful for comparisons: one proxy gateway against another, or today’s figures against last week’s. Enter the host and the port from your dashboard, because the port field starts on the standard HTTPS port and a proxy usually listens on a different one.
| What you see | What to do next |
|---|---|
| Samples close together | The route is steady. Note the average as the normal figure for that gateway. |
| Samples far apart | The network or the host is busy. Run it again in a few minutes before drawing conclusions. |
| Some samples time out | Connections are being dropped. If it keeps happening on a proxy host, send the results to support. |
| Every sample times out | Usually a wrong port, a firewall or nothing listening. Check the host and port in your dashboard. |
Each attempt waits up to two seconds, and the average only counts connections that succeeded. The figures describe the route from our server to the host, not from your office, so a faraway gateway will normally show higher figures than a nearby one. Only public hosts can be tested; addresses inside private networks are refused.
