Skip to content

Website monitoring email alerts

Most alerts tell you something is down and leave you to find out the rest. Uptimia’s email arrives with the answers already in it — where it failed, a picture of what the visitor saw, and how far the request got. Setting it up takes one thing: an address.

An email has room for the evidence

A short buzz tells you the site is down — and nothing else. The alert email carries what you need next: which check failed, from where, since when, and what the checkpoint saw at that moment.

The alert that fits on a lock screen

An investigation that starts at zero

“Storefront is DOWN”
07:41 · that’s the whole message
log in · reconstruct
Six open tabs
regions? status? what did it look like?

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.

The alert that arrives with the case file

Same second, plus the evidence

Storefront is DOWN
07:41 · confirmed 3 regions
screenshot · trace
You start from the answer
and forward it to whoever owns the box

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.

Keep the terse alert — it is doing its job. Just make sure something also arrives that you can read, forward and keep. The same outage, end to end:

The alert arrives with the evidence attached

A check fails on a host you don’t control. The alert email arrives carrying the proof, ready to be forwarded as the ticket — and the recovery mail closes it with the total downtime.

07:41 The alert carries the client’s error pageThree checkpoints, the same failure — studio-branded, not a vendor white-labelled
07:46 The headers name the host’s cacheNo deploy last night — the traceroute stops in the provider’s network headers · trace
07:49 Forwarded to the host as the ticketTimestamps, three locations and a screenshot — nothing to dispute not retyped
08:12 ✅ Recovery mail: back up after 31 minutesTotal downtime, time back up, root cause — client report writes itself recovery report
31 mindown → up
The argument that never happened08:31
The host’s first reply blamed a plugin. The screenshot, three regions and a traceroute that never reached the shop’s container ended it — and the studio kept the thread as the record.
screenshot from the outage3 locations, timestamped31 minutes down0 client tickets
Nothing here needed a login — the evidence travelled with the alert, so it could be read on a phone, forwarded to a stranger and filed as a record. searchable a year later

Set up email alerts in three steps

There is nothing to connect and nothing to install. Add an address, point your monitors at it, and the alerts start with the next check.

Step 130 s

Add an email address

Type it in — it works immediately, with no confirmation link to chase.

maren@caldmont.com Save contact
ready on the next check · nothing to install anywhere
Step 21 min

Say who hears about what

Pick the checks each address should hear about, and set quiet hours per person.

Alert this monitor to
maren@caldmont.comalerts@caldmont.comSlack
quiet hours 22:00–07:00 · no alerts on Sundays
Step 3optional

Put your own name on it

A branding theme puts your logo and colours on the alert, so a client sees your name at the top of the message.

Sender and theme
From: Caldmont Monitoring · logo and colours from the theme
timestamps in the account’s time zone · plain-text copy included
Technical setup guide

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.

Each check explains itself its own way

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.

Uptime checksCheckpoints, screenshot, traceroute
SSL certificatesIssuer, expiry, days remaining
Domain expiryRegistrar and renewal date
Server metricsMeasured value vs your threshold
1 inbox one address, every kind of failure
Heartbeats & cronExpected at, last seen, missed by
TransactionsThe step it failed on, with the shot
Virus & malwareWhat was found and where
Page speedLoad time against your limit
The recovery mail closes the loop — total downtime, the time it came back and the root cause, so the incident files itself. every check · one address

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.

The people who fix it
Personal addresses, attached to the monitors they own.
The failing check, with its evidence
Quiet hours and no-alert days per person
On an escalation policy, a link that stops the ladder
one contact each
The people who answer for it
A shared mailbox for account managers, clients or the founder.
Only the monitors that face customers
Your logo and colours on every message
Scheduled uptime reports on the same address
forwardable by design
The systems that keep score
Your helpdesk, ticket queue or archive — all speak email.
Point a contact at your intake address
Every incident becomes a thread, with no code
Searchable long after the dashboard has moved on
an address is an API
Run it alongside something faster SlackMS TeamsTelegramWhatsAppTwilio SMSPagerDutyDiscord

Chat says it broke.Email says why.

The whole platform on the trial — every kind of check, 171+ checkpoints, and every failure explained in an email you can keep.

Start your free 30-day trial
30 days free no credit card cancel anytime

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.

Detected from — 3 locationsFLAGS · ERRORS Screenshot at time of failureIMAGE Headers · body · tracerouteRAW

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.

600px · HTML + plain text

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.

DKIM aligned · DMARC pass

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.

5 retries · then dropped

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.

9 monitors · 1 email

