FireHydrant Status Pages Overview

Note: This article is about FireHydrant's built-in status pages system-wide and per-incident. For information about Atlassian Statuspages, visit this page instead.

Keeping users informed during incidents is critical. When you experience an incident, customers want to know what steps you're taking to resolve it.

FireHydrant Status Pages enable you to communicate with customers, both internal and external, about ongoing incidents. You can use Status Pages to update customers using the same tools and workflow that you already use to manage incidents.

FireHydrant offers two status page types:

  1. Incident-specific (e.g. "internal") status pages
  2. System-wide (e.g. "external") status pages

Incident-specific status pages

Each incident automatically creates its own status page where you can send notes and information about that incident. Incident-specific status pages are mostly private in nature, but they can be accessed by anyone with the page URL (however, the URL string is long and therefore difficult to guess). This makes it easy to share high-level incident information with internal stakeholders or any other team members who have the page URL (without requiring them to log in).

Incident-specific status pages "expire" after 48 hours of an incident being resolved, meaning the link will no longer be accessible. Incident-specific status pages are designed to be an easy way to share information during the lifecycle of an incident.

System-wide status pages

System-wide status pages are available all of the time.

System-wide status pages are public by default, but they can be put behind authentication and made "authentication-only." To set up authenticated status pages, contact

To create a new system-wide status page:

In the left nav, click Status pages, then +Create status page. Provide information in the fields provided and click Save.create_status_page.png

The CNAME is generated automatically when the page is created. 

Adding a status page to an incident

To add a status page to an incident:

On the main page for the incident, scroll down to the External Resources section. From the dropdown on the right, select the status page you want to publish. 

Updating status pages

After a status page is linked to an incident, you can use multiple methods to update the page.

  1. You can publish an update to the status page when updating the incident impact. When you update an impact for a specific incident, you can select a checkbox that also causes your update to post to the status page.
  2. You can also publish impact updates to your status pages using the Slack commands /firehydrant update and /firehydrant add note.
Was this article helpful?
1 out of 1 found this helpful

Articles in this section

Contact Our Support Team
Got a Question or Suggestion? We're here to help!
Follow us on Twitter
Get the latest news and updates first