Skip to main content
Changelog
  • Status Page Upgrade: Dual-Region Custom Domains and One-Click Atlassian Statuspage Migration

    Switching away from Atlassian Statuspage is rarely about standing up a new page. The hard part is carrying over history and subscriber relationships intact, otherwise every subscriber's email link and RSS feed breaks.

    Flashduty Status Page shipped late last year. This update covers two things: a real migration path from Atlassian Statuspage, and a custom domain setup rebuilt to hold production traffic.

    One-click Atlassian Statuspage migration

    Migration runs in two CLI steps. flashduty statuspage migrate structure imports components, groups, history events, and notification templates without notifying subscribers, so you can check the result before going further. Once it looks right, flashduty statuspage migrate email-subscribers imports the mailing list. History event feeds keep Atlassian's history.rss and history.atom URL format, so subscribers never have to update their feed URLs. Both commands are paginated and idempotent, so re-running them does not duplicate data.

    Custom domains 2.0

    Custom domains used to resolve through a single CNAME target. They now resolve through separate mainland China and international routes. Certificates are issued and renewed automatically by Caddy, with an idempotency fix that prevents duplicate certificate requests under concurrent traffic. Existing customers on the old single-CNAME setup keep working without any DNS changes.

    RSS/Atom feeds and one-click unsubscribe

    Public status pages now support RSS/Atom subscriptions, no email confirmation required. The history route also accepts an Atlassian-compatible alias, so subscribers migrating over keep their old feed URLs. On the email side, notification emails now carry the RFC 8058 List-Unsubscribe header, so Gmail, Apple Mail, Outlook, and Yahoo show a native unsubscribe button at the top of the message that takes effect immediately.

    Fix

    Components hidden on an internal status page no longer leak into the public change history.

    Getting started

    Go to Flashduty console → Status Pages → Settings to configure a custom domain. Migration steps and CLI commands are in Get started with Flashduty Status Page; feature comparison is in Status Page Comparison.