Skip to content

docs: clarify maintenance uptime calculation #457

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
shiini2 wants to merge 2 commits into
base: main
Choose a base branch
from
Draft

docs: clarify maintenance uptime calculation #457

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
19c8b9f
docs: clarify maintenance uptime calculation
shiini2 Jul 27, 2026
419509a
Merge branch 'main' into agent/clarify-maintenance-uptime-docs
shiini2 Jul 28, 2026
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
2 changes: 1 addition & 1 deletion communicate/status-pages/maintenance-windows.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -106,4 +106,4 @@ Turn on **Don't open incidents** in the status page visibility settings. While t
This option applies only to the services covered by the maintenance on the pages it is shown on. A service that also appears on another page, where it is not under maintenance, can still get an automatic incident there.
</Note>

Maintenance periods are also excluded from your status page **uptime**, so planned maintenance does not count as downtime against your services.
Incident downtime that overlaps a published maintenance period is excluded from your status page **uptime**. If you turn off **Show affected services**, overlapping incident downtime still counts against uptime.
Loading