Source
Incident response, status pages & post-incident review — found from sitemap — Rootly
Checked for Rootly on 6 Nov 2026
- Page
- https://docs.rootly.com/configuration/status-pages
- Checked
- 6 Nov 2026, 04:47 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:1fe4b42b1b22442d30f5855f5ca06863671dca39e1b55902dfd0f604e471a603
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Status pages overview Report an error
“Create and manage status pages to communicate service health and incident information to internal stakeholders and external customers in real-time.”
-
Status page setup time Report an error
“It only takes about 10 minutes to set up a status page: get started by signing up.”
-
Status page components Report an error
“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”.”
-
Status page groups Report an error
“Groups: Organize components into groups, up to two levels deep. A group shows the status of its most affected component”
-
Status page multi posting Report an error
“You can post incidents and announcements to one page or many at once.”
-
Status page types Report an error
“Rootly has two types of status pages: public and private. Both can share information about ongoing or past incidents and the status of your services.”
-
Status page default pages Report an error
“By default, you’ll have one public and one private status page to customize. You can add more pages from the Status Pages section in Rootly.”
-
Private status pages access Report an error
“Private status pages can only be accessed by Rootly users. They’re great for sharing important incidents and service health with your internal teams. Users must be logged in to Rootly to access the page.”
-
Public status pages access Report an error
“Public status pages can be accessed by anyone with the page’s URL.”
-
Status page authentication option Report an error
“Authentication and a custom domain are options you layer on top of a public page afterwards.”
-
Status page custom domain Report an error
“Point your own domain at a status page with CNAME + CAA records.”
-
Status page incident publishing Report an error
“Push incident updates to a status page from Web or Slack.”
-
Statuspage import Report an error
“Importing from Atlassian Statuspage”
-
Status page API reference Report an error
“Status Page API”
2 facts read from this page are not shown because they could not be confirmed on the page as captured.
Scores citing this record
- The Engineering Manager Incident response, status pages & post-incident review
- The ICT Risk Officer Incident response, status pages & post-incident review
- The IT Operations Manager Incident response, status pages & post-incident review
- The MSP NOC Lead Incident response, status pages & post-incident review
- The MSP NOC Lead Integrations, API & administration
- The Skeptic Incident response, status pages & post-incident review
- The SRE Lead Incident response, status pages & post-incident review