Ping & Traceroute: Test Network Latency & Server Uptime
Ping and traceroute test online: measure latency, packet loss, and routing hops to diagnose slow connections and server issues.
Updated 2026-08-16
Related Tools
DNS Lookup: All 16 Record Types (A, AAAA, MX, SRV)
Port Scanner Online: Check Open Ports & Common Services
HTTP Headers Viewer: Analyze & Audit Response Headers
IP Address Lookup: Online Geolocation, ISP & ASN Info
SSL/TLS Certificate Checker: Verify & Analyze Online
Subnet Calculator: CIDR/IPv4 Range & Host Calculator Online
Features
- ICMP ping from 20+ global nodes with latency visualization
- Traceroute showing network path with hop-by-hop details
- TCP port connectivity check from multiple locations
- HTTP status check with response time and IP detection
- DNS resolution check showing A/AAAA records and TTL
- Visual latency bars with proportional width display
- Summary statistics: total nodes, average latency, packet loss
- Platform-specific command reference for all check types
- Historical results tracking: past check results are kept locally for comparison
- Packet loss percentage displayed per node in ping results: identify problematic hops in the route
- HTTP check includes response headers and server IP detection: verify web server configuration from multiple global locations simultaneously
- All checks produce shareable results: copy the full report as formatted text for team collaboration or troubleshooting documentation
How to Use
- 1Enter a hostname or IP address (e.g., 8.8.8.8 or example.com).
- 2Click Ping to test ICMP latency from global nodes.
- 3Click Traceroute to see the network path with hop details.
- 4Click TCP to check port connectivity (enter port number first).
- 5Click HTTP to check web server status and response time.
- 6Click DNS to verify DNS resolution from multiple locations.
- 7Check the Commands tab for platform-specific command-line tools.
- 8In Ping results, look at the packet loss column; nodes with >0% loss may indicate network congestion or routing issues
- 9In Traceroute results, identify high-latency hops; a sudden spike often points to an overloaded or geographically distant router
- 10Use the TCP check to verify specific services (e.g., HTTPS on port 443) after firewall changes
- 11Copy the summary statistics panel to share with your team; it includes average latency, total nodes tested, and packet loss across all locations for quick reporting
- 12Run the DNS check to confirm that your domain's A and AAAA records have propagated globally; compare results from nodes on different continents to spot regional propagation delays
Frequently Asked Questions
What checks are available?
The tool supports 5 types of checks: ICMP ping (latency), Traceroute (network path), TCP (port connectivity), HTTP (web server status), and DNS (name resolution). All checks run from distributed global nodes.
How many nodes are used for each check?
Ping uses up to 20 nodes, Traceroute uses 5, TCP/HTTP use 15, DNS uses 10. The actual number depends on node availability at check time.
Is this a real ICMP ping?
Yes. The ping check uses distributed global nodes to send real ICMP packets. Results show actual round-trip times from multiple worldwide locations.
How does the TCP check work?
TCP check tests if a specific port is accepting connections from global nodes. Enter host:port (e.g., example.com:443) to test. Useful for verifying firewall rules and service availability.
What HTTP status codes mean?
200 = OK (success), 3xx = redirect, 4xx = client error (e.g., 404 Not Found), 5xx = server error. The tool shows the status code and response time from each location.
What is the difference between ping and traceroute?
Ping measures the round-trip time to a destination and reports packet loss; it answers 'can I reach this host and how fast'. Traceroute shows the path your packets take hop by hop, revealing which router adds latency or drops packets. A common workflow: use ping first to confirm reachability, then traceroute to locate the slow or failing hop. This tool runs both checks from global nodes so you can see regional differences.
Why does ping work but traceroute fail (shows stars or timeouts)?
Ping and traceroute rely on different ICMP messages. Ping needs echo replies, while traceroute needs 'TTL exceeded' responses from every intermediate router. Many routers and firewalls (especially in cloud networks like AWS) block or rate-limit TTL-exceeded packets, so traceroute shows * * * even when the route is fine. Also, some hosts block ICMP entirely, so ping can fail while TCP/HTTP still work. If only one method fails, test the other (the TCP check here is a good fallback) before concluding the network is broken.
What does packet loss mean and when should I worry?
Packet loss occurs when data packets fail to reach their destination. 0-1% loss is normal for internet connections. 1-2.5% may cause noticeable degradation for streaming and VoIP. Above 5% significantly impacts most applications. The tool shows per-node packet loss in ping results; consistent loss at a specific hop often points to a congested or failing router, while loss at multiple hops may indicate a broader network issue. For Wi-Fi connections, try moving closer to the access point or switching to a wired connection to rule out wireless interference.
What is the difference between jitter and latency?
Latency (or ping) measures the time it takes for a packet to travel to a destination and back. Jitter measures the variation in latency over time: how much the ping times fluctuate between consecutive tests. High jitter (above 20ms) is more disruptive to real-time applications like VoIP calls and online gaming than high latency because it causes uneven packet delivery. The tool helps you assess both by showing individual node latencies that reveal jitter patterns across multiple locations.
Why does traceroute show unexpected IPs or extra hops?
Both are normal. Traceroute lists every router your data passes through: the first hop is usually your router (192.168.x.x or 10.x.x.x), followed by your ISP's gateway, then intermediate routers across different networks, and finally the destination; the more networks the route crosses, the more hops you see. Unexpected entries usually point to: 1) High latency spikes (>100ms increase): a slow or overloaded router. 2) Asterisks (* * *): routers that don't respond to traceroute probes (common and not necessarily a problem). 3) Sudden geographic jumps: routing through another continent adds significant latency. 4) Packet loss at specific hops: a router that drops packets may indicate congestion or hardware issues.
Why does ping latency vary between different global nodes?
Geographic distance is the primary factor; a node in Tokyo will have higher latency to a US East Coast server (approximately 100-150ms) than a node in New York (5-20ms). Other factors include: the number of network hops, undersea cable routes, ISP peering arrangements, and current network congestion. The tool's multi-node approach shows you the realistic latency your server experiences from different regions, which is critical for global applications and CDN configuration.
Why does my ping and traceroute command show high latency to a server that loads fast in the browser?
Ping measures the ICMP round trip to the host itself, while browsers usually talk to a CDN edge server near you, and HTTP can take a different path than ICMP. Firewalls may also deprioritize or drop ICMP while letting web traffic through. So high ping does not always mean the site will be slow; check the HTTP response time separately before concluding there is a problem.
Why can't I run ping and traceroute commands on Mac the same way as on Windows?
Windows uses tracert for traceroute; macOS and Linux use traceroute: different names, the same idea. Ping exists on both, but macOS ping keeps running until stopped unless you pass -c 4, while Windows stops after four replies by default. This web tool runs the same ping and traceroute checks with the same controls on any operating system.