--- title: Status Pages description: >- Communicate service availability, incidents, and planned maintenance with customers or internal stakeholders through a shareable status page. breadcrumbs: Docs > Incident Response > Status Pages --- > For the complete documentation index, see [llms.txt](https://docs.datadoghq.com/llms.txt). # Status Pages {% 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 %} ## Overview{% #overview %} {% image source="https://docs.dd-static.net/images/incident_response/status_pages/shopist_status_page3.baf3df91655cb183f1dc234b0b7b9023.png?auto=format&fit=max&w=850 1x, https://docs.dd-static.net/images/incident_response/status_pages/shopist_status_page3.baf3df91655cb183f1dc234b0b7b9023.png?auto=format&fit=max&w=850&dpr=2 2x" alt="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**, **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, Slack, Microsoft Teams, and RSS feed notifications Use the following pages to set up and run your status pages: - [Components](https://docs.datadoghq.com/incident_response/status_pages/components.md): Represent the services and features your users rely on. - [Notices](https://docs.datadoghq.com/incident_response/status_pages/notices.md): Publish degradations and schedule maintenance windows. - [Notice Templates](https://docs.datadoghq.com/incident_response/status_pages/templates.md): Reuse notice titles, messages, and components. - [Subscriptions](https://docs.datadoghq.com/incident_response/status_pages/subscriptions.md): Notify subscribers by email, Slack, or Microsoft Teams, or publish an RSS or Atom feed. ## Configure permissions{% #configure-permissions %} To create, update, or publish Status Pages, you must have the appropriate RBAC permissions. For more information, see [Access Control](https://docs.datadoghq.com/account_management/rbac.md). | Name | Description | Default Role | | -------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------- | ---------------------- | | Status Pages Settings Readstatus_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 Writestatus_pages_settings_write | Create new Status Pages, and configure Status Pages settings. | Datadog Admin Role | | Status Pages Notice Writestatus_pages_incident_write | Publish and update Incidents. | Datadog Admin Role | | Status Pages Public Page Publishstatus_pages_public_page_publish | Publish and unpublish public Status Pages. | None | | Status Pages Internal Page Publishstatus_pages_internal_page_publish | Publish and unpublish internal Status Pages. | Datadog Admin Role | ### Granular access control{% #granular-access-control %} By default, access to a status page is unrestricted within your organization. Use [granular access controls](https://docs.datadoghq.com/account_management/rbac/granular_access.md) to restrict an individual status page by team, role, user, or service account. | Access level | Capabilities | | ------------- | ------------------------------------------------------------------------------ | | **Viewer** | View the status page. | | **Responder** | View the status page and publish or update notices. | | **Manager** | View and respond to the status page, edit its settings, and manage its access. | Granular access control only restricts access and does not grant RBAC permissions. Users must also have the corresponding Status Pages permissions described above. Configuring granular access requires the **Status Pages Settings Write** permission. If the status page is already restricted, you must also have **Manager** access to it. To restrict access: 1. Navigate to [Status Pages](https://app.datadoghq.com/status-pages) and select a status page. 1. Click **Settings**, then select **Access**. 1. Click **Edit Access**, then click **Restrict Access**. 1. Add teams, roles, users, or service accounts and assign each an access level. 1. Click **Save**. **Note**: Access restrictions apply to users in your Datadog organization. They do not change who can view a published public status page. ## Create a status page{% #create-a-status-page %} 1. In Datadog, navigate to [**Status Pages**](https://app.datadoghq.com/status-pages). 1. 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](https://docs.datadoghq.com/incident_response/status_pages/subscriptions.md#email-subscriptions), [Slack](https://docs.datadoghq.com/incident_response/status_pages/subscriptions.md#slack-subscriptions), [Microsoft Teams](https://docs.datadoghq.com/incident_response/status_pages/subscriptions.md#microsoft-teams-subscriptions), or an [RSS or Atom feed](https://docs.datadoghq.com/incident_response/status_pages/subscriptions.md#rss-and-atom-feeds). For email, you can let visitors subscribe from the published page or [add subscribers](https://docs.datadoghq.com/incident_response/status_pages/subscriptions.md#add-or-import-subscribers) yourself. Email, Slack, and Microsoft Teams subscriptions can be turned on or off independently for each status page. **Note**: [Email subscriptions](https://docs.datadoghq.com/incident_response/status_pages/subscriptions.md#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. | 1. (Optional) [Add components](https://docs.datadoghq.com/incident_response/status_pages/components.md) to show the status of individual services. 1. Click **Save Settings**.Important alert (level: info): A status page **is not Live** after you save your settings. To make the page available, publish your status page. ## Publish your status page{% #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. ## Set a custom domain{% #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](https://docs.datadoghq.com/incident_response/status_pages/subscriptions.md#configure-a-custom-email-sender-domain), which controls the from address on subscription emails. 1. From your status page, click **Settings**, then select **Custom Domain** under **General**. 1. Follow the instructions to enter your domain and add DNS records. 1. Datadog automatically detects the DNS configuration and provisions an SSL certificate. {% alert level="warning" %} Custom domains require access to your DNS provider to add a CNAME or A record. {% /alert %} **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{% #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](https://registry.terraform.io/providers/DataDog/datadog/latest/docs/resources/status_page). ## Further reading{% #further-reading %} Additional helpful documentation, links, and articles: - [Keep stakeholders informed with Datadog Status Pages](https://www.datadoghq.com/blog/status-pages) - [Learn more about Incident Management](https://docs.datadoghq.com/incident_response/incident_management.md) - [Learn more about On-Call Scheduling](https://docs.datadoghq.com/incident_response/on-call.md) - [Integrate Datadog Status Pages with Incident Management](https://docs.datadoghq.com/incident_response/incident_management/integrations/status_pages.md)