A LITTLE HELP. A LOT DONE.
Good tools.
Great flow.
Your shortcut to the everyday. Create, convert, calculate,
and get back to what you love.
✳
✳
✓ Free to use✓ No sign-up✓ 500+ possibilities
About this tool
The Online Ping Test measures the round-trip response time from our server to any hostname or IP address, simulating what an ICMP ping would return from a neutral, third-party vantage point. It sends multiple sequential requests and reports min, max, and average response times alongside packet loss percentage. This is useful for checking whether a server is reachable, measuring latency to a remote host, verifying that a server is responding after a deployment, and troubleshooting network connectivity from a reference point outside your own network. The tool uses HTTP-level probing or ICMP where available from the backend.
Why use it
Server-side pinging provides a neutral measurement independent of your network.
Reports min, max, average, and packet loss across multiple pings.
Works for both hostnames and raw IP addresses.
Useful for confirming server reachability from a third-party perspective.
Server-side pinging provides a neutral measurement independent of your local network or ISP.
Reports min, max, average, median, and packet loss across multiple probes.
How to use
- Enter a hostname or IP address in the input field.
- Set the number of pings (default 4).
- Click Ping to start the test — probes are sent sequentially with a 1-second gap.
- Review min, max, average response times, and packet loss in the results.
- Enter a hostname (e.g. example.com) or IP address (e.g. 8.8.8.8) in the input field.
- Set the number of pings to send (default 4, max 10).
When it helps
- Verifying a server responds after a reboot or deployment.
- Measuring latency to a remote server from a neutral data center.
- Checking whether a host is reachable independent of your local network or ISP.
- Troubleshooting intermittent connectivity by checking packet loss.
- Verifying a server responds after a reboot, deployment, or DNS change.
Examples
InputHost: 8.8.8.8, count: 4
Expected resultProbe 1: 12.3 ms
Probe 2: 11.8 ms
Probe 3: 12.1 ms
Probe 4: 11.9 ms
Min/Avg/Max: 11.8 / 12.0 / 12.3 ms
Jitter: 0.2 ms
Loss: 0%
02Distant server (cross-continent)
InputHost: server.au.example.com, count: 4
Expected resultProbe 1: 178 ms
Probe 2: 182 ms
Probe 3: 175 ms
Probe 4: 1000 ms (timeout)
Min/Avg/Max: 175 / 383 / 1000 ms
Jitter: 412 ms
Loss: 25% (1/4)
InputHost: protected.example.com, count: 4
Expected resultICMP blocked — falling back to HTTP probe
Probe 1: 89 ms (HTTP)
Probe 2: 91 ms (HTTP)
Probe 3: 88 ms (HTTP)
Probe 4: 92 ms (HTTP)
Note: Server reachable via HTTPS but blocks ICMP.
Tips
- Ping under 20ms is excellent; 20-100ms is good; 100-300ms is acceptable; over 300ms degrades real-time apps like voice/video.
- Packet loss above 1% is a problem worth investigating — even 5% loss makes TCP-based protocols stutter.
- Many production servers block ICMP at the firewall — a failed ping does not necessarily mean the host is down. Try the Website Status Checker for HTTP-level confirmation.
- Jitter (variance between probes) matters more than average latency for VoIP and gaming — aim for under 30ms jitter.
- If you see consistent loss on every Nth packet, a router on the path may be rate-limiting ICMP — typical and usually harmless.
- Compare hostname ping (uses DNS) to IP-only ping — large differences indicate slow DNS resolution.
- Use traceroute (or our future traceroute tool) to find which hop on the path is causing latency.
Frequently Asked Questions
What is ping?⌄
Ping is a network utility that sends ICMP Echo Request packets to a host and measures the time for the Echo Reply to return — the round-trip time (RTT), commonly called latency.
Why might a ping fail even though the site loads in my browser?⌄
Many servers block ICMP packets (ping) via firewall rules for security. The server may still accept HTTP/HTTPS traffic while refusing ICMP. A ping failure does not necessarily mean the service is down.
What is a good ping (latency) value?⌄
Under 20ms is excellent. 20-100ms is good for most applications. 100-300ms is acceptable but may cause perceptible delay in real-time applications. Above 300ms is considered high latency.
Can I ping a private IP address (192.168.x.x)?⌄
No. The ping is sent from our server on the public internet and cannot reach private/non-routable IP addresses.
Is this the same as running ping in my terminal?⌄
Functionally similar, but the request originates from our server rather than your machine. This eliminates your local network as a variable.
Glossary
- ICMP
- Internet Control Message Protocol — the network-layer protocol used by ping (Echo Request/Reply) and traceroute. Often filtered at firewalls for security.
- RTT
- Round-Trip Time — the duration for a packet to travel from sender to receiver and back. The latency metric reported by ping.
- Latency
- The time delay between sending a network request and receiving the response. Measured in milliseconds (ms). Synonymous with RTT in the ping context.
- Jitter
- The variation in latency between successive packets. High jitter (over 30ms) degrades real-time applications even when average latency is low.
- Packet loss
- The percentage of probes that did not receive a response within the timeout. Above 1% indicates a network issue worth investigating.
- Traceroute
- A diagnostic command that maps the network path from source to destination by sending packets with increasing TTL values and recording each router's reply.
- TTL (network)
- Time-To-Live in IP packets — a counter decremented at each router hop. When it reaches zero, the packet is dropped and an ICMP Time Exceeded is sent back. Used by traceroute.
- MTU
- Maximum Transmission Unit — the largest packet size that can be sent over a network without fragmentation. Standard ethernet is 1500 bytes.