---
title: X
description: When you already know a monitor is broken and are working on it, every further ping is noise. You can now mute a monitor's notifications for 1h, 8h, 24h or 7d…
canonical: https://watchfor.io/changelog/2026-08-05-mute-and-quieter-alerts
---

[All updates](/changelog/page/7#2026-08-05-mute-and-quieter-alerts) ⚡ Improved Aug 5, 2026 · v 5.2.3

# Mute a monitor's alerts + smarter flap suppression

When you already know a monitor is broken and are working on it, every further ping is noise. You can now mute a monitor's notifications for 1h, 8h, 24h or 7d from its ⋯ menu or straight from a firing incident; checks keep running and incident history keeps recording, only the pings pause. Muted monitors carry an amber badge and a Muted filter in the monitors list, so a silenced one is never lost among hundreds. Also quieter: a rapidly flapping monitor stops paging until it stabilises, and warning alerts stay quiet while the same monitor's critical incident is already firing.

The Muted filter lists every silenced monitor.

## Mute instead of pause

Pausing a monitor stops its checks, so you lose the very data that tells you when your fix worked. Muting keeps everything running and only holds back the notifications.

- Mute for 1 hour, 8 hours, 24 hours or 7 days from the monitor's ⋯ menu, or from the header of a firing incident.

- Checks keep running, and incidents still open, close and appear in history. Each notification that was held back is listed as Silenced in notification history.

- A muted monitor shows a crossed-out bell next to its name, and the amber Muted filter on the Monitors page lists every silenced one.

- The mute ends by itself when its time is up, so nobody has to remember to switch alerts back on.

## An example

Your search cluster is rebuilding its index and the Search monitor fires every few minutes. You mute it for 8 hours. You keep watching its response-time chart while you work, the rest of the team stops getting pinged, and the monitor alerts normally again by the evening.

## Quieter without muting anything

- Flapping: a monitor that keeps going down and up in a short time stops paging on every swing until it settles.

- Critical first: while a critical incident is open on a monitor, its warning alerts wait. One problem gives you one incident, not a warning and a critical about the same thing.

Muting needs the owner or admin role and is written to the activity log. See [Muting a monitor](/docs/notifications#muting-a-monitor).

Since then: an incident that is still open when a mute ends is notified within about a minute ([details](/changelog/2026-09-06-maintenance-window-fixes)).

Share this update

---

Canonical page: https://watchfor.io/changelog/2026-08-05-mute-and-quieter-alerts · Site guide: https://watchfor.io/llms.txt