Mail a confirmed outage
The mail goes out once enough independent EU locations fail the check often enough in a row, not on the first failed request; both thresholds sit in your package.
Use Uptimeify with email.
The channel that needs no setup on the other side, and the one that carries the most, including the picture of the page that broke.
What lands in the inbox
Everything the alert pipeline sends by email is on this list, and nothing beyond it. Read it once and you know what your team will see.
Mail the recovery
The all clear follows in the same thread of recipients, without a screenshot, because there is nothing broken left to show.
Attach the screenshot
A page that was still reachable in a browser is captured at send time and attached, so the mail shows what the visitor saw.
Reach the recipients you name
Addresses on the channel win, and without them the mail follows the notification targets of the client and your organisation.
Send through your own SMTP
Your server is tried first and our sender takes over only when it fails, so a broken relay never swallows an outage mail.
Carry your branding
Product name, app link and accent colour come from your organisation, and the product name can be hidden entirely.
Send its own mail for domains and blocklists
Expiring domains and blocklist hits arrive as their own mail, from a template written for them rather than as an outage notice.
Retry a transient failure
A greylisted or briefly unreachable server is retried on its own ladder, and the attempt is logged as retrying rather than as failed.
A list per monitor
Each channel has its own recipients, so a client's outage reaches the people who look after that client instead of everyone.
Teams that run their monitoring on Uptimeify
Minutes to set up. Then it runs on its own.
1. Add an email channel
In the alerting settings create a channel of type email, no account or token needed anywhere.
2. Name the recipients
Enter the addresses the alerts should reach, or leave them empty to follow the notification targets of the client.
3. Assign monitors and test
Assign the monitors the channel covers and send the test mail, so the first real alert is not the first delivery attempt.
Before you add the email channel.
Yes. The organisation's SMTP is tried first, and our own sender only takes over when that attempt fails, so a relay having a bad day cannot swallow an outage mail.
Because there is nothing broken left to show. Screenshots are taken for the outage, where the picture is the evidence, and a recovery is deliberately screenshot-free.
No, and that is on purpose. It is captured only when the page was still reachable in a browser. A DNS or connection failure would produce a misleading picture, so none is taken.
Yes. Product name, app link and accent colour come from your organisation, and the product name can be hidden entirely for a client facing mail.
No. Your quota covers monitors and the monthly SMS and voice allowance. Alerts over email, webhook or Slack do not draw on it.
Every alert, where your team already works.
Add an email channel, and every confirmed outage reaches the people you named, with the page that broke attached.