Is the server responding?
Send four probes to any IP address or domain and see latency, packet loss and jitter. If the server ignores ping, measure a TCP connection instead.
How it works
What the ping test measures
IDX Ping sends four probes from IDX's server to the address you enter and shows the time each one takes to come back, plus how many were lost.
ICMP ping
The classic ping: an echo request the target answers if it allows ICMP. The name is resolved once and pinged by IP address.
TCP when ICMP is blocked
Many servers and firewalls drop ICMP. The TCP options time how long it takes to open a connection on port 443, 80, 3389 (RDP) or 22 (SSH) instead.
Reading the result
Lower is better. Steady times mean a stable path; large jumps between probes suggest congestion. Lost probes on ICMP alone often just mean ICMP is filtered.
Public addresses only
Private, loopback and link-local addresses are refused, so the tool cannot be pointed at internal networks.
Common questions
The ICMP test fails but my site works. Why?
The server or its firewall is dropping ICMP, which is common. Try TCP 443 or TCP 80 to measure the same path over a port the server does answer.
Why is my result different from my own ping?
The test runs from IDX's server, not from your computer, so it measures a different network path. It is useful for checking whether a host is reachable from outside your network.
What is a good ping time?
It depends on distance. A few milliseconds is typical inside the same country, and over 100 ms is normal between continents.