Quiet mode for alerts
Quiet hours suppress personal notifications during a night window of your choosing, so minor outages do not wake you up. It is configured individually for your account and, once enabled, it applies to all your monitors at once. This article explains in detail which channels quiet hours affect and which they do not - so you do not rely on suppression where it will not happen.
For instructions on how to enable quiet hours and set the from-to time, see the article Quiet hours - quiet notification mode. This article is purely about what exactly quiet hours do to notifications.
What quiet hours suppress
During the quiet window, these personal notifications are not sent:
- Email notifications - no message about an outage or a recovery will arrive at your account email.
- Telegram messages - the bot
@epulzio_alerts_botwill not message you during the quiet window.
These suppressed notifications are not sent afterwards once the window ends - they are simply not sent. The incident itself, however, is always recorded in the monitor history, so in the morning you will see exactly what went down and when, and how long it lasted.
What quiet hours do NOT affect
- Webhooks (Slack, Discord, Microsoft Teams and your own endpoint) run always, quiet hours do not turn them off. Programmatic integrations usually have their own escalation logic, which is why we deliberately do not silence them.
- Escalation policies also go through their own channel (email or webhook within the escalation step) and quiet hours do not apply to them. Escalation is meant for critical, unresolved incidents that there is no point in silencing.
- History and status page - the incident is written into the history and the status is updated on the public status page for your customers in the usual way.
How to make sure you get an alert even at night
If you need to be alerted even during the quiet window for a truly critical outage, you have two reliable options:
- Webhook - route notifications to an on-call management tool (for example PagerDuty) or to a team channel. Webhooks bypass quiet hours.
- Escalation policy - create a step that, after a few minutes of an unresolved incident, sends a notification via email or webhook to the next responsible person. You will find the details in the article about the escalation matrix.
Caution: quiet hours suppress personal email and Telegram notifications, not all channels. If you run a service with 24/7 customers, route critical monitors through a webhook or escalation, which quiet hours will not stop.