Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion communicate/status-pages/maintenance-windows.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -69,6 +69,7 @@ With the setting off:

- The maintenance card and its detail page list no components, and no component on the page is marked as under maintenance.
- Subscriber notifications leave out the affected components.
- Incident downtime during the maintenance lowers uptime as usual.

## Posting updates to your status page

Expand Down Expand Up @@ -110,4 +111,4 @@ Turn on **Don't open incidents** in the status page visibility settings. While t
This option applies only to the components covered by the maintenance on the pages it is shown on.
</Note>

Maintenance doesn't change your status page **uptime**: incident downtime that overlaps a maintenance counts the same as any other downtime.
Incident downtime on an affected component while the maintenance is active does not lower the component's **uptime**.
2 changes: 2 additions & 0 deletions communicate/status-pages/overview.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -62,6 +62,8 @@ Uptime is calculated over the **last 90 days**, per component, from incident imp
Uptime = ((Total time - Weighted downtime) / Total time) × 100
```

Downtime during a [maintenance window](/communicate/status-pages/maintenance-windows) that covers the component is not counted.

A group shows the average uptime of its child components. Uptime is driven by incidents, not directly by check results: without an automation rule or a manually created incident, a failing check does not lower uptime.

## Monitoring as code
Expand Down
Loading