Sazabi
Status Pages

Status Timeline

Understanding the 7-day status timeline, bucket structure, and uptime calculation.

Each component on your status page includes a status timeline showing its health over the past 7 days. The timeline provides a quick visual history of when the component was operational, degraded, or experiencing an outage.

Timeline structure

The timeline is divided into 28 buckets, each representing a 6-hour window. This creates a 7-day view:

28 buckets x 6 hours = 168 hours = 7 days

Each bucket shows the worst status that occurred during that 6-hour period. Reading left to right, you can see how component health has changed over the past week.

Why 6-hour buckets?

Six-hour buckets balance detail with readability:

  • Granular enough to show when incidents occurred during a day
  • Coarse enough to fit a full week on screen
  • Aligned with common operational patterns (morning, afternoon, evening, night)

Status per bucket

Each bucket displays one of four statuses based on what occurred during that time window:

Operational

The component had no active issues during this period. Displayed with a green indicator.

Degraded

The component had one or more degraded issues during this period, but no outages. Displayed with a yellow indicator.

Outage

The component experienced an outage during this period. Displayed with a red indicator.

Unknown

No status data exists for this period. This typically means the component had not yet been discovered. Displayed with a gray indicator.

Worst severity wins

When multiple issues overlap within a single 6-hour bucket, the bucket shows the worst severity that occurred:

Issues in bucketBucket status
NoneOperational
Degraded onlyDegraded
Outage onlyOutage
Degraded + OutageOutage

For example, if a component had a 2-hour degraded issue and a 30-minute outage within the same 6-hour window, that bucket shows as "Outage" because outage is the more severe condition.

Unknown status

A bucket shows Unknown status when no data exists for that time period. This occurs in two situations:

Before component discovery

When a component is newly discovered, buckets before the discovery timestamp show as unknown. For example:

  • Component discovered 3 days ago
  • Buckets from days 4-7 show as unknown
  • Buckets from days 1-3 show actual status

Data gaps

If there is a gap in status tracking (rare), affected buckets may show as unknown rather than assuming operational status.

Uptime calculation

Each component displays an uptime percentage based on its timeline data. Uptime is calculated as:

Uptime = (Total time - Outage time) / Total time x 100

Important notes about uptime calculation:

  • Degraded time does not reduce uptime: Only outages count against uptime
  • Unknown time is excluded: Buckets with unknown status are not included in the calculation
  • Resolution matters: A 30-minute outage has the same impact whether it is in a quiet period or during peak hours

Example calculation

Consider a component over 7 days (168 hours):

StatusDuration
Operational150 hours
Degraded12 hours
Outage6 hours
Uptime = (168 - 6) / 168 x 100 = 96.4%

The 12 hours of degraded status do not affect the uptime percentage.

Uptime calculations use the precise issue timestamps, not the 6-hour bucket boundaries. A 15-minute outage counts as 15 minutes of downtime, not a full 6-hour bucket.

Timeline interpretation

When reviewing the timeline:

  • Clusters of red/yellow indicate recurring or persistent problems
  • Isolated incidents show up as single colored buckets
  • Recent greens after reds suggest successful resolution
  • Unknown gaps typically indicate new components

The timeline helps you quickly answer questions like:

  • Has this component been stable this week?
  • When did the last outage occur?
  • How long did recent incidents last?
  • Is this a new or long-standing component?

Next steps