Email

New accounts get email alerts on from the moment they sign up. They go to the email address you signed in with (your Google or GitHub email) and cover all your monitors. You’ll see this destination as Email on the Notifications page, next to any Telegram, Slack or webhook destinations.

Don’t see an Email row?

Accounts created before email alerts launched, and accounts that already had another destination, may not have one yet. Turn it on yourself: on Notifications, choose Add destination, then Email under Other channels, and Turn on email alerts. It uses your Google or GitHub sign-in address.

One address for now

Email alerts go only to your account’s sign-in address. Other addresses and shared team inboxes aren’t supported yet. To alert a team, add a Slack channel, a Telegram group, or a webhook.

What an email alert contains

The subject line says what happened, so the notification alone is enough — for example [DOWN] checkout-api — HTTP 503 (service unavailable). Inside:

• What we saw — the problem in plain words, e.g. “HTTP 503 (service unavailable)” or “No check-in received on time”. See what each cause means.
• What’s being checked, which locations saw the problem, when it started (in UTC, plus “3 minutes ago”), and the response time when it matters. “When it started” is the first failed check, which is a little before the email arrives, because CuliPulse waits for the outage to be confirmed before it alerts; see Incidents.
• A Coverage line when only some of the monitor’s locations were reporting, for example “Only 1 of 3 locations is reporting (Frankfurt and Office NAS are silent) — this result may not reflect every location.” It’s left out when every location is reporting.
• A button to the incident and a link to the monitor.

A missed heartbeat email says when the last check-in arrived and when the next one was expected. When a monitor that was only degraded (it never went down) recovers, the email says it’s back to normal rather than “back up”. When the length of the episode is known, it says how long it was Slow (a slow HTTP, TCP or UDP response, or a heartbeat run that went past its max run time) or Degraded (any other cause, such as ping loss or latency, or an expiring certificate).

You get one email when something breaks and one when it’s fixed. You also get emails for domains that are about to expire, heartbeats that didn’t check in, outages your vendors report, and your own agents going offline.

Emails come from [email protected]. Add it to your contacts so alerts don’t land in spam. Replies go to our support inbox.

Limit: 20 emails per hour

Each account gets at most 20 alert emails per hour, so a monitor that keeps flapping can’t flood your inbox. Alerts over the limit aren’t emailed — they still go to your other destinations and show in the console — and the next email within the hour tells you how many were skipped.

Send a test

Email alerts must be switched on to send a test — turn on the Email row first if it’s off.

On Notifications, open the ⋯ menu on the Email row and choose Send test alert. The subject starts with [TEST], the status label reads TEST instead of the red DOWN, and the email says This is a test, nothing is down. Tests count toward the hourly limit, and there’s a short wait between tests.

Turn email alerts off (and back on)

• From an alert email: click Turn off email alerts at the bottom, then confirm. Some mail apps also show an Unsubscribe button next to the sender; that turns them off in one click.
• From the console: switch off the Email row on Notifications.

To turn them back on, switch the Email row on again. The Email destination can’t be removed — only turned off.

Why email alerts might be off

If CuliPulse turned email off for you, the Email row shows Off in amber, with the reason under the name. It never says Connected while email is off:

What the row says	What happened	What to do
Turned off from an email link	Someone used the Turn off email alerts link in an alert.	Switch it back on if that wasn’t intended.
Turned off: the address bounced	Your mail server rejected our email as undeliverable.	Check the mailbox still exists, then switch it back on.
Turned off: marked as spam	An alert email was reported as spam.	Mark our emails as “not spam”, then switch it back on.
Turned off: the address can’t receive mail	Earlier emails bounced or were reported, so our email provider won’t send to this address.	Contact us to clear it.

In the API and Terraform

Email alerts aren’t part of the API or the Terraform provider yet: /v1/channels lists Telegram, Slack and webhook destinations only.