Skip to content

Which emails do I get, and when?

Uptime Gorilla emails you when a monitor goes down, when it works again, and when an SSL certificate or a test website's Basic Auth needs you. Each email goes once, to one address at a time: nobody sees who else got it. Each monitor's page shows its latest alerts under Alerts, and to whom each email went; Show all alerts lists every one your plan shows (how far back alerts go).

The emails

What happened When we email
Down Once a second checking server agrees that the website does not work (how).
Up again After two good checks in a row, with how long it was down. Only to the addresses that got the Down email.
Can no longer check When, while a monitor is down, only a firewall or a Basic Auth password that is missing or no longer works has answered our checks for 2 hours. We end the outage, as we cannot tell whether the website works, and say at least how long it was down and what to fix (below). Only to the addresses that got the Down email.
Still down None, unless you choose them (while a monitor stays down): once after 24 hours, or also by Priority, after 30 minutes for P2 and 4 hours for P3 (still down, by Priority). To the alert email only.
SSL certificate 5 days and 1 day before it runs out, at once when it has expired, is not trusted or is made for another name, and when it is renewed or trusted again (the SSL rules).
Basic Auth is off When a monitor with the Basic Auth warning finds its website open twice in a row: anyone can open it. Then reminders after 1 hour, 4 hours and 1 day, and every day after that, while it stays off. To the alert email only.
Basic Auth is back on When the website asks for its password again, twice in a row.
Basic Auth password needed or refused Once, when the website asks for a Basic Auth user name and password and none is saved, or the saved one no longer works; again only after it was fixed and broke again. To the alert email only.

An email sent more than 15 minutes after what it is about says so at its end ("sent late"). If our mail server cannot pass an email on, we try again after 1, 5, 15 and 60 minutes.

Screenshots in Down and Up again emails

A Down and an Up again email of an HTTP(S) or Keyword monitor says what happened first, then shows one screenshot of the top of the page on desktop, as a visitor sees it. You see what happened without opening the website. The alert email links to the incident's page, which shows every screenshot we took.

  • When: under the screenshot, the date and the time it was taken. It is taken from another place than our checks, so it can differ from what they saw; when it does, the email says so.
  • Inside the email: the screenshot is part of the email, so your mail program shows it without loading anything from outside. An email waits at most a minute for it, then goes without.
  • When there is none, one line says so, and why when we know: the site did not answer, the page did not open, a firewall showed a challenge instead of the page, the page did not open from our screenshot server (some websites let in only our checking servers), many monitors went down at once, most monitors on the server went down, or the screenshot was not ready in time.
  • Several monitors in one email (one server or one host): the screenshot of the first website that has one, and the email says which. When most of a server's monitors are down, the email shows one screenshot for all of them (for a group, one of its own websites) and says so. A group's email only ever shows its own websites.
  • A group's addresses get the screenshot too. When there is none, their email says so, and says why only when a visitor would notice it (the site did not answer, the page did not open, or a firewall's challenge). Their email has no link to the incident's page, which needs a sign-in.
  • Never for Port or Ping monitors, nor for SSL certificate and other emails.
  • Basic Auth: a website behind Basic Auth is opened with its saved user name and password, sent over https to that website only.
  • Kept 30 days, then deleted. A screenshot we keep to learn from an incident is kept up to 25 months. All are deleted with the rest of your account's data when your account is removed. On every plan, never counted against its limits.

Who gets them

  • The alert email gets every email of all your monitors (set it in Notifications). Its emails say everything: a title such as Site Down, the address with its server and group under it, what happened and since when, rows such as Reason and HTTP Code, whether the group was notified, and a button to open the monitor. With priority tags on, their subjects start with a tag.
  • The group's addresses get a monitor's emails when its Group alerts switch is on, and only addresses that are confirmed or have consent on file. Their emails come from your account's name and say only what a visitor would notice: what we saw and when, and that we keep checking. They never name your servers or other addresses. Replies are not read; their footer asks your client to contact you. Still down, the SSL warnings before a certificate runs out, and every email about a test website's Basic Auth go to the alert email only. Group alerts are not on every plan (what each plan includes): where your plan does not include them, the switch is shown off with the plan's name and Comes with that plan, Not on sale yet, groups get nothing, and an address added to a group gets no confirmation email until your plan has them.
  • A check in maintenance keeps checking and sends no emails. Leave maintenance while a problem lasts and the next email (a reminder, or Up again) goes as usual: a Still down held while in maintenance goes then, if the website is still down.

