From 553bb2390ecdb012d22af3cae7b3c2bd1a7a4ffc Mon Sep 17 00:00:00 2001 From: Ryan Peffers Date: Thu, 4 Jun 2026 21:20:54 -0400 Subject: [PATCH] Add note for cap on active notices --- content/en/incident_response/status_pages/_index.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/content/en/incident_response/status_pages/_index.md b/content/en/incident_response/status_pages/_index.md index 7586bbc00e3..592266edb0f 100644 --- a/content/en/incident_response/status_pages/_index.md +++ b/content/en/incident_response/status_pages/_index.md @@ -143,6 +143,8 @@ After a degradation notice is reviewed and published, it: You can publish updates over time and mark the notice as **Resolved** when the issue is fully mitigated. +**Note**: Each status page supports a maximum of 100 active (unresolved) degradations at a time. + ### Backfill a degradation Backfilled degradations allow you to retroactively document service disruptions that were not previously announced. Each update can be assigned its original timestamp, so the incident timeline appears accurately in your uptime history. @@ -181,6 +183,8 @@ After reviewing and scheduling, the maintenance window: You can post updates if plans change or reschedule the maintenance window as needed. +**Note**: Each status page supports a maximum of 100 scheduled or in-progress maintenance windows at a time. + ### Backfill a maintenance window Backfilled maintenance windows allow you to retroactively document planned downtime that was not previously announced. Each update can be assigned its original timestamp, so the maintenance timeline appears accurately in your uptime history.