Every monitor carries one status, drawn as a colored pill on the dashboard and as a badge beside the monitor's name on its own page. There are seven. Three of them, Warning, Degraded and Suspended, mean something the color alone will not tell you. If a monitor has stopped checking or stopped alerting, Why a Monitor Stopped Checking names the cause.
Every Status #
| Status | Color | What it means | What to do |
|---|---|---|---|
| Up | green | The last check succeeded and no incident is open | Nothing |
| Down | red | A critical incident is open: the thing being checked failed | Open the monitor and read the incident |
| Warning | amber | A Security monitor has an open incident: a check found an issue at or above the monitor's alert level. Security monitors read Warning where other families read Down | Open the monitor and read the finding |
| Degraded | amber | A degraded incident is open and no critical one: the thing being checked still works, but a limit you set was crossed | Open the monitor and read the incident |
| Paused | gray pill with a yellow dot | Someone paused the monitor. No checks run, no alerts fire | Resume it from the monitor's row menu, or leave it |
| Maintenance | violet | A maintenance window covering this monitor is running | Nothing. On most families a line under the monitor name gives the window and its end time |
| Suspended | gray | The monitor is over your plan's limit for its type | Move to a plan that covers it; deleting other monitors does not lift the flag on its own |
The dashboard, the monitor's own page and the incident pages all use the same word. A monitor with an open degraded-severity incident reads Degraded on each of them. The DNS and blacklist pages are the one difference: their red status reads Critical instead of Down, for example Critical · 2 active listings. On the DNS page a record change below critical reads Warning, for example Warning · <changed record>, while the dashboard shows that monitor as Degraded. A health problem reads Degraded on both.
How Uptimia Picks the Status #
A monitor can be several things at once: paused, over the plan limit, and inside a maintenance window. One status wins, in this order:
- Suspended, which outranks everything.
- Paused and Maintenance.
- Down, when a critical incident is open (Warning on a Security monitor).
- Degraded, when only degraded incidents are open.
- Up.
A monitor that is both paused and inside a maintenance window renders either of those two, and which one you see varies by screen. The other four levels are consistent everywhere.
Some families add a neutral state outside the seven, for a monitor that has never produced a result. None of them is green, because nothing has been measured yet. On the dashboard, a server, heartbeat or DNS monitor in this state sits under Awaiting data in the filter. An API or blacklist monitor waiting for its first run is not counted there.
| Monitor family | Neutral state | Shown until |
|---|---|---|
| Heartbeat | Pending first ping | you send the first ping |
| API | Pending | the monitor runs for the first time |
| Blacklist | Pending · first sweep | the first sweep finishes |
| Server | Awaiting agent | the agent reports for the first time |
| DNS | Waiting for first sweep… (Awaiting first sweep on the dashboard) | the first sweep finishes |
A DNS monitor whose sweeps cannot run at all reads Not monitoring in amber instead. On the dashboard the row gives the reason, for example No nameservers found for this zone. Nothing is being watched until you fix the zone or the monitor. A Security monitor with no open incident reads Unknown in gray when none of its checks reached a verdict; once one check does, it reads Up.
Degraded: Which Checks Produce It #
The status follows the severity of the monitor's open incidents. One open critical incident makes it Down. Open degraded incidents with no critical one make it Degraded, on the dashboard and on the monitor's page alike.
Every incident Uptimia opens is stamped either critical or degraded. Critical means the thing being checked failed. Degraded means it still works and a limit you set was crossed, which turns the monitor's status amber. Severity belongs to the incident rather than the monitor, so the same monitor can raise a degraded incident one week and a critical one the next. Webhook payloads and the API still carry the value trouble for a degraded incident.
A person can also open an incident by hand. An Owner, Admin or Editor picks Open manual incident from the monitor's menu and chooses Critical, which shows the monitor as Down, or Degraded. While it is open, Uptimia stops judging that monitor automatically until someone resolves it. Manual incidents work on every family except Real User, and a Security monitor holding one reads Down or Degraded rather than Warning.
| Monitor family | Opens a critical incident | Opens a degraded incident |
|---|---|---|
| Uptime | Any confirmed failed check | None |
| Transaction | A failed step | None |
| API | A failed request or assertion | None |
| Heartbeat | A missed ping | None |
| Server | The agent stops reporting (offline) | Any threshold alert (CPU, memory, disk, load, swap, process count, inodes or network I/O) |
| Speed | The page fails to load | Average load time over your threshold; a web-vitals budget breached; a watched page element failing while the page stays up |
| Real User | Visitor traffic stops | Average speed dropped; traffic volume dropped; JavaScript errors over your percentage |
| SSL | Certificate expired, or expiring within 45 days | Certificate expiring, but more than 45 days out |
| Domain | Registration expired, or expiring within 3 days | Registration expiring, but more than 3 days out |
| DNS | Every nameserver unreachable; a change in a record group set to critical (A/AAAA/CNAME, MX and NS are critical by default) | One nameserver unreachable; serial drift between servers; a parent/child delegation mismatch; a server not answering authoritatively; a change in a group set to Warning (SPF/DMARC/CAA by default) |
| Security | A finding at or above the monitor's Alert on level (Critical only or High and critical), or a Google Web Risk flag for malware, social engineering or unwanted software. The monitor reads Warning, and the incident adds no downtime | None |
| Blacklist | A listing on a major-tier list (critical by default), and any re-listing within 7 days of a verified delisting | A listing on a standard-tier list (Degraded by default) |
The SSL and domain thresholds are family constants, and your alert lead time is a separate setting. Each SSL and domain monitor has its own Expiry warning lead time, picked from a fixed list of seven values that runs from 1 day up to 90 days. The default is 7 days. No alert opens until expiry falls inside that lead time. The family's own threshold then decides the severity: 45 days for SSL, 3 days for domain. With the default 7-day lead time an SSL monitor always opens a critical incident when it alerts, because 7 days sits inside the 45-day critical band. A domain monitor opens a degraded incident on days 7 to 4 and a critical one at 3 days out.
An info-tier blacklist listing leaves the status alone. Uptimia records it and counts it on the monitor's page. It opens no incident and alerts nobody, so the monitor stays Up. Each tier's severity is a per-monitor setting: the editor's blacklist card lets you set Major and Standard to Critical or Degraded.
The Healthy Cell Counts Up Monitors Only #
The dashboard's Healthy cell counts monitors that are Up. A degraded monitor is not counted in it, and neither is a down, paused, suspended or maintenance one. The Monitors cell's sub-line gives each count, for example 19 up · 3 down · 2 warning. Its warning number covers degraded monitors and Security monitors at Warning together.
The Active Incidents sub-line counts open incidents rather than monitors, split by severity: 3 critical · 2 degraded. A monitor with two open degraded incidents adds 2 there and 1 to the warning monitor count. An automatic Security incident counts as critical there. The Warning filter chip below the summary selects the same monitors the Monitors cell counts as warning, and each row keeps its own word, Warning or Degraded.
Paused #
Pausing is your own switch, from a monitor's row menu (Pause / Resume) or from the bulk action bar after selecting rows. It stops the checks: the monitor leaves the check queue, and a check that is already running is thrown away instead of counted. Whatever was already queued goes quiet. Any down alert that has not gone out yet is deleted. The incident's escalation ladder and alert-group membership stop, so a ladder cannot keep paging a monitor nobody is checking.
Pause never touches the plan. Resuming needs no upgrade and is never refused.
Maintenance #
A monitor is in Maintenance while a window covering it is running. Uptimia stops checking it for the duration. A probe result that arrives anyway is dropped, so it cannot be logged, open an incident or fire an alert.
The two inbound families are the exception. A heartbeat still logs its pings and a server monitor keeps recording the readings its agent sends, so their charts keep filling and only the alerting goes quiet.
On uptime, SSL, speed, domain, transaction, Security and server pages, a line under the monitor's name reads Under maintenance until <end time> · <window name>. That line links to Maintenance. The DNS, blacklist, API, heartbeat and RUM pages show only the violet Maintenance badge. Scheduling is covered in Maintenance Windows.
Suspended: A Plan Limit, Never a Failing Check #
A suspension comes from billing, never from a failed check. Your plan can drop in a few ways: you downgrade, your trial ends and the account moves to Free, or a failed-payment sequence reaches its end. Uptimia then reconciles each monitor family against the new limit and suspends the excess. It keeps the oldest monitors and suspends the newest ones over the line, then emails you a list of the monitors it suspended. Suspended monitors are not deleted and their history is not touched.
Uptimia stops checking a suspended monitor and stops alerting on it. Nothing on the monitor clears the flag. Moving back up to a plan that covers them reactivates them, oldest first, and Uptimia emails you to say the monitors are running again. Reactivation only ever clears the suspension: a monitor you had paused yourself stays paused. Per-family limits are in Plan Limits and Quotas.
What Each Status Does to Your Numbers #
| Status | Checks run | Alerts fire | Counts in the dashboard's fleet Availability |
|---|---|---|---|
| Up | Yes | — | Yes |
| Down | Yes | Yes | Yes, the incident consumes downtime seconds |
| Warning | Yes | Yes | Yes, but a Security incident adds no downtime seconds |
| Degraded | Yes | Yes | Yes, but a degraded incident adds no downtime seconds |
| Paused | No | No | No, the Paused cell's sub-line says "excluded from availability" |
| Maintenance | No | No | Yes, but the maintenance window is left out of both the downtime and the total time |
| Suspended | No | No | No |
Real User monitors are excluded from the fleet Availability average whatever their status, because they report visitor timings rather than availability.
Only a critical incident adds downtime seconds. A speed monitor sitting amber over a vitals budget stays in the average, and its availability percentage does not move. A certificate or domain that has not expired yet adds no downtime either, even inside the 45-day or 3-day band where its incident is critical. An automatic Security incident adds none either. A critical manual incident on a Security monitor does count, and the monitor reads Down while it is open. On the Professional plan and above you can also change an incident's Availability impact from its More actions menu, so that it counts in full, not at all, or only for part of its time. The arithmetic behind all of this is in How Uptime Is Calculated.
Filtering the Dashboard by Status #
The chip row under the summary filters the monitor list: All, Up, Down and Warning. The Warning chip holds degraded monitors and Security monitors at Warning. A More dropdown beside them holds Awaiting data, Paused, Maintenance, Suspended and No recipients. Each entry carries a live count for the monitors in view, and an entry whose count is zero is hidden, so a missing Suspended entry under More means nothing is suspended. Clicking an active chip clears the filter. The six summary cells above are clickable too and drive the same filter.
No recipients filters on coverage, not status: it selects monitors that would page nobody if they went down, because no contact, team or escalation policy is attached. A monitor can be green, healthy and on that list at the same time. Fix it from the monitor's Alerting card.