An address that is both the alert email and one of a group's gets one email each time, never two.

Times in an email are in the time zone of the person with that address, if they are on your team, else in the account owner's.

Alert email

Your account has one alert email, on every plan: every alert of all your monitors goes there. At the foot of the side menu, under Manage account, click Notifications. Until an Owner or Admin changes it, it is the account owner's sign-in email.

Owners and Admins click Change beside Alert email, type the address and click Save the alert email: it applies to all your monitors straight away. Use a shared inbox to reach several people. The address of someone on your team is used straight away, for as long as that person is on your team; if they leave, alerts go back to the account owner's sign-in email. Any other address is shown as Unconfirmed under the one in use and gets nothing until it is confirmed; until then alerts keep going to the address in use before. We email it a link to confirm at once (how), and the line under it says when the link went, or that it could not go; Send it again beside it sends the link again, at most once a day. Members and Viewers see the alert email but cannot change it.

Alert emails need a confirmed sign-in email. When the alert email is the sign-in email of someone on your team who has not confirmed it yet (the link we sent when they signed up), no alert email goes out: your monitors keep checking and every incident shows in the app, but its emails are not sent, then or later. Notifications says No alert emails go out until you confirm your email address; Resend in the line at the top of the page sends the link again. When it is someone else's address, ask them to confirm it, or change the alert email. Once the address is confirmed, the next alerts go out.

Your sign-in email gets account emails only: sign-in, security and billing. If your sign-in email is also the alert email, it gets every alert too once you have confirmed it, and the page says so. Each monitor's Who gets alerts shows the alert email with Change in Notifications, which opens your account's Notifications in a new tab.

While a monitor stays down

You get one email when a monitor goes down and one when it is back up. Nothing in between, unless you choose more in your account's Notifications, under While a monitor stays down (at the foot of the side menu, under Manage account, click Notifications). It is saved at once, for every monitor of the account.

Choice Emails while it stays down
No more emails (the default) None.
One reminder after a day One more email if it is still down after 24 hours.
Remind by Priority One after 30 minutes for a P2 monitor or 4 hours for P3 (still down, by Priority), then one after 24 hours for every monitor.

The reminders come with the paid plans. On the free plan every monitor sends one Down and one Up again email.

Still down, by Priority

A short outage often fixes itself; a long one needs someone now. So with Remind by Priority chosen (while a monitor stays down), a monitor still down after a while gets one more email, at a time set by its Priority (on its Settings):

Priority Still down email Its tag, with priority tags on
P1 None extra: its Down email is already urgent
P2, the default After 30 minutes [P1-URGENT]
P3 After 4 hours [P2-ACTION]
P4 None extra

When your plan does not include Priorities, every monitor counts as P2 here, whatever was chosen before.

With priority tags on, its subject reads like [P1-URGENT] STILL DOWN | www.example.com (31m) or [P2-ACTION] STILL DOWN | www.example.com (4h); with them off, like "Still down after 31 minutes: www.example.com" or "Still down after 4 hours: www.example.com", with how long it had been down.

It goes once per outage, to the alert email only, and at least 15 minutes after the Down email reached you. A Down held because the check was in maintenance counts too, since you still need to hear: the email comes 15 minutes after maintenance ends, if the website is still down. It never comes while the check is in maintenance, nor once the website works again. A monitor whose server's outage already came as [P1-URGENT] SERVER OUTAGE (its Down went in that email, or the outage is still open) gets no extra email: you have been paged already (one email for several monitors of one server).

With One reminder after a day or Remind by Priority chosen, every monitor gets the Still down email at 24 hours, tagged with its own Priority. It too waits while the check is in maintenance, and goes when maintenance ends if the website is still down. When the 24-hour email is less than an hour away, only that one goes.

WordPress maintenance mode

While WordPress installs an update it shows visitors "Briefly unavailable for scheduled maintenance". An update usually takes a few minutes, so for its first 10 minutes the monitor shows Updating in amber, with "WordPress maintenance mode since 10:14; counted as down if it lasts past 10:24", and sends no email. If the update finishes within those 10 minutes, they show as needing attention in the bars and count as up. If it gets stuck, the outage counts from the first maintenance page.

