Skip to main content

​
What’s a Status Page?

Status pages let you share the health of your systems with the people who depend on them, from internal teams to customers and partners. Rootly’s Status Pages keep your stakeholders up-to-date on the systems most relevant to them, without taking your responders’ focus off of the incident. Image 13 It only takes about 10 minutes to set up a status page: get started by signing up.

​
How a Status Page Works

A status page is built from a few pieces.
  • Components: The parts of your product that customers see on the page. Add services from your catalog, or create custom items for anything that isn’t a catalog service, like “Login” or “Checkout”. See Components.
  • Groups: Organize components into groups, up to two levels deep. A group shows the status of its most affected component, so one degraded region shows as one degraded region, not a page full of red. See Grouping and Ordering.
  • Updates: What you post to the page. There are three types:
    • Incident: an unplanned issue.
    • Scheduled maintenance: planned work with a start and end time.
    • Announcement: a standalone notice, shown as a banner at the top of the page.
Clean Shot 2026 09 23 At 10 46 48@2x You can post incidents and announcements to one page or many at once. See Publishing Updates.

​
Internal, Public, or Customer?

This is the first choice you make, and it shapes everything after it. The page type sets who can reach the page at all. Authentication and a custom domain are options you layer on top of a public or customer page afterwards. Rootly has three types of status pages: internal, public, and customer. All three can share information about ongoing or past incidents and the status of your services. The Create a new status page dialog, showing the Internal, Public, and Customer page types Every organization includes 2 free published status pages, in any mix of types. You can add more pages from the Status Pages section in Rootly. See Free Status Pages.
Internal status pages are for your team only. They’re automatically private to your Rootly organization and never visible to outside users. They’re great for sharing important incidents and service health with your own teams, with custom internal statuses and severities and SSO-protected access for employees.
Public status pages can be accessed by anyone with the page’s URL, with no login needed. They show uptime history and the incident timeline, and they’re the right choice for sharing incident updates and service health with customers and partners at large.
Customer status pages are for specific accounts or segments. Viewers must authenticate to see them, and you manage access by invitation. They’re the right choice when you want to share service health with some customers and not the world. See Customer Pages.

Creating a Status Page

Set up a status page after picking a type.

Publishing Incidents

Push incident updates to a status page from Web or Slack.

Custom Domain Names

Point your own domain at a status page with CNAME + CAA records.

Customer Pages

Share service health with specific customers, behind a login.