Check if any website, server or IP address is online and measure its response time and latency. Real-time results, no sign-up needed.
A ping test is the fastest way to confirm whether any server, website or IP address is online and how quickly it responds to network requests. This tool sends ICMP Echo packets from our server to your target and measures the round-trip time (RTT) in milliseconds. If ICMP is blocked, it automatically falls back to a TCP connection probe on ports 80 and 443 so you get a result regardless of firewall configuration.
In addition to confirming reachability, the tool calculates minimum, average and maximum latency, packet loss percentage, and an estimated jitter value. For a complete network health check, combine this with our DNS Lookup to confirm the domain resolves correctly, our Port Checker to verify specific services are running, and our HTTP Headers Checker to inspect the server's response configuration.
A ping test uses the ICMP (Internet Control Message Protocol) Echo Request and Echo Reply messages defined in RFC 792. Our server sends a small packet to your target host and starts a timer. When the target responds with an ICMP Echo Reply, the elapsed time — the round-trip time (RTT) — is recorded in milliseconds. By sending four packets in sequence, the test calculates the best (minimum), average and worst (maximum) RTT, along with the percentage of packets that received no reply (packet loss). This gives a complete picture of network path quality, not just a single snapshot.
When ICMP is blocked (common on cloud servers, firewalls and hardened infrastructure), our tool automatically falls back to a TCP handshake on ports 80 and 443. The result is marked as a TCP probe. A TCP probe confirms the host is accepting connections but measures slightly different network characteristics than a true ICMP ping. For the most comprehensive reachability test, combine ping with our Port Checker to verify specific service ports are open and accepting connections.
Packet loss occurs when one or more of the sent packets receives no reply. Even small amounts of loss have a significant impact on real-time applications. A 5% loss rate in a voice call means roughly 1 in 20 audio packets is dropped, causing choppy audio. For gaming, any consistent packet loss causes lag spikes and disconnections.
Packet loss can be caused by network congestion, physical link errors, firewall rules, or the target server being genuinely offline. If a host shows 100% packet loss but you know it is online, the most likely explanation is ICMP filtering — confirm by checking whether HTTP is working with our HTTP Headers Checker, or verify specific ports with our Port Checker.
Jitter is the variation in latency between successive packets. If packet 1 takes 12ms and packet 2 takes 48ms, the jitter is 36ms. Low jitter means your connection delivers packets at a consistent rate; high jitter means packets arrive at unpredictable intervals. This tool estimates jitter as the difference between the maximum and minimum RTT. For voice and video calls, jitter above 30ms causes audible quality degradation even when average latency looks acceptable. To understand the network path between you and a target, look up the destination IP with our ASN Lookup to identify the hosting provider and network region.
Ping and port checking answer different questions. A ping test confirms that the host's IP address is reachable at the network layer. A port check tests whether a specific application service is running and accepting connections on a TCP port. A server can pass a ping test while a critical service is crashed and its port is closed. Conversely, a server can block ICMP entirely (failing a ping test) while serving web traffic normally on port 443. Use ping to establish basic reachability, then use our Port Checker to verify specific services, and our HTTP Headers Checker to confirm the web server is returning correct responses. For domain-level investigation, DNS Lookup confirms the IP being pinged is the correct one for the domain.