Why use this instead of opening the site in a browser?

Browser returns an HTTP status that depends on the entire web stack (DNS, TLS, the app). Ping uses raw ICMP and tells you only whether packets can reach the host and how fast they round-trip. That isolates network reachability from application or DNS issues. If ping works but the browser does not, the network is fine and the problem sits higher up.

I get 100% packet loss but the site loads in my browser. Why?

Many production servers and CDNs (Cloudflare, AWS, Fastly) drop ICMP at the edge to reduce noise and DDoS surface. Ping packets disappear silently while normal HTTP traffic gets through fine. To confirm the service itself is alive use HTTP Headers or SSL Checker, and use Traceroute to see where in the path packets actually stop.

What counts as a 'good' ping time?

Rough guide: under 20 ms is the same continent over fiber, 20 to 100 ms is normal for most cross-country and cross-Europe traffic, 100 to 300 ms is intercontinental, 300+ ms suggests satellite, congested mobile, or an inefficient route. Spikes matter more than averages: a consistent 80 ms beats a jittery 30 ms average with 200 ms peaks for real-time apps.

Why is the first packet always slower than the rest?

The first packet pays for DNS resolution, possibly an ARP lookup on your local network, and route discovery on intermediate hops. After that everything is cached. Watch the second and later packets for the real round-trip number, the first one is noise.

Is this free? Any limits?

Free, no signup. Max 6 packets per request, rate-limited per IP. Private IPs (RFC 1918, localhost) are refused for security.

Network

Ping

Test network connectivity

Input

Instantly check the reachability of any domain or IP address using the standard ICMP protocol. This tool measures Round-Trip Time (RTT) and detects packet loss.

Terminal

Console ready. Execute a command to see output...

About Ping

What connects you to the world?

Ping is the heartbeat of the internet. It uses the ICMP (Internet Control Message Protocol) to send "Echo Request" packets to a target host and waits for an "Echo Reply".

How it works under the hood

The Handshake: Your device sends a tiny data packet (32 or 64 bytes) to the server.
The Stopwatch: A timer starts the moment the packet leaves.
The Return: The server catches the packet and immediately throws it back.
The Result: The time taken (Round Trip Time) is your "Ping".

Interpreting the Data

< 20ms: Pro-gaming quality. Fiber-optic speeds.
20ms - 100ms: Standard operations. Good for browsing and streaming.
> 150ms: Noticeable lag. Voice calls may chop.
Packet Loss: If packets go out but don't come back, your connection is unstable or the server is firewalled.

Pro Tip: High ping to a local server usually means local Wi-Fi congestion. High ping to a server across the ocean is just the speed of light law (physics!).

How to use Ping

Enter the target
Type the domain name or IPv4 address into the host field. No protocol prefix and no trailing slash.
Pick a packet count
Anywhere from 1 to 6. Four is enough for a quick reachability check, six gives a more reliable jitter estimate.
Run the ping
Hit Ping. Packets stream into the terminal panel one by one with their RTT, then a summary line appears at the end.
Read the summary
Look at packet loss (anything above 0% on a stable network is suspicious) and the min/avg/max RTT. If timing varies wildly across packets, the path is congested. Follow up with Traceroute to find the slow hop.

Frequently Asked Questions

: Browser returns an HTTP status that depends on the entire web stack (DNS, TLS, the app). Ping uses raw ICMP and tells you only whether packets can reach the host and how fast they round-trip. That isolates network reachability from application or DNS issues. If ping works but the browser does not, the network is fine and the problem sits higher up.