Email alerts - configuration

E-mail is the default channel for alerts. It works right after you register, with nothing to set up. This article explains what an alert looks like, when it arrives and what to do if it happens not to reach you.

What the alert contains

When a monitor detects an outage, you receive an e-mail with this information:

• The monitor name and the monitored address (URL).
• The reason for the outage - for example an HTTP error code (the number the server responds with) or the error text.
• The exact time when the outage started.
• A direct link to the monitor detail in the dashboard.

Once the service is restored, we automatically send a second e-mail as well (recovery, that is a confirmation that the service is back), in which you find out how long the outage lasted and when exactly it ended. That way you immediately know whether there is still something to deal with or everything is fine.

How fast the alert arrives

E-mails are sent from [email protected]. They typically reach you within 5 to 15 seconds of the outage being confirmed. Delivery can be a little slower if your mail server uses strict anti-spam rules.

Who the alerts are sent to

The recipient is always your account e-mail. If you need to alert a whole team, use a Telegram group or a webhook pointing to an on-call management tool (such as PagerDuty).

When an alert did not arrive

If you are sure the monitor had an outage but no e-mail reached you, check the following in turn:

• Look in the Spam or Bulk folder.
• Add [email protected] to your trusted senders (whitelist).
• In your profile, check that you entered the correct e-mail address - even a small typo in the domain will cause the message not to arrive.
• Check in the dashboard whether the monitor really switched to the Down state. A short fluctuation (within the configured tolerance, the so-called tolerance window) does not trigger an alert.