// tool/ping-monitor
Ping Monitor
Track latency, jitter, and packet loss over time for quick before/after comparisons.
What this is
Ping (ICMP echo) is the cheapest reachability + latency check you have. A monitor that samples continuously turns three numbers — round-trip time, jitter, and loss — into a story about the path so you can prove a change improved things or didn't.
What it covers
- ›RTT samples
- ›Jitter calculation
- ›Loss percentage
- ›Browser and edge comparison
Operator notes
- $Collect a baseline before the change window.
- $Jitter matters heavily for voice and video.
- $Packet loss under load often points to congestion or policing.
status: Live monitoring is queued behind the server diagnostics work.
Ping monitor — browser + edge
checking limit…
— solid: browser-- dashed: edge
1.1.1.1
browser
last —avg —jit —loss 0%
edge
last —avg —jit —loss 0%
8.8.8.8
browser
last —avg —jit —loss 0%
edge
last —avg —jit —loss 0%
Browser probes use a no-cors fetch to {target}/favicon.ico; edge probes go through the Lovable Cloud server. Failures count as loss. Compare the two: if browser is slow but edge is fast, the issue is local (Wi-Fi, VPN, last mile).
Frequently asked
- What's an acceptable jitter for VoIP?
- Under 30 ms is generally safe, under 10 ms is comfortable. Above 50 ms users start hearing choppy audio regardless of bandwidth.
- Why is ping fine but the app is slow?
- Ping measures one tiny packet round-trip. App slowness is usually TCP throughput, TLS handshakes, or backend latency — none of which ICMP sees.
- Is packet loss always bad?
- Steady-state loss above ~1% on a wired path is bad. Bursty single-sample loss can be ICMP rate limiting on a router and is often noise.