Email alerts that arrive with the evidence.
When a check fails, the message carries the checkpoints that saw it, a screenshot from the moment of failure, the response headers and a traceroute. Setup is an address — no webhook to host, no app to install, no confirmation link to click.
Overview
Last 7 DaysThe alert that only wakes you
A push notification has to be terse, and that is right for the interruption. It is wrong for the minute after: “Site is DOWN” answers one question and raises six it has no room for.
An investigation that starts at zero
Every question the one-liner leaves behind costs minutes at the worst time — and if the failure was intermittent, half the evidence is already gone by the time anybody goes looking for it.
Same second, plus the evidence
An email has room. The same incident arrives as a report: the checkpoints, a screenshot while the site was broken, the response headers and a traceroute — evidence that stays true after it ends.
The proof arrives before the client
At 07:41 a furniture shop mid-campaign starts serving HTTP 500 from a host the studio that built it does not control. The shop’s own dashboards show nothing: the ads are still running and the orders have simply stopped.
Nothing to connect. Type an address.
Email is not an integration you authorise — it is a contact type. Add the address, attach it to monitors, and it works on the next check. No webhook to host, no app to install, no confirmation link to chase.
Add the address as a contact
In Alerting → Contacts, add a contact of type Email and type the address. It works immediately — email contacts need no confirmation — and your account address gets alerts before you add anyone.
Say who hears about what
Attach contacts per monitor, so whoever runs the shop is not woken by the staging box. Quiet hours and no-alert days are set per recipient — one person can be reachable at 03:00 while another is not.
Put your own name on it
A branding theme sets the logo and the colours per monitor, so a client sees your studio at the top of the message. Branded alerts and the custom sender name in the From line both come with the Professional plan and above. The Uptimia footer goes on a branded theme — the per-address opt-out link always stays.
Add and verify an email contact
The Help Center walks the contact screen: adding the address, setting the days and hours it may be alerted, and assigning it to the monitors it should hear about.
- Adding a new contact
- Verification
- Alerting schedule
- Assigning contacts to monitors
- Per-monitor alert settings
Twelve monitor types. Twelve different reports.
Every check writes its own report, because the useful facts differ: a transaction the step it died on, a certificate its expiry and issuer, a server the measured value vs your threshold. Only the frame is shared.
People, mailboxes and machines
An address can belong to a person, a shared mailbox or a ticket queue, so the same alert reaches whoever fixes it, whoever answers for it and whatever keeps the record — without a second integration.
Chat says it broke.Email says why.
The whole platform on the trial — twelve monitor types, 171+ checkpoints, and every failure explained in an email you can keep.
Renders, delivers, retries
An alert that renders as broken boxes in Outlook, or lands in a spam folder nobody opens, has not alerted anyone. Both are engineering problems, and both were solved before a word of the message was written.
What a down email actually holds
A status badge, the monitor name and a key-facts strip — down since, the error, locations confirmed. Below: the checkpoint table with flags, the failure screenshot, and headers, body and traceroute.
Renders where you read mail
Nested tables and inline styles only — no flexbox, no web fonts, no rgba — so it looks the same in Outlook desktop, Gmail and Apple Mail, with a plain-text copy for everything else.
Sent to arrive, not to bounce
The From domain is matched to the relay that actually sends the message, so DKIM aligns and DMARC passes — plus one-click unsubscribe headers, the way the big providers now expect.
Retried, not forgotten
A failed delivery is re-queued and retried up to five times, each wait a minute longer than the last, and one malformed address can never take down the rest of the batch.
One digest per storm
When monitors on the same escalation policy fail together you get one email listing them all — name, error and the time each went down — with throttled updates as more join and a single recovery notice at the end.
Acknowledge without logging in
Alerts from an escalation policy — Professional plan and above — carry a signed, per-recipient Acknowledge incident link. Click it and the ladder stops: no password, no session, and it dies when the incident resolves. A monitor that fails on its own still gets its full report, with the link at the bottom. Recovery mails never carry one.
How email alerts work
Uptimia checks your websites from 171+ external locations and, when a check fails, emails every address attached to that monitor a full report of the failure. The subject states the verdict and the monitor — “DOWN | Uptime Check example.com Failed”, “TROUBLE | SSL Certificate example.com Expires Soon”, “UP | Uptime Check example.com UP After 31 Minutes”. Inside is a status badge, the key facts (down since, the error, how many locations confirmed it), and then the evidence that belongs to that check type: the checkpoint table, a screenshot from the moment of failure, response headers and body, and a traceroute. Recovery mails lead with the total downtime, the time it came back and the root cause. When several monitors on one escalation policy fail together, that group is summarised into a single email listing them rather than a report for each. Timestamps use your account’s time zone, every message ships with a plain-text copy, and a branding theme puts your own logo and colours on the message.
A sending problem, not a mail problem
A From address that does not match the relay fails DMARC alignment, and quarantine hides it. Uptimia matches sender identity to relay — Europe gets the European sender — so DMARC passes.
Confirmed first, then explained in full
Nothing is emailed on one probe’s opinion. You set how many independent locations must agree — up to three — before an incident is opened at all. Email differs in what happens next: no length limit, so the message carries enough to act on, forward and file.
Six emails, one address
The subject line tells you the verdict before you open anything; the body changes with the kind of check.
Compare all 12 alert channels →| Subject begins | What’s inside | |
|---|---|---|
| Down alert | DOWN / CRITICAL | Key facts, checkpoint table, screenshot, headers, traceroute |
| Trouble warning | TROUBLE | What is degrading — expiry dates, thresholds, measured values |
| Recovery | UP | Total downtime, time back up, and the root cause |
| Storm digest | DOWN | Every monitor in the group, one acknowledge link |
| Join update | DOWN | Which monitors joined since the last message — throttled |
| Scheduled report | Your report name | Uptime and response time for the period, attached as PDF, HTML or CSV |
Email alerts FAQ
01How do I turn email alerts on?+
02What is actually inside a down alert?+
03Do all monitor types email me?+
04Will the alerts land in spam?+
05Can the emails carry my own branding?+
06What stops a storm from flooding the inbox?+
07Can different people get different alerts?+
08What happens if an email cannot be delivered?+
09How does someone stop getting alerts?+
10Is email included on every plan?+
Type an address. Get the incident.
Add the people who should know, attach them to the monitors they care about, and let the next failure explain itself — with the checkpoints, the screenshot and the traceroute already in the message.