Free Tool
Ping Test
Instantly test latency, packet loss, and jitter to any server or website. Free, no signup required.
What You Get
Here's an example of the latency report this tool provides. Try it above with any host.
All Pings Successful
example.com — 0% packet loss
Min
12 ms
Avg
18 ms
Max
24 ms
Jitter
3.2 ms
Latency (ping time) measures the round-trip time for a TCP connection to the server. Under 50 ms is excellent for most regions, 50-100 ms is good for cross-region connections, and anything over 200 ms may cause noticeable delays for real-time applications like video calls or online gaming.
Jitter is the variation between consecutive ping times. Low jitter (under 5 ms) means a stable connection, while high jitter (over 20 ms) indicates network instability that can degrade VoIP, streaming, and real-time communications even when average latency is acceptable. Packet loss above 1-2% usually signals a network problem and should be investigated.
How It Works
Enter Host
Type any hostname, domain, or IP address. Choose how many pings to send (1-10).
We Ping It
Our server resolves the hostname and sends TCP connection requests, measuring the round-trip time for each one.
See the Results
View individual ping times, packet loss, jitter, and min/avg/max statistics at a glance.
Network Glossary
The terms behind every ping result — explained without the textbook detour.
Latency (RTT)
Round-trip time — the time for a packet to travel from your machine to the server and back. Bound by physics: light through fibre is roughly 2/3 the speed of light in vacuum, so any path adds a real, unavoidable floor.
Jitter
Variation in latency between consecutive packets. Calculated as the average absolute difference between successive RTTs. Low jitter (< 5 ms) means a steady connection; high jitter (> 20 ms) means VoIP and video will struggle even when average latency looks OK.
Packet loss
Percentage of packets that never received a response. A small amount (< 1%) is tolerable; anything more degrades streaming, calls, and TCP throughput. Always measured over a sample — a single missing packet on a 5-ping test is 20% loss but probably noise.
TCP ping vs ICMP ping
ICMP ping (the classic ping command) uses ICMP Echo. TCP ping opens a TCP connection on a real port (usually 80 or 443) and times the handshake. TCP is more useful for web work because many firewalls block ICMP but allow TCP, and it tests the same path your traffic actually uses.
Hop
Each router along the path between you and the destination. Latency accumulates per hop. A traceroute shows them all; a ping just shows the round-trip total. Most internet paths cross 10–20 hops.
MTU
Maximum Transmission Unit — the largest packet a link will carry. Default for Ethernet is 1500 bytes. PMTU mismatches cause fragmentation or black-hole drops, which look like inexplicable timeouts on otherwise healthy paths.
What Your Ping Results Actually Mean
The latency, jitter, and loss numbers you will see — and what action they should trigger.
Latency under 50 msExcellent — same-region performance
Typical of a server in the same city or country. Real-time apps (gaming, voice, live trading) feel instant. If a critical user-facing endpoint is over 50 ms, consider edge deployment or a closer region.
Latency 50–150 msGood — typical cross-region
Normal for cross-country or transatlantic traffic. Web browsing and most apps feel responsive. Above ~120 ms, voice and video start to feel slightly sluggish.
Latency 150–300 msAcceptable — long-haul connection
Cross-continental traffic (Europe ↔ Asia, US ↔ Australia). Web works fine; real-time interactivity is noticeably degraded. CDN edges and regional replicas help close the gap.
Latency over 300 msPoor — investigate the path
Either a genuinely long path (satellite link, far region) or a routing problem. Check whether the result is consistent. If it spikes only sometimes, the path has congestion or an unstable hop.
Jitter over 20 msUnstable connection
Even when average latency is fine, high jitter wrecks voice, video, and any app expecting steady packet delivery. Common causes: WiFi interference, congested ISP link, or buffer-bloated router on the path.
Packet loss above 1%Network is dropping packets
Anything above 1% degrades real-time apps and slows TCP throughput (TCP retransmits + reduces congestion window). 5%+ is broken. Investigate which hop is dropping with a traceroute.
100% packet lossHost is unreachable
Either the host is down, a firewall is blocking the chosen port, or there is no route to it. TCP ping (this tool) checks ports 80/443 — many servers respond on those even when ICMP is filtered.
TCP timeoutConnection never completed
The TCP three-way handshake did not finish in time. Often a stateful firewall silently dropping SYN, the server overwhelmed, or routing returning to a black hole. Try ICMP ping or a different port.
Frequently Asked Questions
Learn More About Network Monitoring
Guides on ping testing, latency measurement, and infrastructure monitoring.
Online Ping Test Guide
How to measure latency, jitter, and packet loss — and what the results actually mean.
What Is Network Jitter?
Understanding and fixing connection instability that affects VoIP, video, and real-time apps.
Free ICMP Ping Monitoring Guide
Set up continuous ping monitoring for servers, routers, and network devices.
ICMP vs HTTP Monitoring
When to use ping checks vs HTTP checks, and why you need both for full-stack visibility.
Last updated · Built and maintained by exit1.dev — uptime, SSL, and domain monitoring with instant alerts.
Need Continuous Latency Monitoring?
Stop checking manually. exit1.dev monitors your servers 24/7 and alerts you instantly when latency spikes, packet loss occurs, or your services go down.
Start Free Monitoring