Online Ping Test: How to Measure Latency, Jitter, and Packet Loss
Ping is the simplest network diagnostic tool. It sends a small packet to a server and measures how long it takes to come back. Despite its simplicity, ping tells you three critical things about your connection: latency, jitter, and packet loss.
Run a Free Ping Test
Use our free ping test tool to check latency and packet loss to any server or website. Enter a hostname or IP address and get instant results including:
- Latency (min, average, max) in milliseconds
- Packet loss percentage
- Jitter measurement
- Multiple ping rounds for reliable results
No signup required. No software to install.
Understanding Latency
Latency is the time it takes for a packet to travel from your location to the server and back, measured in milliseconds (ms). The ping test shows you minimum, average, and maximum latency.
What's normal?
| Latency | Typical Scenario |
|---|---|
| Under 10ms | Same datacenter or local network |
| 10-50ms | Same region or nearby city |
| 50-100ms | Same continent |
| 100-200ms | Cross-continent |
| 200-300ms | Intercontinental |
| Over 300ms | Satellite links or severe congestion |
When to worry
Latency is relative to distance. A server in Sydney pinged from London will naturally show 250-300ms. That's physics, not a problem.
Worry when:
- Latency spikes suddenly (was 50ms, now 500ms)
- Latency is high for a nearby server (200ms to a server in your city)
- Latency fluctuates wildly between pings (sign of network congestion)
Understanding Jitter
Jitter is the variation in latency between consecutive packets. If five pings return 45ms, 47ms, 44ms, 46ms, 45ms — that's low jitter (good). If they return 45ms, 120ms, 30ms, 200ms, 50ms — that's high jitter (bad).
Why jitter matters
Low latency with high jitter is worse than moderate latency with low jitter for:
- Video calls: Jitter causes freezing and audio glitches
- VoIP: Jitter makes voices sound robotic or choppy
- Gaming: Jitter causes rubber-banding and desync
- Real-time APIs: Jitter makes response times unpredictable
Acceptable jitter levels
- Under 5ms: Excellent — suitable for any application
- 5-20ms: Good — fine for most uses
- 20-50ms: Acceptable — may affect real-time applications
- Over 50ms: Poor — will cause noticeable quality issues
Run the ping test to check your jitter to any server.
Understanding Packet Loss
Packet loss means some packets never came back. The ping test tool shows this as a percentage: 0% is perfect, 1-2% is noticeable, and 5%+ is a serious problem.
What causes packet loss?
- Network congestion: Too much traffic on the route
- Faulty hardware: Bad cables, failing switches, or overloaded routers
- WiFi interference: Weak signal, channel congestion, or distance from AP
- ISP issues: Backbone capacity problems or routing changes
- Firewall rate limiting: Some hosts drop ICMP packets intentionally
Impact of packet loss
- 1%: Barely noticeable for web browsing. Causes slight delays.
- 2-5%: VoIP calls drop words. Video stutters. Web pages load slowly.
- 5-10%: Unusable for real-time applications. Web pages timeout frequently.
- 10%+: Severe connectivity issue. Investigation needed immediately.
How to Run an Effective Ping Test
From the command line
# Basic ping (runs continuously on Linux/Mac, 4 pings on Windows)
ping example.com
# Specific count
ping -c 20 example.com # Linux/Mac
ping -n 20 example.com # Windows
# With timestamp
ping -D example.com # Linux
From our online tool
The free ping test tool runs pings from Exit1.dev's infrastructure, not from your local machine. This means:
- Results aren't affected by your local WiFi or ISP issues
- You can test server reachability even when your connection is unstable
- Results represent what your users actually experience from different locations
Testing methodology
For reliable results:
- Run at least 10-20 pings (not just 4)
- Test at different times of day (congestion varies)
- Compare results from the online tool vs local ping to isolate whether the issue is your connection or the server
- Test multiple destinations to determine if the problem is route-specific
Ping Test vs Other Network Tests
| Test | What It Measures | Best For |
|---|---|---|
| Ping (ICMP) | Latency, jitter, packet loss | Server reachability, basic network health |
| Traceroute | Path and per-hop latency | Finding where slowdowns occur |
| HTTP check | Application response time | Website and API health |
| Speed test | Bandwidth throughput | Download/upload capacity |
Ping tests network-level connectivity. For application-level health, use the API status checker. For SSL validation, use the SSL checker. The most thorough approach combines all three.
Common Ping Test Scenarios
"I can ping the server but the website is down"
The server is reachable at the network level, but the web application has crashed or is misconfigured. Use the API status checker to see the HTTP error.
"Ping times out but the website works"
The server is blocking ICMP packets (common on cloud hosts and some firewalls). This doesn't mean there's a problem — it means ping isn't the right tool for this host. Use HTTP checks instead.
"Latency is high only at certain times"
Network congestion follows patterns. Business hours bring higher traffic. Peak streaming hours (evening) congest residential connections. Run the ping test at multiple times to map the pattern.
"Packet loss only to one destination"
The problem is likely on the route to that specific server, not your connection. Run traceroute to identify which hop is dropping packets.
From Ping Test to Continuous Monitoring
A single ping test gives you a snapshot. Continuous monitoring gives you trends, baselines, and instant alerts when something changes.
Exit1.dev offers free ICMP ping monitoring:
- Automated pings from multiple global regions
- Latency and packet loss tracking over time
- Instant alerts when a host becomes unreachable
- Combined with HTTP, API, and SSL monitoring in one dashboard
Start with a quick ping test, then set up continuous monitoring at exit1.dev for free.
Recommended Resources
- Free Ping Test Tool – Test latency, jitter, and packet loss to any server
- Free API Status Checker – Check HTTP status and response time
- Free ICMP Ping Monitoring Guide – Set up continuous ping monitoring
- ICMP vs HTTP Monitoring – When to use each check type
Morten Pradsgaard is the founder of exit1.dev — the free uptime monitor for people who actually ship. He writes no-bullshit guides on monitoring, reliability, and building software that doesn't crumble under pressure.