Latency — last 3 minutes
latencybaselinespike thresholdlagspike
Lagspikes per hour — last 12 h
Throughput tests downloadupload
Lagspike log
Time
Severity
Peak latency
Duration
Above baseline
no lagspikes recorded yet — looking good
Settings
how often latency is measured
how far above baseline counts as a spike
64 KB download + 32 KB upload per test
measure latency to a different server
What am I looking at?
Latency — time for a signal to go from you to the server and back. Under 50 ms is great for gaming, 50–100 ms is fine, over 150 ms feels laggy. Baseline — your connection's normal latency (rolling median). Spikes are measured against this, so the monitor adapts to your line. Jitter — how much latency jumps around between measurements. Under 5 ms is rock solid; over 15–20 ms causes stutter in games and robotic voice in calls even when average ping looks fine. Packet loss — percentage of probes that never came back. Anything above ~1% is noticeable in games (rubber-banding, teleporting). Lagspike — a moment where latency jumped well above your baseline. Even short ones cause missed shots and freezes. Severity: minor (+15–40 ms), major (+40–100 ms), severe (100+ ms or lost packets). Download / Upload — small periodic throughput tests. They use tiny amounts of data so they won't disturb your connection. Note — measurements go from this browser to the server showing the page, so they describe the path between you and it — a good real-world proxy for game-server traffic.