If the page is still there after 10 minutes, the update most likely got stuck: once a second checking server agrees, the monitor turns Down, "Down for 12 minutes, since 10:14: WordPress is stuck in maintenance mode", and the Down email says "WordPress is stuck in maintenance mode". The outage counts from the first maintenance page. To end it, delete the .maintenance file in the folder that holds wp-config.php, then check in WordPress, under Dashboard and Updates, that the update finished.

If the 10 minutes are over and no check has looked again yet, the line says "counted as down if the next check still finds it". If the page is still there after 10 minutes in the 30 minutes after a second checking server reached the website (down only when a second place agrees), the monitor shows Stuck in maintenance mode, not counted as down yet, with the same advice; only the pages of the first 10 minutes count as needing attention in the bars, later ones as not counted.

The 10 minutes need two maintenance pages in a row at least. They start again each time the site has answered normally in between, after an outage has ended, and when the check is switched on again or the monitor resumed. Any other error page counts as down as soon as a second checking server agrees.

One email for several monitors of one server

Behind Cloudflare and most hosting, we cannot see which server a website runs on, so you tell us: on a monitor's Settings, type its Server, such as web-03, the same way for every monitor on it (the field suggests the names you already use; capitals and spaces at the ends do not matter).

When a monitor goes down and another monitor of yours that is not paused, with its check on, has the same Server, its email waits up to 3 minutes for the others. All of them that went down by then come in one email per address, such as "3 monitors down on web-03". When more than half of the server's monitors are down at once (with at least 2 on it), the alert email gets one Server outage email, listing every monitor of that server then down, and saying the server itself may be down; when half of its monitors or fewer are still down, one Server recovered email, with how many work again and which are still down. Up again is grouped the same way. A monitor that goes down after that email has gone gets its own email, which mentions the earlier one. A group's address gets one email listing only its own websites, without the server's name. A monitor without a Server, or alone on it, never waits.

One email for several monitors of one host

A monitor with no Server is grouped by its Hosting instead, the host you chose for it on its page (Hosting). Its email waits up to 3 minutes when another of your monitors has the same Hosting and no Server, as for a server. Paused monitors and monitors with their check off do not count. All of them that went down by then come in one email per address, such as "3 monitors down at Example Host", saying how many of your monitors at that host are down. Up again is grouped the same way, such as "Up again at Example Host: 3 monitors".

  • Server comes first. A monitor with both a Server and a Hosting is grouped by its Server only: one server down says more than some websites at one host down, and a server's outage email is never split.
  • Only your own answer counts. What we guess from a website's address or headers never groups alerts; only the Hosting you set does.
  • One host, one name. Capitals and spaces do not matter, and a host you type is written the way the list or your other monitors already write it.
  • There is no host outage email: a host has many servers, so only a Server gets a Server outage email.

A monitor that goes down after that email has gone gets its own email, which mentions the earlier one. A group's address gets one email listing only its own websites, without the host's name.

Can no longer check

Sometimes, after a monitor goes down, something else starts to answer our checks: a firewall's page, or a Basic Auth password prompt that refuses the saved password or asks for one that is not saved. Those answers do not say whether the website behind them works, so they never end an outage on their own and never count as down.

If only such answers come for 2 hours, we end the outage and send Can no longer check. It says at least how long the website was down (until the first of those answers), and what to fix: allow our checks for a firewall, or save the current user name and password in the monitor's Settings, under Basic Auth. The reminders stop. The monitor's page says so for a day, and the monitor shows what our checks see now. Once our checks see the website again, a new failure starts a new outage, with its own Down email.

Priority tags

A mail filter, or a tool that watches your inbox, can sort alerts by the tag at the start of their subject. Switch on Priority tags in subjects in your account's Notifications (at the foot of the side menu, under Manage account, click Notifications). It is off until an Owner or Admin switches it on, and saved at once. Only the subjects of emails to the alert email get tags; a group's emails never do.

With the tags on, a subject reads [TAG] WHAT | address (detail), the address without https://. Each monitor has a Priority, on its Settings and on Add a monitor (under Advanced settings): P1, P2 (the default), P3 or P4. It sets the tag of that monitor's down, keyword and still down emails, and when its first still down email comes (still down, by Priority).

