Help / Troubleshooting
I did not get an alert
A monitor went down, or you think it did, and no alert reached you. Go through these checks in order. Most missed alerts come from the first three.
1. Check that a channel gets down alerts
- Open Alerts.
- Read Your alert setup at the top. It says how many channels get outage alerts. If it says “No channel is set to receive outage alerts”, nobody is told when a monitor goes down.
- In the list of channels, look at Events. A channel only gets the events listed there: down, up, certificate or slow.
Channels apply to all your monitors. You cannot change the events of a channel you already added. Press Remove and add it again with the right boxes ticked. See Setting up alerts.
2. Send a test
- On Alerts, press Send test on the channel.
- Look under Recently sent further down the page. It lists the last 30 messages. Each shows as sent, delivered, failed or not delivered, with the reason when it did not get through.
If the test arrives, the channel works and the problem is with the monitor (see step 4). If it shows failed, the reason tells you what to fix. You can send up to 10 test alerts an hour.
3. Check the channel itself
- Look in your spam or junk folder, and in any filters or rules you have set up.
- Until you confirm your own email address, alerts can only go to that address. A notice at the top of the app says so, with a Send it again link.
Slack, Teams, Discord, Zapier and webhooks
- If someone deleted or changed the webhook in the other service, our messages fail. Recently sent shows the error. Make a new webhook there, remove the old channel here and add the new address.
- For Teams, older Office 365 connector addresses no longer work. Use a Teams workflow address. See Microsoft Teams.
Telegram, PagerDuty and ntfy
Check that the bot is still in the chat, the PagerDuty integration key is still active, or the ntfy topic is the one your phone follows. See Telegram, PagerDuty and ntfy.
The phone app
Phone alerts are chosen on each phone, not on the website. If the phone stays quiet, see App alerts not arriving.
A channel marked Disabled
A channel marked “Disabled” in the list gets no monitoring alerts. Contact support if you did not expect this.
4. Check that the monitor went down
- Open the monitor from your dashboard and look at Incidents, or open Incidents.
- If there is no incident, the monitor never counted as down. By default 2 cities have to agree, each after 2 failed checks in a row. A short blip, or a failure seen in one city only, does not send an alert. See How checks work.
- If the monitor says Resume at the top, it is paused. Paused monitors are not checked and send nothing.
5. Check for a maintenance window
Alerts are held back while a maintenance window covers the monitor. If the monitor is still down when the window ends, the alert goes out then. Open Maintenance to see your windows. See Maintenance windows.
6. Recovery and repeat alerts
- A “back up” message needs both a channel with Back up ticked and the monitor's Send a "back online" message when it recovers box ticked. That box is under More settings when you edit the monitor.
- A down alert is sent once unless you set Repeat the down alert every (minutes, 0 = once) on the monitor. Repeats stop when someone acknowledges the incident.
- Slow alerts only come if the monitor has a number in Alert when slower than (ms, optional) and a channel has Slow ticked.
Still nothing
Contact support with the monitor name, the time you expected the alert and the channel it should have gone to. If Recently sent shows an error, copy it into your message.
Still stuck? Email [email protected] and say which guide you were following.