Statuspage

Rationale

Statuspage  is our main communication tool with users regarding our product’s health and incidents. This helps us inform quickly, clearly, and transparently about outages, performance degradations, or any other eventuality in our components or external dependencies.

The main reasons why we chose it over other alternatives are:

• It provides a simple hub where incidents can be written quickly, providing all the necessary information.
• It is fully customizable for every need.
• It provides the possibility to display real-time dependency status .
• It brings easy multiple integration options  with other Atlassian  products we use and also with external tools.
• Its API provides quite a few options to run automations and get data easily.

Alternatives

The following alternative was considered but not chosen for the following reasons:

BetterStack : It was our main status page for some time, but it finally did not meet our strict security requirements.

Usage

We use Statuspage  for

• informing internal and external users about our products’ status on status.fluidattacks.com ;
• creating, managing, and displaying incidents;
• giving updates  on incident status;
• creating and displaying the incidents’ postmortem ;
• displaying components’ uptime timeline ;
• displaying third-party dependencies’ status ;
• sending notifications via email, SMS, webhook, Slack, and RSS to our status page subscribers;
• providing a historical register  of our incidents and their respective details.

We do not use Statuspage  for scheduling maintenance  events.