This release makes it easier to publish updates during incidents, manage access and routing settings, and present a clearer experience for customers viewing status pages and subscription emails.
🚨 Incident response
You can now publish customer-facing status updates from your incident workflows, with support for both the Incident Management view and the Slack declare-incident flow. The Slack modal now also helps responders fill in the right service, severity, and publishing details more quickly.
⚙️ Service routing and incident defaults
Service settings now support linking one internal service to multiple public status page components, along with a default severity for incidents tied to that service. This helps teams route updates more accurately and reduces manual setup during incident declarations.
📧 Subscription emails
Subscription notification emails now come from the status page’s brand name instead of a generic sender name, making them easier for subscribers to recognize.
🔐 Authentication and access
Organization settings now include a Security section for managing sign-in methods such as email and password, Google, GitHub, and SSO/SAML. The flow helps admins keep at least one access method available and makes private status page sign-in smoother by preserving the existing login session.
📄 Public status pages
Public status pages now have a cleaner design that better highlights active incidents, impacted services, and uptime history. Timeline cards, service grids, and the top banner now present outage severity more clearly so customers can understand what’s happening at a glance.
💬 Feedback links and API responses
The Groups settings view now points to the correct feedback board, so customers can open the feature request link without hitting a dead page. Public status API endpoints also handle non-JSON requests more gracefully, reducing unnecessary errors.