---
title: Alert notifications now group during incident storms
description: When one upstream problem takes ten monitors down at once, ten separate pings tell you less than one message would. Your chat and email channels now receive a…
canonical: https://watchfor.io/changelog/2026-08-05-notification-grouping
---

[All updates](/changelog/page/7#2026-08-05-notification-grouping) ✨ New Aug 5, 2026 · v 5.2.3

# Alert notifications now group during incident storms

When one upstream problem takes ten monitors down at once, ten separate pings tell you less than one message would. Your chat and email channels now receive a single summary — "10 new incidents" with the affected monitors listed — instead. Monitors failing one by one batch too: follow-up waves collect for a few minutes and arrive as one further summary, and recoveries group the same way. A lone incident still arrives promptly as a normal, fully detailed notification, and PagerDuty, Opsgenie and webhooks keep their exact per-incident behaviour.

## What a storm looks like now

Your load balancer drops for two minutes and eleven monitors fail together. Before, your Slack channel got eleven messages in a row. Now it gets one:

🔴 11 new incidents
🔴 api.example.com: Probe failed to connect
🔴 [www.example.com](http://www.example.com): Unexpected HTTP status
…

When the load balancer is back, the recoveries arrive the same way, as one 🟢 11 recovered message.

## The timing

- New incidents are collected for up to 30 seconds and sent together. A single incident still arrives as a normal, fully detailed message.

- Follow-ups, such as recoveries and repeat reminders, are collected for a few minutes and sent as one more summary, so a slowly spreading outage doesn't drip one message per wave.

- A summary lists up to 10 monitors, then "…and N more".

## Which channels group

Email, Slack, Discord, Telegram, Microsoft Teams, Google Chat, Mattermost and Rocket.Chat. PagerDuty and Opsgenie stay one event per incident, because opening and closing each alert depends on it. Webhooks and Zapier get one payload per incident, and push apps one notification per incident.

[Notification history](/docs/notifications/history) still shows one row per incident, even when several went out in one message. More in [Grouping during a storm](/docs/notifications#grouping-during-a-storm).

Since then: a new incident's first message never waits behind an earlier one ([details](/changelog/2026-09-05-notification-timing)), and each row shows the monitor's target and the actual reason ([details](/changelog/2026-09-04-grouped-alerts-target-and-reason)).

Share this update

---

Canonical page: https://watchfor.io/changelog/2026-08-05-notification-grouping · Site guide: https://watchfor.io/llms.txt