Statuspage

Last updated: Nov 3, 2026

---

Rationale

Statuspage is the primary tool that Fluid Attacks uses to tell users about the health of its products and about incidents. With it, Fluid Attacks can quickly, clearly, and transparently give information about outages, performance degradations, or other problems in its components or external dependencies.

Fluid Attacks chose Statuspage over other alternatives for these reasons:

• It gives a simple hub where the team can quickly write incidents with all the necessary information.
• It is fully customizable for all needs.
• It can show the real-time dependency status.
• It has many easy integration options with other Atlassian products that Fluid Attacks uses, and with external tools.
• Its API has many options to run automations and get data easily.

Alternatives

Fluid Attacks evaluated this alternative and rejected it for these reasons:

BetterStack: It was the primary status page of Fluid Attacks for some time. But it did not satisfy the strict security requirements of Fluid Attacks.

Usage

Fluid Attacks uses Statuspage for these tasks:

• Tell internal and external users about the status of its products on status.fluidattacks.com.
• Create, manage, and show incidents.
• Give updates on the status of incidents.
• Create and show the postmortem of incidents.
• Show the uptime timeline of components.
• Show the status of third-party dependencies.
• Send notifications by email, SMS, webhook, Slack, and RSS to the subscribers of its status page.
• Keep a historical register of its incidents and their details.

Fluid Attacks does not use Statuspage to schedule maintenance events.