Status Pages

This product is not supported for your selected Datadog site. ().
Cette page n'est pas encore disponible en français, sa traduction est en cours.
Si vous avez des questions ou des retours sur notre projet de traduction actuel, n'hésitez pas à nous contacter.

Overview

Example status page showing service components with their current status and recent incident updates

Status Pages is part of Datadog’s Incident Response suite, alongside On-Call and Incident Management. It lets your team proactively communicate service availability and incidents 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
  • Reduce inbound support volume with proactive email notifications

Configure permissions

There are three RBAC permissions that are relevant to Status Pages. Users with the Datadog Admin Role have all the necessary permissions.

To create, update, or publish Status Pages, you must have status_pages_settings_read, status_pages_settings_write, and status_pages_incident_write RBAC permissions. For more information, see Access Control.

NameDescriptionDefault Role
Status Pages Settings Read
status_pages_settings_read
View the list of Status Pages, the settings of each Status Pages, their Incidents, and launched Internal Status Pages.Datadog Read Only Role
Status Pages Settings Write
status_pages_settings_write
Create and launch 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

Create a status page

  1. In Datadog, navigate to Service Management > Status Pages.
  2. Click Create Status Page and follow the onboarding flow:
    FieldDescription
    Status Page TypeChoose who can access the page:
    - Public - Anyone with the link can view
    - Internal - Only authenticated users within your Datadog organization can view
    Page nameDisplayed as the page header (if no logo is uploaded).
    Example: Acme Cloud Platform
    Domain PrefixUsed as your status page subdomain prefix.
    Example: shopist → shopist.statuspage.datadoghq.com
    - Must be globally unique
    - Lowercase, alphanumeric, and hyphenated
    - May affect links if changed later
    Subscriptions (optional)Enable users to receive email notifications about status page updates. When subscriptions are enabled, users can sign up to get notified about new notices and updates. You can turn subscriptions on or off for each status page. Note: Email subscriptions are double opt-in, email must be confirmed.
    Company logo, Favicon, or Email Header Image (optional)Upload a logo, favicon, or image to personalize the appearance of your status page and email notifications.
  3. (Optional) Add components to show the status of individual services.
  4. Click Save Settings.
    A status page is not Live after you save your settings. To make the page available, publish your status page.

Add components

Status page component configuration with live preview panel

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 intial setup or through the status page settings:

  1. From your status page, click Settings and select the Components tab.
  2. Create individual components or a group of related components. You can associate notices with these components to reflect impact on your status page.
  3. Select a visualization type:
    1. Bars and Uptime Percentage
    2. Bars Only
    3. Component Name Only

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 on Status Pages are carefully crafted messages posted to a public website to communicate system status. When an issue arises, you can communicate it clearly through your status page.

  1. From a status page, click Publish Notice to open a “Publish Status Page Notice” modal and provide:
    FieldDescription
    TitleShort, clear description of the incident
    Example: Increased error rates on US region
    StatusCurrent state of the incident:
    - Investigating
    - Identified
    - Monitoring
    - Resolved
    Message (optional)Additional details for your users
    Examples: known cause, expected resolution time
    Components impactedOne or more components impacted by the incident
    ImpactLevel of impact per component:
    - Operational
    - Degraded Performance
    - Partial Outage
    - Major Outage
    Notify SubscribersToggle to send the notice to subscribers
  2. Click Publish Notice.
Screenshot of the Status Page Notice creation modal with fields filled out

After a notice is published, the notice:

  • Appears on the Status Pages List under Active Notices.
  • Updates the uptime bars for impacted components.
  • Is visible in the notice history timeline.

You can post updates over time to keep users informed, and then mark the notice as Resolved.

Email subscriptions

Email subscriptions on status pages are double opt-in: users must confirm their email address before they are added as subscribers. After entering an email to subscribe, a confirmation email is sent, and the subscription is only activated after the user clicks the confirmation link.

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.

Further reading