---
title: X
description: If a report ever showed 98% while the monitor page said 100%, you were not imagining it; that was our inconsistency. Uptime now means one thing everywhere…
canonical: https://watchfor.io/changelog/2026-09-03-uptime-one-formula
---

[All updates](/changelog/page/5#2026-09-03-uptime-one-formula) ⚡ Improved Sep 3, 2026 · v 6.4.3

# One uptime formula everywhere: dashboard, monitor pages, reports and the API

If a report ever showed 98% while the monitor page said 100%, you were not imagining it; that was our inconsistency. Uptime now means one thing everywhere: 100% minus time in confirmed critical incidents, with scheduled maintenance neutral, shared by the monitors list, monitor page, dashboard, reports and the API's uptime endpoint. The raw check signal stays visible as a separate check success rate (in reports, and check_success_percent in the API). Monitors younger than 24 hours are judged on the time they have existed and say "since created".

## Why the numbers disagreed

Different screens counted different things. The monitor page counted time spent in confirmed incidents. Reports and the API counted failed checks, so a single timeout from one location that never became an incident still took a bite out of uptime. Same monitor, same week, two answers.

## The formula

uptime = (observed time − time in confirmed critical incidents − scheduled maintenance) / observed time

- Only critical incidents count. A warning incident shows the monitor as Degraded but does not lower uptime.

- Scheduled maintenance is neutral: neither up nor down.

- A failed check that was never confirmed as an incident does not count as downtime.

## Example

Your API monitor checks every minute from three locations. On Tuesday one location times out twice at 03:12 while the other two reach the API fine, so no incident opens. On Thursday a bad deploy takes the API down for 22 minutes, confirmed from all three locations. The week's uptime is 99.78 %, and only Thursday's 22 minutes count. Tuesday's timeouts show up in the check success rate, which is where you look for a flaky location.

## Where it applies

The monitors list and its sort, the monitor page, the dashboard, reports and the API's uptime endpoint. A monitor younger than a day is judged on the time it has existed and says since created . Details in [How uptime is calculated](/docs/monitors#how-uptime-is-calculated).

Since then: incidents marked as false positives are left out ([false positives](/changelog/2026-09-04-incident-false-positive)), and the Uptime SLA tab follows the same rule ([Uptime SLA accuracy](/changelog/2026-09-06-uptime-sla-accuracy)).

Share this update

---

Canonical page: https://watchfor.io/changelog/2026-09-03-uptime-one-formula · Site guide: https://watchfor.io/llms.txt