Skip to main content

Uptime History

The One Status tracks component availability over time using automated HTTP monitoring. Uptime data appears on both the management console and the public status page.

How Uptime Is Measured​

Uptime data is only collected for components that have automated monitoring configured (URL, interval, timeout, and expected status codes). Components managed purely by manual status updates do not accumulate automated uptime data.

For monitored components:

  1. A health check runs against the configured URL every minute
  2. Each check is recorded as up, down, or degraded based on the HTTP response
  3. Checks are aggregated into hourly and daily summaries
  4. The 90-day rolling uptime percentage is calculated from daily summaries

90-Day Uptime Percentage​

Each component displays a 90-day rolling uptime percentage — the percentage of the past 90 days during which the component was operational.

Calculation:

Uptime % = (minutes up / total minutes in 90 days) × 100

For example, if a component was down for 6 hours in 90 days:

Total minutes = 90 × 24 × 60 = 129,600
Down minutes  = 6 × 60 = 360
Uptime %      = ((129,600 - 360) / 129,600) × 100 = 99.72%

Uptime Display on Public Page​

If Show Uptime Percentage is enabled in page settings, each component on the public status page shows:

  • Uptime percentage as a number (e.g., 99.98%)
  • Uptime bar — a visual 90-day timeline where each day is a small colored bar

Uptime Bar Colors​

ColorMeaning
GreenDay had 100% (or near 100%) uptime
YellowDay had degraded periods
OrangeDay had a partial outage
RedDay had a major outage
GrayNo data (monitoring was not configured for that day)

Hovering over a bar shows the date and uptime percentage for that day.

Uptime in the Management Console​

In the Components tab, click any component to view:

  • Overall 90-day uptime percentage
  • Response time chart — average response time per hour over the past 24 hours (or longer)
  • Recent checks table — last N individual check results, including timestamp, check status (up/down/degraded), response time in milliseconds, and HTTP status code

See Performance Metrics for more on response time charts and recent checks.

History Period​

The History Days setting (in page settings) controls how many days of incident history are displayed on the public page. This is separate from uptime data — uptime always reflects a rolling 90-day window regardless of the history days setting.

Interpreting Downtime Periods​

When clients view the uptime bar and see a red or orange day:

  1. They can see the exact date from the tooltip
  2. You can cross-reference incidents from that date in the incident history section
  3. If an incident was declared, clients can see the title, updates, and postmortem
💡If a red bar in the uptime history has no associated incident, consider retroactively creating a resolved incident to explain the downtime. Unexplained outages look worse than documented ones.

Uptime Data Accuracy​

A few things to know:

  • Monitoring origin: Checks originate from The One Status infrastructure. If your service is internally hosted and the check URL is not publicly accessible, checks will show as down.
  • False positives: Temporary network blips between The One Status and your endpoint may register as downtime. These are typically brief (1–2 minutes) and visible as individual red entries in recent checks without extended impact on the uptime %.
  • Check interval: The minimum check interval is configured per component. More frequent checks provide more granular data but the uptime % calculation is the same.
  • Data retention: Raw check data is available in the recent checks table. Aggregated daily metrics are retained for 90 days. Checks older than 90 days are not displayed.