Tag Emails
[P1-URGENT] A server's outage: more than half of the monitors of one Server down at once, with at least 2 monitors on it (SERVER OUTAGE), once per outage. Down, keyword and still down of a monitor set to P1. A monitor set to P2 still down after 30 minutes. An SSL certificate that has expired.
[P2-ACTION] Down, keyword and 24-hour still down of a monitor set to P2, the default. A monitor set to P3 still down after 4 hours. An SSL certificate not trusted or made for another name. Basic Auth off, and all its reminders, however long it stays off. Can no longer check.
[P3-MONITOR] Down, keyword and 24-hour still down of a monitor set to P3.
[P4-LOW] Down, keyword and still down of a monitor set to P4.
[INFO] An SSL certificate that runs out in 5 days, and in 1 day.
[RESOLVED] Up again, a server's or a host's monitors up again, a certificate renewed or trusted again, Basic Auth back on.

For example [P2-ACTION] DOWN | www.example.com (502), [P1-URGENT] SERVER OUTAGE | web-03 (3/5 sites down) or [RESOLVED] RECOVERED | www.example.com (down 42m). Several monitors of one server down together that are half of its monitors or fewer come in one email such as [P2-ACTION] DOWN | www.example.com and 1 more (web-03), tagged with the highest Priority among them. A server's outage ends with [RESOLVED] SERVER RECOVERED once half of its monitors or fewer are still down, such as [RESOLVED] SERVER RECOVERED | web-03 (4/5 up, down 12m); one website that stays down never keeps the outage open. Several monitors of one host come the same way, such as [P2-ACTION] DOWN | www.example.com and 2 more (Example Host) and [RESOLVED] RECOVERED | www.example.com and 2 more (Example Host).

Priority tags and the Priority field come with a paid plan. Where your plan does not include them, the switch and the field are shown disabled with the plan's name and Comes with that plan, Not on sale yet, and subjects have no tag. While the switch is off, the Priority field says so: emails have no tag, and a Priority still sets when the Still down email comes.

Basic Auth warnings

A monitor with the Basic Auth warning on emails you when its test website stops asking for its password. Choose how much in your account's Notifications, under Basic Auth warnings (at the foot of the side menu, under Manage account, click Notifications). It is saved at once, for every monitor of the account.

Choice Emails
Alert, then remind daily (the default) One email when Basic Auth goes off, reminders after 1 hour, 4 hours and 1 day, then every day, and one when it is back on.
Alert, then remind once One email when Basic Auth goes off, one reminder once it has been off a day, and one when it is back on.
Alert only One email when Basic Auth goes off, and one when it is back on.
Off No emails when Basic Auth is off. Emails about a missing or refused password still go out, and each monitor's page shows what the checks find.

To quiet one monitor for a while instead, pause its warnings on its page (pause warnings for 24 hours). The choice comes with the paid plans, as the Basic Auth warning does.

How far back alerts go

How much history you see depends on your plan: a monitor's alerts, under Alerts on its page and under Show all alerts, go back 3 months, 12 months or 24 months. We keep each monitor's outages 13 months or 24 months, depending on your plan, counted from when each one ended, and its alerts as long, counted from when each alert was sent; older ones are deleted in the night. A problem that has not ended yet is never deleted, and its alerts stay shown however old. The Last 30 days figures on a monitor's page are the same on every plan.

Where your plan shows less than we keep, the older alerts are hidden, not deleted. The list ends with a line such as Alerts go back 3 months on this plan. Owners and Admins also see the name of the plan that shows more, with Older history comes with that plan, Not on sale yet. Members and Viewers see Older history is hidden on this plan. Show all alerts appears only when the months your plan shows hold more than 10 alerts.

A move to a plan that shows more shows the hidden alerts at once, as far back as we keep them. A move to a plan that shows less hides the older alerts at once and deletes nothing; the nightly clean-up then keeps them as long as the new plan keeps history.

Confirm an address

An address you add to a group, or an alert email of someone not on your team, gets one email: "Confirm that you want alerts from Example Agency", with a Confirm button. Its owner opens it and clicks Confirm on the page it opens; until then, the address gets nothing. The link works once, for 14 days. Beside an address still waiting, Send it again sends the email again, at most once a day.

Stop the emails

Every email to a group's address has Stop these emails at its foot. One click stops all your account's alerts to that address; the group's page and Who gets alerts then say "Stopped by its owner" with the date. Only its owner can start them again, by clicking Confirm in a confirmation email: use Send it again if they ask for it (once after each stop). Removing the address and adding it again keeps it stopped.