---
title: Packet loss and jitter for UDP and game server monitors
description: A UDP or game server check could tell you the server answered, but not that a third of its packets never came back, and that loss is what players feel as lag…
canonical: https://watchfor.io/changelog/2026-11-18-udp-game-packet-loss
---

[All updates](/changelog/page/2#2026-11-18-udp-game-packet-loss) ✨ New UDP Game servers Nov 18, 2026 · v 12.6.4

# Packet loss and jitter for UDP and game server monitors

A UDP or game server check could tell you the server answered, but not that a third of its packets never came back, and that loss is what players feel as lag and timeouts. With Measure packet loss on, each check sends a short train of packets, 5 by default and 150 ms apart, and records packet loss, round trip and jitter per location, with history on the charts. It is on for new UDP and game monitors; existing ones are one switch away in Settings → Advanced options. Opt-in alerts warn at 20 % loss and go critical at 60 %.

## What each check measures

- Packet loss : unanswered packets ÷ packets sent, in percent.

- Round trip : min, average and max over the answered packets.

- Jitter : the mean difference between the round trips of consecutive answered packets, so you can see how much the delay swings from packet to packet.

On game servers this covers the UDP protocols: Steam (A2S), Minecraft Bedrock, SA-MP / open.mp and MTA. Minecraft Java, FiveM and RedM are queried over TCP / HTTP, so there is no packet loss to measure.

## Turning it on

- New UDP and game monitors start with Measure packet loss on, from the dashboard, the API, MCP or an import.

- Monitors you already have keep sending one packet per check until you switch it on in Settings → Advanced options , where you also set Packets per check (3–10) and their spacing (100–500 ms).

- Monitors without it say so where the loss would be (the Packet Loss tile on UDP, the Latency stats on game servers) and link to Settings.

## How the numbers behave

- With it on, a check is up when any packet is answered, so one lost packet no longer fails it. When nothing answers, the monitor is down as before, and that shows as a failed check rather than 100 % loss.

- Loss is averaged over checks that got an answer. Servers that answer only the first packets of a burst on purpose are recognised as rate-limited and left out.

- A check takes about 0.6 s longer with the defaults (about 0.9 s on Steam servers, which are queried at least 220 ms apart). Response-time charts still end at the first reply.

- Charts draw loss as a dashed line on its own 0–100 % axis. On game servers the Latency section also shows Packet loss and Jitter next to Avg / Min / Max, and a thin amber band marks each stretch where a location lost 20 % or more (the alert's warning level); hover it for when, how long and which locations.

- To stay gentle on busy hosts, each location sends at most 50 packets per second to one address; past that, a check sends a single packet for that run.

- The packet loss alerts (and High Game Server Jitter for game servers) are off until you switch them on.

Details: [UDP](/docs/monitors/network#packet-loss-and-jitter) · [game servers](/docs/monitors/game#packet-loss-and-jitter).

Share this update

---

Canonical page: https://watchfor.io/changelog/2026-11-18-udp-game-packet-loss · Site guide: https://watchfor.io/llms.txt
