Skip to main content
Plan requirement: All plans can create public status pages (Free and Standard: up to 1, Pro: up to 5). Internal status pages are available on the Pro plan only (up to 20). Learn more
You cannot create a new status page in these cases (existing status pages keep working, and you can still edit them and publish events):
  • The subscription is expired or disabled: you can create again after renewing.
  • Internal status pages: require Pro or higher.
See What happens when your subscription expires.
Service interruptions happen; how well you communicate about them is something you can improve. When service status fluctuates, relying on manual emails or instant messages for notifications can no longer meet enterprise requirements for information timeliness and consistency. Flashduty Status Page provides a standardized, unified information publishing window to ensure that both internal and external stakeholders maintain real-time awareness of service status.
Subscribe to the Flashduty Official Status Page to receive Flashduty service status updates first.

​
Core value

Reduce Communication Costs

Through the “update once, sync everywhere” mechanism combined with subscription push mode, reduce repetitive inquiries at the source and let technical teams focus on problem resolution.

Build Long-term Trust

Proactively announce unexpected incidents and maintenance plans to eliminate speculation caused by information asymmetry, demonstrating professionalism and control amid uncertainty.

Stability as an Asset

Continuously record status changes and generate visual availability statistics, transforming abstract SLA commitments into verifiable operational records.

​
Status page types

To address different audience needs, Flashduty offers two types of status pages:
For customers and partners
  • Open to all public internet users, accessible without sign in
  • Help enterprises provide real-time, accurate service status updates to customers during incidents
  • Proactively deliver critical information, ease customer anxiety, and build a professional brand image
  • Users can subscribe to event updates through email

​
Core concepts

​
Components and groups

Status pages organize and present different services through Components. A component is one functional unit of your system; each event states which components it affects, so the scope of impact is clear. Related components can be Grouped.

​
Event types

​
Impact status

In order of increasing severity:
  • 🟢 Operational
  • 🟡 Degraded Performance
  • 🟠 Partial Outage
  • 🔴 Full Outage

​
FAQ

Both a status page (such as Flashduty Status Page) and an uptime monitor (such as Uptime Kuma) provide dashboards that display service availability.The key differences are as follows:If you only need a simple self-monitoring tool for service availability checks (such as domain or port probing), use an uptime monitoring tool instead.
If you need a formal service status dashboard and notification system for external customers or internal organizations, Flashduty Status Page is the better choice.
Access Control
  • Public status pages are accessible to anyone on the public internet and do not require login.
  • Internal status pages are restricted to organization members and require authentication with a Flashduty account.
Management Permissions Status page management follows Flashduty’s RBAC permission model. Administrators can assign the following roles:
  • Status Page Management: Create, edit, and delete status pages; manage subscriptions.
  • Status Page Event Management: Publish, edit, and delete events on status pages.
Currently, you publish events manually in the Flashduty status page management interface. To simplify this process, Flashduty provides event templates that allow teams to quickly publish incident or maintenance updates with minimal effort.In the near future, Flashduty will introduce workflow support within the On-call incident management module. This will allow predefined rules to automatically publish relevant incidents to associated status pages, enabling seamless integration between Oncall incidents and status page updates.
Users can actively subscribe to service status updates. When publishing an event, administrators can choose whether to notify subscribers, allowing flexible control over notifications.
  • For public status pages, subscribers receive updates by email. StatusPageEmailNotification.png
  • For internal status pages, users can bind their preferred IM integrations in Flashduty notification settings to receive direct messages. Supported: Feishu, DingTalk, WeCom, and Slack. Public status pages support email subscriptions only, not IM. StatusPageIMNotification.png
No. Users can choose their subscription scope. They may subscribe to all updates on a status page or only to specific services or events.Component-based and event-based subscriptions ensure that users receive only relevant information, reducing unnecessary notification noise.
For a component, Partial Outage and Full Outage durations count as downtime. Although maintenance may impact service behavior, Flashduty excludes maintenance time from service uptime calculations.Flashduty calculates component availability over a rolling quarterly window, as the ratio of uptime to total available time.Group availability also uses a quarterly window. It’s the sum of uptime across all components in the group divided by the sum of their total available time.Flashduty calculates each component’s impact periods by replaying status changes from event timelines. Maintenance events follow a separate rule. A component shows Under Maintenance only while the maintenance actually runs, from Ongoing until closure. A scheduled maintenance that hasn’t started doesn’t affect availability charts or the calendar. Uptime calculations exclude components and sections set to “Hide all”. They include those set to “Hide uptime” but don’t show their statistics publicly. You can choose the uptime display mode in status page settings: chart and percentage, chart only, or none.
In some cases, teams must prioritize investigation and recovery and are unable to update the Flashduty status page in real time. During system migrations, existing availability records may also need to be preserved.Flashduty supports retrospective events, which allow teams to publish service status changes after they have occurred.With retrospective events, users can declare a past incident or maintenance event, accurately setting start time, end time, and affected components. Event updates can still be constructed chronologically to clearly reflect service behavior throughout the event lifecycle.The status page shows retrospective events like regular events and includes them in event history and availability statistics, ensuring a complete and accurate operational record.
Flashduty Status Pages support dark mode. You can upload both a standard logo and a dark logo. The system automatically switches to the appropriate logo based on the user’s browser theme. If only the standard logo is uploaded, it will also be used in dark mode.
Yes. You can configure a custom domain for your status page (for example, status.yourcompany.com). Add a CNAME record in your DNS provider pointing to the Flashduty-provided status page address, then enter the custom domain in the status page settings. Custom domains must be globally unique across the platform and cannot be shared by multiple status pages.
After you configure a custom domain, Flashduty automatically issues, renews, and publishes HTTPS certificates for it. Two DNS verification records are required before issuance. After configuring them, click Check configuration in the status page settings to view the verification status:
  • Access entry record (CNAME): points your domain to a managed access entry — cn.statuspage.flashduty.com for the mainland China entry, or statuspage.flashduty.com for the international entry.
  • Certificate management record (dns-01 delegation): a CNAME record under the _acme-challenge prefix that delegates certificate validation to Flashcat-managed DNS. The exact record value is shown by Check configuration.
Once both records pass verification, the system issues and publishes the certificate, and the domain serves HTTPS.If your domain still points to the legacy entry statuspage.flashcat.cloud, Flashduty issues the certificate in advance once the certificate management record passes verification. Switching DNS to a managed access entry later doesn’t interrupt HTTPS.
The Flashduty Status Page comes with the On-call module and isn’t sold separately. Status page limits by plan are as follows:
  • Free and Standard plans: 1 public status page
  • Professional and Private plans: up to 5 public status pages and up to 20 internal status pages
We recommend organizing internal status pages by business line or major platform. If you have special requirements, contact Flashduty support for consultation.Usage limits and access considerations:
  • Email notifications for public status pages are subject to plan-specific email quotas.
  • IM notifications for internal status pages are subject to API rate limits of the integrated IM platforms and typically depend on the organization’s IM plan.
  • Access traffic for all status pages is unlimited.