- Open Add destinationIn the sidebar, go to Integrations → Add destination.
- Choose EmailFind Email and choose "Set up Email".
- Enter name and addressGive the destination a Name and enter the Email address that should receive alerts. Your own sign-in address is filled in for you.
- SaveChoose "Add destination".
- Confirm other addressesIf it is not your own sign-in address, the recipient opens the confirmation link we email them within 7 days.
- Send a testOnce the destination shows verified, choose "Send test" under Configured destinations on Integrations → Destinations.
Email alerts are available on every plan. Each Email destination sends alerts to one address, and you can add as many as you need, for example one per teammate or a shared on-call mailbox.
Before you start
Any plan works, including Free. You need the owner, admin or operator role to add destinations; viewers can only see them.
Add an email destination
- Go to Integrations → Add destination.
- Find Email and choose Set up Email.
- Enter a Name (shown in routing rules and the delivery log) and the Email address. Your own sign-in address is filled in; replace it to alert someone else.
- Leave Personal destination — only notify me when I am on call unticked for a normal shared destination.
- Choose Add destination.
Confirm the address
Your own sign-in address is verified at once. Any other address must prove it wants the alerts:
- We email that address a confirmation link, naming your workspace and who added it. The recipient does not need an Uptime Tracker account.
- The recipient opens the link within 7 days. The destination then shows verified.
- Until then it shows pending (or expired after 7 days) and receives no alerts and no tests.
If the email went missing, choose Resend confirmation next to the destination. You can resend once every 10 minutes; each resend replaces the previous link, so only the newest one works.
What you receive
By default every verified, enabled shared destination receives:
- a down alert when a monitor's failure is confirmed and an incident opens,
- a recovered notification when the monitor comes back.
Each alert names the monitor, the time the outage was confirmed, a Reason: line such as HTTP 503 Service Unavailable or Timed out after 10s, and a redacted target (for HTTP monitors only the host). Reminders, escalation pages and acknowledgements are emailed too when routing rules or escalation policies produce them. If you use routing rules (Pro and higher), only the destinations chosen by the matching rules receive the alert.
Shared and personal destinations
Tick Personal destination — only notify me when I am on call to make an address yours alone. Personal destinations are used only by escalation policies when you are the on-call responder (Team plan); routing rules never use them. Leave it unticked for a normal shared destination.
Manage destinations
On Integrations → Destinations, under Configured destinations, you can Send test, Pause or Resume, Rename, Edit connection and Delete. Integrations → Deliveries shows every notification attempt and its state.
Change the address
Choose Edit connection, enter the New email address and choose Save connection. The address is checked like a new one. Changing it restarts confirmation: the new address receives a confirmation link, and the destination receives no alerts until it is opened (your own sign-in address is verified at once). Saving a change also re-enables a destination that was disabled after delivery failures. The change is recorded in the audit log as destination.connection_updated.
Changing the email address of your own account under Settings → Account does not change alert destinations that send to the old address; edit them here if they should move too.
Other confirmation emails
- Status page subscribers also confirm by email (double opt-in, link valid 7 days). See status page subscribers.
- Scheduled reports are sent only to verified email destinations. See availability reports.
Troubleshooting
- Still pending: the recipient has not opened the link. Ask them to check spam, then use Resend confirmation.
- "A verification message was sent in the last 10 minutes": wait 10 minutes before resending.
- "This confirmation link is invalid or has expired": the link is older than 7 days or a newer one was sent. Resend and use the newest email.
- No Send test button: tests are only possible for verified, enabled destinations.
- Alerts land in spam: allow-list email from
uptimetracker.live, and combine email with a chat or push channel so you see alerts quickly. - The address has a typo: use Edit connection to correct it; a new confirmation link goes to the corrected address.
Frequently asked questions
Can I send alerts to several email addresses?
Yes. Add one Email destination per address. Addresses other than your sign-in address must confirm through a link.
How long is the confirmation link valid?
7 days. Resending (at most once every 10 minutes) creates a new link and the old one stops working.
Why am I not receiving alerts at a new address?
It is probably still pending. Open the confirmation link in that inbox, or use Resend confirmation on Integrations → Destinations.
Do I get an email when the site comes back up?
Yes. Destinations receive a recovery notification when the incident resolves.
Can I change the address of an email destination?
Yes. Choose Edit connection on the destination. The new address must confirm through a link before alerts resume, unless it is your own sign-in address.
Does the alert email say why the monitor is down?
Yes. Down alerts, reminders and escalation emails include a Reason line, for example HTTP 503 Service Unavailable or DNS: no such host.