Overview

📘

Note:

This article is about FireHydrant's built-in status pages. For information about Atlassian Statuspages, visit Atlassian Statuspage documentation instead.

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

FireHydrant Status Pages enable you to communicate with internal and external customers about ongoing incidents. You can use Status Pages to update customers using the tools and workflow 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

Also called Internal status pages, each incident automatically creates a dedicated page with high-level information about the incident. This makes it easy to share high-level incident information with internal stakeholders or other team members with the page URL without requiring them to log in.

To read more about them, visit Internal Status Pages.

System-wide status pages

System-wide status pages are always available and show an overarching view of your system and which components are impacted by incidents.

To read more about system-wide status pages, visit External Status Pages.

Next Steps

• Configure a FireHydrant Status Page or an Atlassian Statuspage
• See how you can seamlessly post updates to incidents and to external status pages in one smooth motion