---
title: I'm not receiving alerts
description: Track down why a monitor went down without a notification reaching you, and make sure the next one does.
section:
title: Fix a problem
order: 3
order: 2
lastUpdated: 2026-10-31
next: ["/docs/guides/choose-who-gets-alerted", "/docs/concepts/alerts"]
keywords:
[
"no notification",
"missing alert",
"email not arriving",
"slack not working",
"spam",
"silent",
"no email",
]
---
Open Alerts and click View History. Whether the monitor's event is listed, and with which **Status**, tells you which section below applies.
## If no alert covers the monitor
An alert only hears about the monitors in its Scope. An alert scoped to one monitor, or to Every HTTP monitor, stays silent when a cron job or a DNS monitor breaks.
Check the **Scope** column of the Alerts list. Widen an alert with Edit Alert, or create a Team-wide (every monitor) alert as a catch-all.
## If a maintenance window was running
While a maintenance window with Suppress alerts during this window covers a monitor, no alert is sent for it, and nothing appears in the history either.
Look under Maintenance for a window that was Active at the time, including recurring ones. Their times are in UTC.
## If the history says Skipped (Cooldown)
The first notice of an outage is always sent; repeats wait out the alert's Cooldown (minutes), 60 by default. A recovery notice sent shortly after another one for the same monitor is also held back.
To hear more often, lower the cooldown with Edit Alert. Repeats are never closer than 5 minutes apart.
## If the history says Failed, or the alert shows Broken
Failed means the destination refused or couldn't take the delivery. A Broken badge on the alert means the destination said it no longer exists, as when a Slack or Discord webhook is deleted.
Open the alert with Edit Alert, enter a working webhook URL, integration key or address, and click Save changes. Saving clears the badge.
## If the history says Sent but the email never arrived
The email left Uptime. It comes from `no-reply@uptime.sergiodxa.com`, so check your spam folder and any filter that matches the alert's subject prefix, and add the address to your allow-list. Make sure the Recipient on the alert is spelled right.
## If the monitor's state doesn't alert
Some states never send a notice:
- A cron job that is Late alerts only when Alert on Late is on for that job. A Missed job always alerts.
- A flow monitor that shows Cannot run hasn't found anything wrong with your service, so it never alerts. See [My flow monitor fails or can't run](/docs/troubleshooting/flow-monitor-fails).
- A recovery is only announced with Notify on recovery on.
There's no test button. To try a channel, point a monitor at a URL that returns a different status from its Expected Status Code and click Run Monitor; the alert fires on that first failing check.