Status Pages Overview

Keeping your users informed during incidents is critical. Customers want to know that you are experiencing an incident and what steps you're taking to resolve it.


FireHydrant Status Pages are a great way to communicate with your customers, both internal and external, about ongoing incidents. And with FireHydrant Status Pages, you can update customers using the same tools and workflow that you already use to manage incidents.


FireHydrant offers two status page features:

  1. Incident-specific status pages
  2. System-wide status pages

Incident-specific status pages

Each incident automatically creates it's own status page where you can send notes and information about that specific incident. Incident-specific status pages are private in nature, as the URL string is long and therefore hard to guess. This makes it easy to share high-level incident information with internal stakeholders (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 meant to be an easy way to share information during the lifecycle of an incident.


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


System-wide status pages

System-wide status pages are public by default, but they can be put behind authentication and made private. This is an enterprise feature, get in touch with for more information.


To create a new system-wide status page, click on Organization in the left Navigation bar, Status Pages, and then New. Fill out the blanks on the next page and hit the Save button in the bottom right corner.



The CNAME will be generated automatically when the page is created, and you can point a subdomain at it (like You can find more information in our Status Pages Setup Guide.


Adding a status page to your incident is easy. On the incident page, go to External Resources and then "Published status pages." Pick your page off of the pulldown list.


You can also add status pages to incidents automatically using a runbook.

Once a status page is linked to an incident, you can publish to it in multiple ways. The first way is by updating an impact. You'll see a checkbox that allows you to publish to your status page.



The update will appear on your status page.


You can also publish timeline updates to your status page. Just change the visibility to Public Status Pages and leave the checkboxes checked for any status pages that you want to publish to.




You can also publish impact and timeline updates to your status pages using our Slack integration with "/firehydrant update" and "/firehydrant add note."


Status Pages can help you streamline your process of communicating with customers, so they stay informed about the progress of your incidents. Informed customers are happy customers.

Was this article helpful?
0 out of 0 found this helpful

Articles in this section