Repository navigation
docs: status page maintenance plans and uptime on v3 pages (DOC-147) - #741
Merged
Merged
Conversation
- Status page maintenance is included in Communicate Team and Enterprise, not every Communicate add-on (Hobby and Starter don't include it). - Maintenance doesn't change status page uptime: on v3 pages, incident downtime that overlaps a maintenance counts like any other downtime. Measured on the local stack: a 626 s major outage during an in-progress maintenance brought the component's uptime to 99.992 (no exclusion). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
hlenke
commented
Oct 28, 2026
| </Note> | ||
|
|
||
| Incident downtime that overlaps a published maintenance period is excluded from your status page **uptime**. Windows with [**Show affected components**](#hiding-affected-components) turned off are the exception: their overlapping downtime still counts. | ||
| Maintenance doesn't change your status page **uptime**: incident downtime that overlaps a maintenance counts the same as any other downtime. (On deprecated v2 pages, overlapping downtime is still excluded when **Show affected components** is on.) |
Member
Author
There was a problem hiding this comment.
Leave this out: (On deprecated v2 pages, overlapping downtime is still excluded when Show affected components is on.)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
hlenke
marked this pull request as ready for review
October 28, 2026 20:16
hlenke
enabled auto-merge
October 28, 2026 20:16
hlenke
disabled auto-merge
October 28, 2026 20:16
hlenke
enabled auto-merge
October 28, 2026 20:16
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes DOC-147.
The status page maintenance page was mostly right, but two things were wrong.
1. Which plans include it. The page said status page maintenance is part of "the Communicate add-on". It's only included in Communicate Team, not Hobby or Starter, and Enterprise (contract) accounts always have it. The note and the prerequisite now say "Communicate Team and Enterprise plans", the same wording the other status page pages use.
2. Uptime. The page said that incident downtime during a maintenance is left out of your status page uptime. On today's status pages (v3) that isn't true: downtime during a maintenance counts like any other downtime. The page now says so. I also removed a bullet that only made sense under the old claim.
How it was proven
communicate-team.tsincludes the feature,communicate-hobby.tsandcommunicate-starter.tsdon't, and contract accounts are always entitled (plan-overrides.ts)npm run check:linksand vale pass. An independent reviewer checked the diff against the code and the measurement and found nothing wrong. Its optional v2 aside was applied and then removed in review, because the page covers v3. The proof resources were deleted afterwards.Noticed, not changed
POST /v1/maintenance-windows) can't attach a maintenance to a v3 page. It answers "The selected status pages have no services", because it only understands v2 services. The Checkly app uses an internal field (componentConfigs) instead. That's a product gap, not a docs error.uptime-calculations.tssays "v3 pages ship without maintenance window support for now". That's stale: maintenance works on v3, only the uptime part is missing.🤖 Generated with Claude Code