This release adds image uploads to incident and template descriptions and improves how status pages preserve subscribers’ language preferences.

You can now add images to incident and template descriptions, making it easier to share visual context and details.

Status pages now keep the subscriber’s selected language after canceling a subscription, instead of switching to the browser’s language.

This release gives you more visibility into monitoring behavior and improves how notices are displayed.

Monitoring checks now include down-threshold settings.

This makes it easier to see how a check is configured at a glance.

Checks history and results history are now available, giving you more visibility into what happened and when.

You can look back at recent check activity and better understand how a check has been performing over time.

The notices list and notice cards are more reliable and easier to read. We also fixed paragraph spacing so notices look the same across email and the website.

This release improves how multi-language pages behave for subscribers and visitors, and fixes a few API and security edge cases.

Subscription-related pages and emails now follow the language a subscriber chose, instead of falling back to the visitor’s browser language or the page default. The CAPTCHA widget on the subscription form also uses the page’s selected language.

Organization API keys can now access the status page access groups API the same way they already access other status page resources.

This release makes it simpler for new teams to get set up.

A new onboarding screen now guides new users through setting up their workspace with clear progress, collapsible sections, and step-by-step actions. It also makes Slack-based incident setup easier by streamlining the collaboration step.

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.

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 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 notification emails now come from the status page’s brand name instead of a generic sender name, making them easier for subscribers to recognize.

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 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.

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.

This release makes sign-up easier with password managers, lets admins export incident reports, and refreshes a few customer-facing links and status page behaviors.

Password managers can now generate passwords that work during registration without tripping extra password rules.

Admins can now download incident reports, instead of this being limited to owners only.

Canceled maintenances now age out of the Past incidents section after a few days, so older canceled items don’t linger.

StatusPal’s changelog, roadmap, and feedback links now point to the new Canny board and domain.

This release expands access to StatusPal Monitoring V2, tightens how legacy custom domains are handled, and includes a few improvements to incident workflows.

Legacy custom domains can no longer be provisioned through the API. This closes the last remaining path for creating them after they were removed from the UI.

StatusPal Monitoring V2 is now available for new organizations. Existing organizations can request access by contacting us.

Incident templates now let you choose a separate internal template title while keeping the incident title used for the actual incident.

Incident end times can no longer be set in the future, preventing affected services from remaining marked as impacted on the public status page after an incident should have ended.

This release makes custom seat pricing easier to understand and gives the incidents API a new way to narrow results.

When an annual plan is selected, the add-ons, cost estimate, and manage extra seats screens now show a (monthly) label so the billing setup is clearer.

The API can now return only incidents with a chosen status, making it easier to fetch the records you need.

A couple of updates to help you write cleaner incident updates and get more out of your webhooks.

The rich-text editor used for incidents and maintenance updates got a round of polish. Hover any block to reveal a drag handle for reordering, and open the block menu to insert a new block, duplicate, clear formatting, or delete. The same editor is now used consistently across every notice and update form.

Two improvements to the webhooks we shipped last cycle: