---
title: Notices
description: >-
  Publish degradations and schedule maintenance windows to communicate service
  impact on a status page.
breadcrumbs: Docs > Incident Response > Status Pages > Notices
---

> For the complete documentation index, see [llms.txt](https://docs.datadoghq.com/llms.txt).

# Notices

{% callout %}
# Important note for users on the following Datadog sites: app.ddog-gov.com, us2.ddog-gov.com

{% alert level="danger" %}
This product is not supported for your selected [Datadog site](https://docs.datadoghq.com/getting_started/site.md). ({% placeholder "user-datadog-site-name" /%}).
{% /alert %}

{% /callout %}

Notices are messages published to a status page to communicate system status. Status Pages support two types of notices: **degradations** for unplanned service impact and **maintenance windows** for planned downtime.

{% image
   source="https://docs.dd-static.net/images/incident_response/status_pages/select_notice_type_status_page.02deb3be62eef0ce4233a921105a84f1.png?auto=format&fit=max&w=850 1x, https://docs.dd-static.net/images/incident_response/status_pages/select_notice_type_status_page.02deb3be62eef0ce4233a921105a84f1.png?auto=format&fit=max&w=850&dpr=2 2x"
   alt="Status page notice type selector with degradation and scheduled maintenance options" /%}

## Publish a degradation{% #publish-a-degradation %}

{% image
   source="https://docs.dd-static.net/images/incident_response/status_pages/shopist_status_page_degradations2.49aa9b1f7f2c2c5d8377ffaf53492030.png?auto=format&fit=max&w=850 1x, https://docs.dd-static.net/images/incident_response/status_pages/shopist_status_page_degradations2.49aa9b1f7f2c2c5d8377ffaf53492030.png?auto=format&fit=max&w=850&dpr=2 2x"
   alt="Example status page showing service components experience degradation" /%}

Degradation notices communicate **unplanned service impact**, such as incidents or service disruptions. Use degradation notices to keep users informed as an issue is investigated, mitigated, and resolved.

From a status page, click **Publish Notice** and select **Degradation**, then provide:

| Field                   | Description                                                                                                                                                                                                             |
| ----------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Notice title**        | Short, clear description of the issue*Example: Increased error rates in US region*                                                                                                                                      |
| **Status**              | Current state of the issue:- Investigating- Identified- Monitoring- Resolved                                                                                                                                            |
| **Message**             | Additional details for your users*Example: We are aware of the issue and are actively working on a fix.*                                                                                                                |
| **Components impacted** | One or more components affected by the degradation                                                                                                                                                                      |
| **Impact**              | Impact level per component:- Operational- Degraded Performance- Partial Outage- Major Outage                                                                                                                            |
| **Notify subscribers**  | Toggle to send updates to subscribed users. Email also requires the page-level [**Notify subscribers**](https://docs.datadoghq.com/incident_response/status_pages/subscriptions.md#enable-email-subscriptions) setting. |

{% image
   source="https://docs.dd-static.net/images/incident_response/status_pages/publish_status_page_degradation_1.a3b292ad266c764dff84c62843c73216.png?auto=format&fit=max&w=850 1x, https://docs.dd-static.net/images/incident_response/status_pages/publish_status_page_degradation_1.a3b292ad266c764dff84c62843c73216.png?auto=format&fit=max&w=850&dpr=2 2x"
   alt="Example publish notice modal for degradations" /%}

After a degradation notice is reviewed and published, it:

- Appears on the **Status Pages List** under Active Notices.
- Updates the uptime bars for impacted components. Components set to **Partial Outage** or **Major Outage** also have their uptime percentage reduced for the duration of the impact.
- Is visible in the notice history timeline.

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{% #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.

From a status page, select the dropdown next to **Publish Notice**, select **Publish Backfilled Notice** > **Degradation**, then provide:

| Field            | Description                                                                                                                                                                                               |
| ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Notice title** | Short, clear description of the incident*Example: Increased error rates in US region*                                                                                                                     |
| **Updates**      | Exactly two timestamped updates representing the start and end of the degradation. Each update requires a started at timestamp, status (Investigating or Resolved), description, and affected components. |

{% image
   source="https://docs.dd-static.net/images/incident_response/status_pages/publish_status_page_backfill_degradation.f56f52bfcd726ca64f71c7b69eb362b8.png?auto=format&fit=max&w=850 1x, https://docs.dd-static.net/images/incident_response/status_pages/publish_status_page_backfill_degradation.f56f52bfcd726ca64f71c7b69eb362b8.png?auto=format&fit=max&w=850&dpr=2 2x"
   alt="Example publish backfilled notice modal for degradations" /%}

## Edit a degradation update{% #edit-a-degradation-update %}

After publishing a degradation update, you can edit its status and message to correct typos, fix an inaccurate status selection, or clarify the description. To edit an update, open the degradation notice on the status page, hover over the update you want to modify, and click the edit icon that appears. Make your changes in the **Edit Update** modal.

{% image
   source="https://docs.dd-static.net/images/incident_response/status_pages/edit_degradation_update.ad83942cbdfd699b324e288bc751017a.png?auto=format&fit=max&w=850 1x, https://docs.dd-static.net/images/incident_response/status_pages/edit_degradation_update.ad83942cbdfd699b324e288bc751017a.png?auto=format&fit=max&w=850&dpr=2 2x"
   alt="Edit Update modal showing Notice Status options and a Message field" /%}

Only the **Notice Status** and **Message** fields can be edited. To resolve the notice or update affected components, add a new update instead. Click **Save Changes** to apply the edits.

## Delete a degradation update{% #delete-a-degradation-update %}

To delete an update posted by mistake, open the degradation notice on the status page, hover over the update you want to delete, and click the delete icon that appears. Confirm in the **Delete Update** modal.

{% image
   source="https://docs.dd-static.net/images/incident_response/status_pages/delete_degradation_update.53981802ca3a4ad7d657f52e19f8f301.png?auto=format&fit=max&w=850 1x, https://docs.dd-static.net/images/incident_response/status_pages/delete_degradation_update.53981802ca3a4ad7d657f52e19f8f301.png?auto=format&fit=max&w=850&dpr=2 2x"
   alt="Delete Update confirmation modal" /%}

Deleting an update replaces it on the timeline with a note indicating it was deleted by the page administrator. This action cannot be undone.

## Schedule a maintenance window{% #schedule-a-maintenance-window %}

{% image
   source="https://docs.dd-static.net/images/incident_response/status_pages/shopist_maintenance_example.986133754af461c3e4f5df00f37613ce.png?auto=format&fit=max&w=850 1x, https://docs.dd-static.net/images/incident_response/status_pages/shopist_maintenance_example.986133754af461c3e4f5df00f37613ce.png?auto=format&fit=max&w=850&dpr=2 2x"
   alt="Example status page showing service components undergoing maintenance" /%}

Maintenance windows allow you to proactively communicate planned downtime or service impact before it happens. Unlike degradations which are used for unplanned incidents, maintenance windows are scheduled in advance for infrastructure upgrades, system maintenance, database migrations, and other planned work. This allows you to keep customers informed and reduce support volume.

From the status page, click **Schedule Maintenance**, or click **Publish Notice** and select **Scheduled Maintenance**. Then, provide the following details:

| Field                   | Description                                                                                                                                                                                                                     |
| ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Notice title**        | Clear description of the maintenance activity*Example: Database infrastructure upgrade*                                                                                                                                         |
| **Maintenance window**  | Scheduled start and end time for the maintenance                                                                                                                                                                                |
| **Messages**            | Messages that are automatically published as the maintenance progresses                                                                                                                                                         |
| **Components impacted** | Components affected during the maintenance window                                                                                                                                                                               |
| **Notify subscribers**  | Toggle to send advance notification to subscribers. Email also requires the page-level [**Notify subscribers**](https://docs.datadoghq.com/incident_response/status_pages/subscriptions.md#enable-email-subscriptions) setting. |

{% image
   source="https://docs.dd-static.net/images/incident_response/status_pages/publish_status_page_maintenance.774ab646b9f05beaee7d2b43a123c34c.png?auto=format&fit=max&w=850 1x, https://docs.dd-static.net/images/incident_response/status_pages/publish_status_page_maintenance.774ab646b9f05beaee7d2b43a123c34c.png?auto=format&fit=max&w=850&dpr=2 2x"
   alt="Example publish notice modal for maintenance windows" /%}

After reviewing and scheduling, the maintenance window:

- Appears under **Upcoming Maintenance** on the status page
- Automatically updates component status to **Maintenance** when the window begins
- Returns components to **Operational** when the window ends (unless manually overridden)

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.

## Cancel a maintenance window{% #cancel-a-maintenance-window %}

To cancel a scheduled maintenance window before it starts, open the maintenance notice, click the three-dot icon, and select **Cancel Maintenance**. Confirm the cancellation in the dialog that appears.

{% image
   source="https://docs.dd-static.net/images/incident_response/status_pages/cancel-maintenance-window.a22d6178204e35754d4d8af8ea13cfa1.png?auto=format&fit=max&w=850 1x, https://docs.dd-static.net/images/incident_response/status_pages/cancel-maintenance-window.a22d6178204e35754d4d8af8ea13cfa1.png?auto=format&fit=max&w=850&dpr=2 2x"
   alt="Cancel Maintenance confirmation dialog for a scheduled maintenance window" /%}

Canceling a maintenance window removes it from **Upcoming Maintenance** on the status page. This action cannot be undone.

**Note**: An in-progress maintenance window can't be canceled.

## Backfill a maintenance window{% #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.

From a status page, select the dropdown next to **Publish Notice**, select **Publish Backfilled Notice** > **Scheduled Maintenance**, then provide:

| Field            | Description                                                                                                                                                                                                     |
| ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Notice title** | Clear description of the maintenance activity*Example: Database infrastructure upgrade*                                                                                                                         |
| **Updates**      | Exactly two timestamped updates representing the start and end of the maintenance window. Each update requires a started at timestamp, status (In Progress or Completed), description, and affected components. |

{% image
   source="https://docs.dd-static.net/images/incident_response/status_pages/publish_status_page_backfill_maintenance.f008b93eb4de6004d6709963c2b1a4a7.png?auto=format&fit=max&w=850 1x, https://docs.dd-static.net/images/incident_response/status_pages/publish_status_page_backfill_maintenance.f008b93eb4de6004d6709963c2b1a4a7.png?auto=format&fit=max&w=850&dpr=2 2x"
   alt="Example publish backfilled notice modal for maintenance windows" /%}

## Edit a maintenance update{% #edit-a-maintenance-update %}

After publishing a maintenance update, you can edit its message to correct typos or clarify the description. To edit a past update, open the maintenance notice on the status page, hover over the update you want to modify in the timeline, and click the edit icon that appears. Make your changes in the **Edit Update** modal.

{% image
   source="https://docs.dd-static.net/images/incident_response/status_pages/edit_maintenance_update.836f639785388af91d8c6433fad29959.png?auto=format&fit=max&w=850 1x, https://docs.dd-static.net/images/incident_response/status_pages/edit_maintenance_update.836f639785388af91d8c6433fad29959.png?auto=format&fit=max&w=850&dpr=2 2x"
   alt="Edit Update modal showing a Message field for a past maintenance update" /%}

Only the **Message** field can be edited. Click **Save Changes** to apply the edits.

## Further reading{% #further-reading %}

Additional helpful documentation, links, and articles:

- [Datadog Status Pages](https://docs.datadoghq.com/incident_response/status_pages.md)
