What Visitors see

A Visitor is anyone who opens your Status page. Visitors need no account, and the page tells them one thing: whether your Monitors are up.

The page has five parts, from top to bottom: your logo, the banner, one row for each Monitor on the page, the Incident history, and the footer. A switch at the top lets each Visitor choose Auto, Light or Dark.

The four words

Each row shows the Monitor’s name and one of four words. The first word whose rule holds is the one shown:

Word	When it is shown
Not monitored	The Monitor is paused or suspended, or it is a heartbeat still waiting for its first call.
Down	An Incident is open on the Monitor.
No data	We have had no new result for the Monitor over its last 3 intervals, and at least 90 seconds. A failure we could not confirm, with no good result since, reads No data too, and so does a heartbeat while we are not receiving heartbeat calls ourselves.
Operational	None of the above. A warning, a snoozed Check and a Regional outage all leave the word Operational.

Operational is green, Down is red, and the other two are grey. Your accent color never changes them.

A row reads only the Monitor’s uptime: whether it answers. Its other Checks, such as a certificate or a domain, never reach the page.

The banner

One line above the rows sums up the page. Monitors that read Not monitored are left out of it.

When	The banner says
No Monitor is on the page	Nothing is published on this page yet.
Every Monitor reads Not monitored	Nothing is being monitored right now.
Two or more Monitors are watched, and all of them are Down	All systems are down.
One Monitor is Down	API is down.
Two or three Monitors are Down, named one by one	API and Checkout are down.
More Monitors than that are Down, counted	4 of 9 systems are down.
None is Down, and one or more reads No data	We are not receiving data for some systems.
Every other case	All systems operational.

Under the banner, the page says when it was made, such as Updated 14:05. This page refreshes every minute. The page reloads itself, so a Visitor who keeps it open sees changes without doing anything.

The uptime bars

Each row has a bar of 90 days, one for each day in your Project’s timezone, oldest on the left and today on the right.

• A day with any downtime is red from the top, as much of the cell as the day was down, and at least 20% of it, so a short outage still shows.
• A day with no downtime is green.
• A day we could not watch for most of is grey, and says only “no data”, never why.

Pointing at a day, or moving to it with the keyboard, shows one line: 2 Oct: no downtime, 2 Oct: down 4 minutes or 2 Oct: no data.

An Incident reported in error is not downtime, so its day goes back to green.

Under the bar, one line gives the Monitor’s uptime over the whole bar, such as 99.97 % uptime over 90 days. When there were hours we had no data for, it says how many: 99.97 % uptime over 90 days · 3 hours without data. With nothing to go on, it says No data over the last 90 days.

The Incident history

Below the rows, the page lists every Incident on its Monitors in the last 90 days, newest first, up to 100 Incidents. A line under them counts any more. Each entry is one sentence in plain words, with the day it began beside it:

The Incident	The sentence	Under it
Still open, marked Ongoing	API has been down since 14:02.	From 14:02
Closed	API was down for 39 minutes.	14:02 to 14:41
Reported in error, struck through and marked Retracted	API was reported as down in error.	Our monitoring was at fault. The service was working.

An Incident you resolved, or one closed when you paused the Monitor, reads as closed: the downtime before it was real.

The footer

The footer names your Project’s timezone, which every time on the page is in, such as All times are Europe/Istanbul (UTC+03:00). Under it is the line “Powered by uup”, unless a paid plan turned it off.

What a Status page never shows

• a warning, such as a certificate about to expire or slow answers
• a failure we have not confirmed
• answer times, charts or any other figure but uptime
• the names of our locations, or which location saw what
• a Regional outage
• why a Monitor failed: an Incident’s entry says only what was down and for how long
• a Monitor that is not on the page, and a Monitor’s other Checks

A Status page also has no menus, no search, no sign-up and no cookies. It loads nothing from anywhere but its own address.

When a Project is suspended, its page says only that it is not published at the moment, with no Monitors on it.