What is Statuspage?

Statuspage is a communication tool that helps you inform your users about outages and scheduled maintenance. Your users can subscribe to updates via email or text messages when you have an incident, and you can embed your system status directly into other interfaces and web properties so your customers always know what’s going on.

Watch this video for an overview of how Statuspage works.

Statuspage does not do any direct monitoring of your websites or servers, but you can integrate monitoring tools with Statuspage, or use our API to programmatically update your page.

Why use Statuspage?

  • Build trust with your customers

  • Reduce incoming support requests during incidents

  • Build and scale your incident communication process

Below is a snapshot of what a typical Statuspage setup looks like:

screenshot of a typical status page

The basics


When you signup for Statuspage, you create a page that is part of your account. Multiple pages can be managed from a single account, and all team members in an account can access every page in the account. Pages are autonomous and they have separate billing subscriptions.

A page can be public or private. A public page is viewable by anyone with an internet connection. A private page is viewable by only those who have access to login and view the page.


Account owners: Each account has only 1 account owner. Account owners can invite team members to help them manage the account’s page(s). Only account owners can delete other team members.

Team members: An account can have multiple team members. Each team member has access to all of the pages under the account and has access to manage and configure the entire page. Team members have all of the same permissions as account owners except one thing: team members cannot delete other team members.

Subscribers: Subscribers are typically your customers, end-users, or employees. They are the people who subscribe to receive notifications from your page when you publish incidents.

Employees: Private pages have users who are permitted access to the private status page by logging in. We call these “employees” because most private page customers are using Statuspage to communicate internally with their employees. An employee is not automatically subscribed to receive updates.


Incidents are a core part of Statuspage. They are critical events that have occurred with your product or service that you want to communicate with your users. Incidents have 4 different statuses. You can move incidents to these statuses throughout the life of the incident and you can send notifications for each incident update to your subscribers.

Incident statuses:

  • Investigating

  • Identified

  • Monitoring

  • Resolved

After your Statuspage has been operational for 14 days, the Incident History link will appear to allow page viewers to review historical incidents.


Components are the individual parts of your infrastructure that your users depend on; the functioning pieces or features of your application or service. Components have their own statuses, and they can be updated during the incident creation process or independently without an incident.

Component statuses:

  • Operational

  • Partial Outage

  • Degraded Performance

  • Major Outage

  • Under Maintenance

System metrics

System metrics allow you to increase transparency with your customers by showing them real-time and historical data such as response time and uptime. You can push in data from a variety of supported metrics integrations, or use our API.

Examples of metrics:

  • Uptime

  • Response time


Email and text message notifications can be sent to your subscribers when you create and update incidents. Your subscribers can opt-in to notifications from your page, and you can manage your subscribers any time.


Additional Help