---
title: Packet loss spikes show next to the averages
description: One check from one location lost 40 % of its packets, and the card still read 0.0 %: every tile and figure was an average that rounded the spike away, and the…
canonical: https://watchfor.io/changelog/2026-11-19-packet-loss-spikes
---

[All updates](/changelog/page/2#2026-11-19-packet-loss-spikes) ⚡ Improved Game servers UDP Ping Nov 19, 2026 · v 13.4.1

# Packet loss spikes show next to the averages

One check from one location lost 40 % of its packets, and the card still read 0.0 %: every tile and figure was an average that rounded the spike away, and the band named only its threshold. Now the location tiles say "<0.1% loss · 1 spike (40%)", Packet loss shows the peak, hovering the chart gives each period's peak and where, and the band says what happened: "Querétaro, Mexico · 40% (2 of 5 packets lost)". The same goes for UDP and ping monitors.

## What a spike is

A spike is one check that lost at least one packet. The averages stay as they were; the spikes sit beside them, so a quiet location stays quiet and one bad check still names itself.

## Where you see it

- Game server Ping & packet loss card : each location and region tile adds the spikes in the range ("3 spikes, up to 60%"), hover for the worst check, when it ran and from where. Packet loss adds "peak 40%". The crosshair reads "5.7% avg · peak 40% Querétaro · 33/35 answered".

- The amber band now marks a stretch where a single check reached the Packet Loss alert's warning level (20 %), not only a location's average over the period, and is titled Packet loss spike or Sustained packet loss.

- Packet Loss (UDP, game) and Ping Statistics (ping) : "peak 40%" beside the 24-hour average, the worst check on hover.

- UDP timing and ping charts : hovering a period with loss adds its worst check.

Share this update

---

Canonical page: https://watchfor.io/changelog/2026-11-19-packet-loss-spikes · Site guide: https://watchfor.io/llms.txt
