Changelog

Keep every stakeholder informed without leaving the incident.

Use Rootly Status Pages to update customers, executives, and internal teams in real time, right from the incident.

Keep every stakeholder informed without leaving the incident.

Rootly Status Pages make it easy for you to keep every single stakeholder up to date on your incident response, without distracting teams from their mitigation and resolution work. Status Pages can be updated directly inside an incident channel, so your customers, executives, and internal teams know what’s happening without any missing context.

Rootly suggests the affected components and writes a summary based on context from the incident; you review and decide what gets published.

Publish from where you’re already working

When you create, mitigate, or resolve an incident, Rootly is able to prompt you to publish a status page update, on the web and in Slack. The update opens with the incident’s services and functionalities already picked as affected components, so you review, adjust, and publish in a few clicks. You can also ask the Rootly agent to draft and post the update for you.

Communication keeps pace with the incident, and the person leading the response doesn’t have to stop and switch tools to do it.

Show exactly what’s affected

Group components up to two levels deep and give each component its own status. If one region slows down, your page shows one degraded region, not a wall of red.

Every status update lets you choose which components are affected and how. As the incident evolves, each new update reflects the current state of your system: add components as impact spreads, change their status as things recover, and remove them once they’re back to normal. Subscribers who follow a removed component are told it’s no longer affected.

Speak to each audience

Run internal pages for your team and public pages for customers, each with its own content and access. For the same incident, you can post a different update to each page, so you control the message and level of detail every audience sees. Your engineers get the technical specifics on the internal page, while customers get a clear, plain-language update on the public one.

Control who can publish

Each status page has its own permissions for each team. With Team Access, you choose which teams can draft and post an update to a status page. Your external status page can be owned entirely by your comms team, while your internal page stays the responsibility of your response team.

What’s included

  • Draft and post updates to a status page through Rootly Web and the incident Slack channel.
  • Include the affected components in each update, with uptime statuses per component to communicate the accurate real-time status of your product.
  • Never miss important context in an update by using the Rootly agent to draft the update for you.
  • Post announcements and planned maintenance windows to your status page.
  • Team Access with Edit & Publish or Publish-only permissions per page.
  • A setup wizard that saves your progress.
  • A refreshed status page design.

Why it matters

During an incident, the people fixing the problem are often the same people expected to keep everyone informed. With a separate status page tool, every update means switching tabs, retyping what’s already in the incident, and hoping the components match. Rootly keeps the status page in the same place as the response, so updates go out faster, stay accurate, and don’t pull attention from the fix.

Get started in the Status Pages docs. Moving from Atlassian Statuspage? Reach out to your CSM or support@rootly.com and our team will run the migration with you, including subscribers and incident history.

What else shipped

Improvements

On-Call

  • The Page command in Teams now lets you pick any Rootly organization connected to your Microsoft tenant, just like Slack.
  • The Create Alert dialog in Teams now fills in your default alert message, matching Slack and the web.
  • Incidents created from a Teams alert now show Teams as their source on the web timeline.
API & CLI

On-Call

  • Alert source allowlist denials now return a 403 error instead of a 404.

Incident Response

  • The API now rejects more than one option on a single-select custom field.
Terraform
  • Alert workflows in Terraform can now use custom alert field conditions, matching what the UI supports.
Fixes

Incident Response

  • Setting up a custom domain that another team’s status page already uses now shows a clear message instead of failing silently.
  • Status page component descriptions now save consistently and follow the 400-character limit on every component type.
  • The OAuth Applications settings page can now create apps with profile and email scopes and choose public or confidential clients.
  • Team member lists now show full names where they should, instead of preferred names.
Mobile

Improvements

  • You can now add Microsoft Teams as a channel in your on-call notification rules in the mobile app.
  • Alerts and escalations attached to an incident now link to the incident’s Teams channel in the mobile app.

Fixes

  • Android now turns Do Not Disturb back on, and keeps Silent mode silent, after a critical page ends.
  • iOS now plays the critical alert sound instead of the default system ping when no custom sound is set.
  • Adding the Rootly contact card is faster and retries when the server is slow.

Your privacy choices

Rootly uses cookies from advertising partners to measure our ads and to show ads for Rootly on other sites. Some US state laws call that selling or sharing personal information. You can opt out of it for this browser here.

Analytics we use to improve this site stay on. Read Rootly's Privacy policy for more information.