Skip to content
Merged
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
4 changes: 4 additions & 0 deletions content/en/incident_response/status_pages/_index.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down Expand Up @@ -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.
Expand Down
Loading