UFOZoo

Ping & Traceroute — Test Network Latency & Server Uptime

Test network latency using HTTP fetch timing. Check server response times and uptime. Includes traceroute commands for Windows, macOS, and Linux.

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 — keeps past check results in your browser 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

  1. 1Enter a hostname or IP address (e.g., 8.8.8.8 or example.com).
  2. 2Click Ping to test ICMP latency from global nodes.
  3. 3Click Traceroute to see the network path with hop details.
  4. 4Click TCP to check port connectivity (enter port number first).
  5. 5Click HTTP to check web server status and response time.
  6. 6Click DNS to verify DNS resolution from multiple locations.
  7. 7Check the Commands tab for platform-specific command-line tools.
  8. 8In Ping results, look at the packet loss column — nodes with >0% loss may indicate network congestion or routing issues
  9. 9In Traceroute results, identify high-latency hops — a sudden spike often points to an overloaded or geographically distant router
  10. 10Use the TCP check to verify specific services (e.g., HTTPS on port 443) after firewall changes
  11. 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
  12. 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.

Is my data sent to any server?

∨
The hostname/IP you enter is sent to our API to initiate checks. The actual checks (ping, TCP, HTTP, DNS) are performed by distributed global nodes. Your browser IP is visible to the service.

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.

How should I interpret traceroute results?

∨
Traceroute shows each hop your data takes from source to destination. 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. Look for: 1) High latency spikes (>100ms increase) — indicates 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 — an IP that routes through a different 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.

Related Tools

DNS Lookup — Free All 16 Record Types (A, AAAA, MX, SRV)

Free DNS lookup supporting 16 record types (A, AAAA, MX, SRV, HTTPS, etc.) via Cloudflare, Google, or AliDNS DoH. All queries run in your browser — no server.

Port Scanner — Free Check Open Ports & Port Forwarding

Check web port availability and identify services. Full reference with 100+ ports. All checks run in your browser — no data sent to servers.

HTTP Headers Viewer — Analyze & Audit Response Headers

Paste raw HTTP response headers to analyze cache, security, CORS, and server headers. Detect missing security headers like HSTS, CSP, and X-Frame-Options.