Email downtime alerts

Updated 25 October 2026 · By the Upcertain team

Set it up

1. In Settings, Alert channels, choose E-mail. Owners, admins and editors can add channels.
2. Enter up to 20 addresses, separated by commas.
3. Pick the events: Down, Up (recovery) and SSL certificate expiry.
4. Save, use Send a test, then add the channel to the monitors it should cover.

When you sign up, your account starts with an email channel for your own address, attached to new monitors, so the first monitor alerts someone straight away.

One copy per recipient

Each address receives its own email rather than one message with everyone in copy. That keeps addresses private from each other and lets each recipient have a personal stop link at the bottom. Mail clients that support one-click unsubscribe (RFC 8058) also show their own unsubscribe button, which works straight away.

Acknowledge from the email

Down alerts carry an Acknowledge button, but only for recipients who can acknowledge: owners, admins and editors of the account. Others, such as a client who just wants to know, get the same alert without the button.

What arrives

• Down: the monitor, its address, the cause, when it started, and links to acknowledge or view the incident.
• Still down: reminders at the interval you set for the monitor's channel, until someone acknowledges.
• Up: the recovery with the total downtime.
• SSL certificate expiry: a warning on each day you chose before expiry.

People without a login

Add people who only need to hear about outages, such as a manager or a client, as notify-only contacts under Team. They receive email alerts for the events you choose and have no login.

Weekly and monthly reports

Under Settings, Notifications, owners and admins can turn on a weekly report (sent on Mondays) or a monthly one (on the 1st) with the previous period's uptime and incidents. It goes to members who receive email notifications.

Delivery

Alerts are sent from alerts@upcertain.com. Add it to your contacts or allow-list so alerts never land in spam. A failed send is retried at 30 seconds, 1, 2 and 4 minutes.