Acknowledge without logging in

Alerts from an escalation policy 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.

Acknowledge incidentSIGNED LINK Escalation pausedMTTA RECORDED

How email alerts work

Uptimia checks your websites from 171+ external locations and, when a check fails, emails you a full report of the failure — what broke, since when, and the evidence from the moment it happened. When the site recovers, a second email leads with the total downtime and the root cause.

“Alert emails always end up in spam”

A sending problem, not a mail problem

From: mail.example.com
sent by a different relay
DKIM misaligned
Quarantined
silently, by policy

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.

Outside probes + a message with room

Confirmed first, then explained in full

171+ locations
loading the real page
one per incident
Your inbox
evidence included

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.

Every event

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
EmailSubject beginsWhat’s inside
Down alertDOWN / CRITICALKey facts, checkpoint table, screenshot, headers, traceroute
Trouble warningTROUBLEWhat is degrading — expiry dates, thresholds, measured values
RecoveryUPTotal downtime, time back up, and the root cause
Storm digestDOWNEvery monitor in the group, one acknowledge link
Join updateDOWNWhich monitors joined since the last message — throttled
Scheduled reportYour report nameUptime and response time for the period, attached as PDF, HTML or CSV

Email alerts FAQ

01How do I turn email alerts on?+
They are already on for the address you signed up with. To add anybody else, create a contact of type Email under Alerting → Contacts and attach it to the monitors that person should hear about. Email contacts are usable as soon as they are saved — there is no confirmation link to click and nothing to install.
02What is actually inside a down alert?+
A status badge and the monitor’s name, then a key-facts strip: down since, the error, and how many locations confirmed it. Then the evidence: the checkpoints that failed with their country flags and individual errors, a screenshot taken while the site was broken, and terminal-style blocks with the response headers, the response body and a traceroute — whichever of those the check produced.
03Do all monitor types email me?+
Every one of them — uptime, transactions, page speed, real-user monitoring, SSL, domains, malware, servers, heartbeats, blacklists, DNS and API checks — and each has its own report layout, because the facts that matter differ. A transaction alert names the step that failed; a server alert shows the measured value against your threshold; a certificate alert leads with the expiry date.
04Will the alerts land in spam?+
Uptimia sends the message from a domain that matches the relay behind it, so DKIM alignment holds and DMARC passes — the single most common reason monitoring mail disappears. Messages also carry standard one-click unsubscribe headers. Strict corporate filters are still worth pre-empting: allowlist the sender once, and alerts stay in the inbox.
05Can the emails carry my own branding?+
A branding theme sets the logo and the colours, and it is assigned per monitor — so an agency can send each client alerts that carry the agency’s mark. Branded alerts come with the Professional plan and above; the sender name in the From line is a separate, account-wide setting on the same plans. Branded themes drop the Uptimia footer; the per-address opt-out link always stays, because a recipient must be able to stop mail they did not ask for.
06What stops a storm from flooding the inbox?+
Monitors on an escalation policy — Professional plan and above — are grouped: several failures inside the same window become one email that lists every affected monitor with its error and the minute it went down, plus throttled updates if more join and a single recovery notice at the end. Acknowledging from the link in that email stops the escalation for everyone on it. A monitor that fails on its own is not summarised into a list — it still gets its full report, acknowledge link included.
07Can different people get different alerts?+
Yes — contacts are attached per monitor, so the shop and the staging box can have entirely different audiences. Quiet hours and no-alert days are set per recipient and apply account-wide, which means one person can be reachable overnight while another is left alone until morning.
08What happens if an email cannot be delivered?+
The message is re-queued with escalating backoff and retried up to five times before it is dropped, and every other contact on that monitor is delivered to independently. A malformed address fails on its own — it can never abort the rest of the alerting run.
09How does someone stop getting alerts?+
Every alert carries a “Do not send alerts to this e-mail address” link in its footer, plus the one-click unsubscribe header that Gmail and Yahoo act on. It suppresses that one address without touching any other contact, and you can re-add it at any time from the dashboard.
10Is email included on every plan?+
Yes — email works on every plan and throughout the 30-day free trial, with nothing extra to pay. It also runs happily alongside the others: the same failure can text you, post in chat and land in the inbox as the version you keep.

Email alerts with the evidence attached

Add an address, point your monitors at it, and the next failure arrives already explained — the checkpoints, the screenshot and the traceroute in the message.

Nothing to install Evidence included 30-day free trial No credit card
Email is a built-in alert channel — and every check Uptimia runs writes its own report.