This product is not supported for your selected
Datadog site. (
).
Overview
Status Pages is part of Datadog’s Incident Response suite, alongside On-Call and Incident Management. It lets your team proactively communicate service availability, incidents, and planned maintenance with customers or internal stakeholders through a shareable web page.
Use Status Pages to:
- Share the availability of critical systems and features
- Communicate service disruptions clearly during incidents
- Announce scheduled maintenance and planned downtime in advance
- Reduce inbound support volume with proactive email and Slack notifications
To create, update, or publish Status Pages, you must have the appropriate RBAC permissions. For more information, see Access Control.
| Name | Description | Default Role |
|---|
Status Pages Settings Read
status_pages_settings_read | View the list of Status Pages, the settings of each Status Page, their Notices, and launched Internal Status Pages. | Datadog Read Only Role |
Status Pages Settings Write
status_pages_settings_write | Create new Status Pages, and configure Status Pages settings. | Datadog Admin Role |
Status Pages Notice Write
status_pages_incident_write | Publish and update Incidents. | Datadog Admin Role |
Status Pages Public Page Publish
status_pages_public_page_publish | Publish and unpublish public Status Pages. | None |
Status Pages Internal Page Publish
status_pages_internal_page_publish | Publish and unpublish internal Status Pages. | None |
Create a status page
- In Datadog, navigate to Status Pages.
- Click Create Status Page and follow the onboarding flow:
| Field | Description |
|---|
| Status Page Type | Choose who can access the page:
- Public - Anyone with the link can view
- Internal - Only authenticated users within your Datadog organization can view |
| Page name | Displayed as the page header (if no logo is uploaded).
Example: Acme Cloud Platform |
| Domain Prefix | Used as your status page subdomain prefix. For more information on custom domains, see the Set a custom domain section.
Example: shopist → shopist.statuspage.datadoghq.com
- Must be globally unique
- Lowercase, alphanumeric, and hyphenated
- May affect links if changed later |
| Subscriptions (optional) | Let users receive notifications about status page updates by email or Slack. When subscriptions are enabled, visitors can sign up from the published page to get notified about new notices and updates. Email and Slack subscriptions can be turned on or off independently for each status page. Note: Email subscriptions are double opt-in; the email address must be confirmed. |
| Company logo, Favicon, Email Header Image, or Slack App Icon (optional) | Upload images to personalize your status page and notifications. The Slack app icon appears as the sender avatar in Slack notifications, alongside your page name. |
- (Optional) Add components to show the status of individual services.
- Click Save Settings.
Add components
Components are the building blocks of your status page. Each one represents a service or feature your users care about. Some examples of components include:
- API Gateway
- Web Dashboard
- Database Cluster
- US Region Services
You can add components to your status page either on initial setup or through the status page settings:
- From your status page, click Settings and select the Components tab.
- Create individual components or a group of related components. You can associate notices with these components to reflect impact on your status page.
- Select a visualization type:
- Bars and Uptime Percentage
- Bars Only
- Component Name Only
Component hierarchy
If multiple notices affect the same component, the notice with the greatest impact takes precedence:
Major Outage > Partial Outage > Degraded Performance > Maintenance > Operational
Component status and uptime
Each component status affects the uptime bars and uptime percentage differently:
| Status | Uptime bars | Uptime percentage |
|---|
| Major Outage | Shown | Counts as downtime |
| Partial Outage | Shown | Counts as downtime |
| Degraded Performance | Shown | No impact |
| Maintenance | Shown | No impact |
| Operational | Shown as healthy | No impact |
Note: Partial Outage and Major Outage are weighted equally. The full duration at either status counts as downtime in the uptime percentage calculation.
Publish your status page
After you save your status page settings, click Launch Status Page to make the page available at its URL.
If you selected:
- Public, the page is immediately accessible to all visitors.
- Internal, access is limited to authenticated Datadog users in your organization.
Add a notice
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.
Publish a 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 |
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
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. |
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.
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
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.
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
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 |
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
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.
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
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. |
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.
Only the Message field can be edited. Click Save Changes to apply the edits.
Use notice templates
Templates let you save pre-configured language for degradation notices and maintenance windows that you publish repeatedly, such as a recurring maintenance activity or a known type of service disruption. When you publish a notice, select a template to pre-fill the notice title, per-status messages, and affected components instead of typing them each time.
Create a template
From your status page, click Settings and select the Templates tab.
In the Degradation Templates or Maintenance Templates section, click Add Template.
Provide the following details:
| Field | Description |
|---|
| Template name | Internal name used to identify the template when selecting it. Not shown on the published status page. |
| Notice Title | Default title pre-filled when the template is used. |
| Messages | A message for each notice status. Degradation templates support Investigating, Identified, Monitoring, and Resolved. Maintenance templates support Scheduled, In Progress, and Completed. |
| Components | Components to pre-select when the template is used. For degradation templates, you can also set an initial status for each component. |
Click Save.
Insert template variables
Insert a variable into a template message to have Datadog resolve it when the template is applied to a notice. Depending on the variable, Datadog either fills the value automatically or prompts the publisher to provide one. The Message Variables panel next to the message fields lists the available variables:
| Variable | Description |
|---|
{{date}} | Prompts the publisher to select a date and time when the template is applied. |
{{components_impacted}} | Automatically fills in the list of components selected on the notice. |
To insert a variable, type {{ in a message field and select a variable from the list, or click a variable in the Message Variables panel to insert it at the cursor.
Apply a template to a notice
From the Publish Notice modal, select a template from the Template dropdown to pre-fill the notice with its title, messages, and components.
Applying a template pre-fills the notice’s fields, which remain editable. To discard your edits and restore the original template content, click Reset Values.
Email subscriptions
Email subscriptions on status pages are double opt-in. After entering an email to subscribe, users receive a confirmation email and must click the confirmation link to activate their subscription. During this process, users can choose to receive notifications for the entire status page or select specific components they want to monitor. A preferred timezone can be configured for timestamp formatting within notifications. Users can manage their preferences and update their subscriptions at any time through the subscription management link included in notification emails.
For internal status pages, the subscription process is the same, but users must log in to the same Datadog organization to confirm their subscription and receive notifications.
Configure a custom email sender domain
By default, status page subscription emails are sent from a Datadog email address. To send notifications from your own domain, configure a custom SMTP server in Organization Settings.
The org_management permission is required to add SMTP servers in Organization Settings. The status_pages_settings_write permission is required to select the email sender domain on a status page.
- On your status page, go to Settings > Subscriptions.
- Under Email Sender Domain, click Organization Settings.
- In Organization Settings, add and validate an SMTP server.
- Return to Settings > Subscriptions and select your SMTP server as the email sender domain.
Slack subscriptions
Visitors can subscribe to status page updates in Slack through the Datadog Status Pages Slack app. When a notice or scheduled maintenance is published with Notify subscribers enabled, the app posts updates to each subscribed channel for the components it follows, using your page name and Slack app icon as the sender. Slack subscriptions are configured independently of email subscriptions.
Enable Slack subscriptions
- From your status page, click Settings.
- Enable Slack subscriptions.
- (Optional) Under Slack App Icon, upload an image to use as the sender avatar on Slack notifications.
Click Subscribe on the published page to open a modal with a tab for each enabled subscription type.
Subscribe in Slack
From a published page with Slack subscriptions enabled:
- Click Subscribe and open the Slack tab.
- (Optional) Select Subscribe to specific services to choose individual components, or leave it cleared to follow the entire page.
- Click Subscribe via Slack.
- Authorize the Datadog Status Pages app for your workspace and select the channel to receive updates.
After subscribing, the selected channel receives a welcome message confirming the subscription.
Private channels: After subscribing, the user receives a message in the Messages tab of the Slack app prompting them to invite the Datadog Status Pages bot to the channel. The bot must be invited before it can post updates. Direct message (DM) channels are not supported. On internal status pages, users must be logged in to the same Datadog organization to subscribe.
Manage subscriptions
Subscribers can change the components they follow or unsubscribe at any time from the Manage Preferences link in any Slack notification.
Status page owners can review subscribers in the status page settings, which lists the subscribed Slack workspaces and channels. Removing a workspace unsubscribes all of its channels from the page.
If the selected SMTP server fails, notifications are sent to subscribers through Datadog Default (no-reply@dtdg.co).
Set a custom domain
To match your branding, you have the option to map your status page URL to a custom domain like status.acme.com. This is separate from configuring a custom email sender domain, which controls the from address on subscription emails.
- From your status page, click Settings.
- Select Custom Domain.
- Follow the instructions to enter your domain and add DNS records.
- Datadog automatically detects the DNS configuration and provisions an SSL certificate.
Custom domains require access to your DNS provider to add a CNAME or A record.
Note:
- DNS propagation may take several minutes.
- You can revert to the default Datadog domain at any time.
- DNS changes must be made by someone with access to your domain registrar.
Manage status pages with Terraform
You can use Terraform to create or manage your status pages. For details on the resources available, see Datadog’s Terraform registry.
Further reading
Additional helpful documentation, links, and articles:
