---
title: Game server latency no longer counts a slow first query
description: Some game servers answer the first query of every check much slower than the ones right after it: 450 ms, then a steady 120 ms. The check reported that first…
canonical: https://watchfor.io/changelog/2026-11-19-game-latency-median
---

[All updates](/changelog/page/2#2026-11-19-game-latency-median) 🐛 Fixed Game servers UDP Nov 19, 2026 · v 13.4.6

# Game server latency no longer counts a slow first query

Some game servers answer the first query of every check much slower than the ones right after it: 450 ms, then a steady 120 ms. The check reported that first query as latency, and the step down from it as jitter, so latency and jitter alerts fired on servers that were fine. With Measure packet loss on, latency is now the median round trip of the check's queries, and jitter starts at the second answer. The slow first query still shows in the max and counts toward packet loss.

## What changed

- Latency (game servers with Measure packet loss on): the median round trip of the answered queries, not the first one alone. With the setting off it is still the round trip of the single status query.

- Jitter (game and UDP monitors): the mean difference between consecutive round trips, starting from the second answer. It needs three answers per check.

- Round trip min / average / max and packet loss are unchanged and still include the first query.

- When the first query is more than twice as slow as the median, the check details say so.

- On Steam servers the challenge round trip was never part of latency and still isn't.

Details: [latency and the first query](/docs/monitors/game#latency-and-the-first-query).

Share this update

---

Canonical page: https://watchfor.io/changelog/2026-11-19-game-latency-median · Site guide: https://watchfor.io/llms.txt
