---
title: Game server latency: thresholds by region in one table
description: Setting latency alerts per region meant a Regions picker per level and a list of extra rules, and you couldn't see which region was already over the line. The…
canonical: https://watchfor.io/changelog/2026-11-18-game-latency-thresholds-by-region
---

[All updates](/changelog/page/2#2026-11-18-game-latency-thresholds-by-region) ⚡ Improved Game servers Alerting Nov 18, 2026 · v 13.1.1

# Game server latency: thresholds by region in one table

Setting latency alerts per region meant a Regions picker per level and a list of extra rules, and you couldn't see which region was already over the line. The latency card now starts with one threshold for all regions and shows each region's latency now under the sliders; Different thresholds by region opens a table where each region is judged on its own, inherits the default until you type its own value, has its own alerts switch (still monitored when off) and shows its latency now and the 24 h p95. A location in a new region starts with alerts off.

## Simple until you need more

- The card starts as before: one warning and one critical value for All regions , judged from every location together, with a quiet line under the sliders showing each region's latency now — "Now: Europe ~18 ms · North America ~94 ms · Asia ~212 ms".

- When some regions are over a threshold and others aren't, a notice under that line names them — "Africa is at ~170 ms — above your 150 ms warning" — and explains that with one threshold a region that is slow on its own won't alert; its different thresholds by region link opens the table.

- Different thresholds by region opens the table; Use one threshold for all regions closes it again.

## The table

- All regions holds the defaults. Each region you check from inherits them in grey until you type a value of its own; Reset puts the default back.

- Each region is judged on its own : it has its own rule, so "3 in a row" counts that region's checks and an incident is confirmed from that region.

- A region's alerts switch stops it alerting while it keeps being checked and charted.

- The Warning and Critical column switches turn a level off for every region, keeping the values.

- Under each region: latency now (median of the last 15 minutes) and the 24 h p95 , grouped by region the way the alerting engine groups checks, with an Above warning threshold tag when a region is over the line right now.

- Regions you don't check from have no rows: one line names them, with Add a location to open Settings on the monitor's locations.

## New regions

In the table, a location added in a new region starts with its alerts off (tagged New , with Turn on ), so it never alerts on a value you didn't choose for it. With one threshold for all regions it is simply judged with the rest.

The Activity Log records each change in words, e.g. "Alerts off for North America" or "Asia warning 220 ms". Details: [Alert rules by region](/docs/alerting#different-thresholds-per-region).

Share this update

---

Canonical page: https://watchfor.io/changelog/2026-11-18-game-latency-thresholds-by-region · Site guide: https://watchfor.io/llms.txt
