Send real ICMP pings to any public IP address or hostname from probes across 6 continents. Check latency, packet loss, and reachability instantly — no installation required.
Real ICMP pings from every continent — not simulated, not proxied
Min / avg / max RTT and packet loss percentage per probe location
Ping IP addresses directly or domain names resolved per region
Send real ICMP pings to any public IP address or hostname from probes around the world and compare latency and packet loss across locations.
Pinging from global probes...
Best Avg RTT
Worst Avg RTT
Packet Loss
| Location | Network | Min | Avg | Max | Loss |
|---|
Powered by the free Globalping probe network by jsDelivr
Type any public IPv4 address (e.g. 8.8.8.8), IPv6 address, or hostname (e.g. google.com) into the input field. Private and reserved addresses are not supported since public probes cannot reach them.
Choose which part of the world the ping probes should come from. 'Worldwide' picks probes from multiple continents simultaneously. You can also select a specific region — Europe, North America, Asia, etc. — to measure regional latency.
Click the Ping button to start the test. The tool submits the measurement to the Globalping probe network, then polls for results automatically. Most tests complete in 3–5 seconds.
The results table shows one row per probe: its location and hosting network, the minimum / average / maximum round-trip time in milliseconds, and the packet loss percentage. Green loss means 0% packet loss; red means packets were dropped.
Round-trip time requirements vary significantly by application. The table below shows the thresholds used by network engineers to classify latency performance.
| Latency (RTT) | Rating | Typical Scenario | Impact |
|---|---|---|---|
| < 20 ms | Excellent | Same-city or same-datacenter | Imperceptible in all applications |
| 20 – 50 ms | Good | Same country / region | Excellent for gaming, VoIP, and video calls |
| 50 – 100 ms | Acceptable | Cross-country or nearby continent | Fine for web browsing; slight lag in fast-paced games |
| 100 – 200 ms | Marginal | Intercontinental (e.g. US→Europe) | Noticeable delay in VoIP; poor for real-time gaming |
| > 200 ms | Poor | Transoceanic or congested link | Audible echo in voice calls; unusable for latency-sensitive apps |
ITU-T G.114 recommends a maximum one-way delay of 150 ms for voice quality, which translates to ~300 ms RTT.
The ping command is available on every major operating system.
Use this tool to ping from external global probes, or run the commands below from your own terminal to test from your local connection.
# 4 pings (default)
ping 8.8.8.8
# Continuous ping (Ctrl+C to stop)
ping -t 8.8.8.8
# Custom count (e.g. 10)
ping -n 10 8.8.8.8
# Ping IPv6
ping -6 2606:4700::1111# 4 pings
ping -c 4 8.8.8.8
# Continuous ping (Ctrl+C to stop)
ping 8.8.8.8
# Custom interval (seconds)
ping -i 0.5 8.8.8.8
# Ping IPv6
ping6 2606:4700::1111# 4 pings
ping -c 4 8.8.8.8
# With timestamp output
ping -D 8.8.8.8
# Flood ping (requires root)
sudo ping -f 8.8.8.8
# Ping IPv6
ping6 -c 4 2606:4700::1111The server may be down, or ICMP is blocked by the host's firewall. Cloud providers (AWS, GCP, Azure) and CDNs (Cloudflare) often drop ICMP by default. Try pinging a different IP of the same provider, or use an HTTP-based check to verify web availability separately.
If probes in Europe respond fast but probes in Asia show 400+ ms, the server has no presence in Asia or the traffic is routing suboptimally. Consider adding a CDN node or a cloud region closer to affected users. Use Routing Simulator to explore routing paths.
Partial packet loss across specific ISPs or regions suggests a congested peering point or a routing issue between that ISP and your hosting provider. This is common across certain IX (Internet Exchange) links at peak times. Contact your hosting provider with the specific probe ISP and timing information.
A big gap between the minimum and maximum RTT (e.g. 10 ms / 180 ms) indicates jitter — inconsistent latency. Common causes: rate-limited ICMP deprioritized by the target router, congested uplinks at the probe or server side, or ECMP (Equal-Cost Multi-Path) routing sending packets over different physical paths. Jitter above 30 ms significantly degrades voice and video quality.
Ping was developed by Mike Muuss in 1983 as a simple tool to determine whether a remote host was reachable on an IP network. The name comes from sonar terminology — like a submarine sending an acoustic ping and listening for the echo. The tool sends an ICMP Echo Request packet to the target host. If the target is reachable and ICMP is not blocked, it responds with an ICMP Echo Reply. The elapsed time is the round-trip time.
Every ICMP packet includes a TTL (Time to Live) field — a hop counter that decrements at each router. If TTL reaches zero before the packet arrives, the router drops it and sends back an ICMP "Time Exceeded" message. This prevents packets from circulating forever on the internet, and is also the mechanism that traceroute exploits to map network paths.
Ping
Measures end-to-end RTT and packet loss to a single destination. Best starting point for any network problem.
Traceroute / Tracert
Shows each hop along the path and the RTT to each. Pinpoints which router is introducing delay or dropping packets.
MTR (Matt's Traceroute)
Combines both: continuous per-hop latency and loss statistics updated in real time. Best tool for diagnosing intermittent issues.
A ping test sends ICMP (Internet Control Message Protocol) echo request packets to a target host and waits for an echo reply. The round-trip time (RTT) measures network latency — how long data takes to travel from the probe to the target and back. Packet loss shows how many packets never received a reply.
Under 20 ms is excellent and typical within the same region. 20–80 ms is good for most applications. 80–150 ms is acceptable for web browsing but noticeable in real-time apps. Over 150 ms causes visible lag in voice calls, video conferencing, and online gaming. Intercontinental connections are naturally 100–300 ms due to the physical distance light travels through fibre.
Packet loss is the percentage of ICMP packets that sent no reply. 0% is normal on a healthy network. 1–5% causes occasional stutters in voice and video. Above 5% causes serious degradation — retransmissions, timeouts, and slow page loads. Consistent loss usually indicates network congestion, a faulty link, or ICMP rate-limiting by the target host or an intermediate firewall.
Latency depends on where the measurement originates. The same server might respond in 5 ms from Europe but 230 ms from Australia. Multi-location pings reveal regional performance differences, help validate CDN and anycast DNS configurations, and can pinpoint whether slowness affects all users or only those in a specific region.
Many servers and cloud platforms intentionally block ICMP packets with firewall rules. AWS EC2, Google Cloud, and Cloudflare-proxied domains often drop ping by default while serving HTTP/HTTPS normally. A failed ping does not mean the host is down — it means ICMP is filtered. Use an HTTP check tool if you need to verify web availability specifically.
No. Private RFC 1918 addresses (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16), link-local addresses (169.254.0.0/16), and loopback (127.0.0.1) only exist inside local networks. Public internet probes cannot reach them. To ping LAN devices, open a terminal on a machine in the same network and run the ping command directly.
Jitter is the variation in round-trip time between successive packets. A large gap between the Min and Max RTT values in the results table indicates jitter. For example, Min 10 ms / Max 120 ms means latency is inconsistent — common on congested links or wireless paths. Jitter above 30 ms causes noticeable audio breakup in VoIP and video calls.
The terminal ping command runs from your own machine on your own network connection. This tool runs ICMP pings from independent probes on different ISPs and continents. That means you can check reachability from outside your network, compare latency across regions, and see whether a problem is local to your connection or affects everyone.
Ping measures end-to-end round-trip time and packet loss to a specific host. Traceroute (tracert on Windows) reveals every hop along the path, showing latency at each router. Ping answers 'is the host reachable and how fast?' Traceroute answers 'where exactly is the delay or packet loss occurring?' Use ping first, then traceroute to dig deeper when ping shows a problem.
This tool sends 3 ICMP echo request packets per probe and reports the minimum, average, and maximum RTT along with the packet loss percentage. Using 3 packets per probe gives reliable results while keeping tests fast — typically completing in under 5 seconds.
Look up the country, city, ISP, and coordinates of any IP address.
Validate IPv4 and IPv6 addresses, check address type, and parse CIDR ranges.
Simulate routing table lookups and understand longest-prefix matching.
Detect CIDR conflicts and overlapping prefixes across multiple subnets.
Convert IP addresses between decimal, binary, hex, and CIDR notation.
Calculate IPv6 prefix ranges, address counts, and subnet boundaries.