This release ensures affected-service information stays accurate across status updates.

The Intercom live chat bubble is available again, making it easier to contact support.

This release gives you more control over what your monitored endpoints verify.

Use custom JSONPath checks to validate specific values in JSON responses from monitored endpoints.

This release fixes several customer-facing issues across billing, custom domains, and status pages.

Trial upgrade prompts now stay visible on status page admin screens, and payment failure emails now include a working link.

Custom domains now use TLS 1.2 or later, with support for TLS 1.0 and 1.1 discontinued.

Private services no longer affect the overall status shown on a dependent status page, and organizations with SSO role mappings can now be deleted correctly.

This release makes Global Services available across the product, from setup and monitoring to the public status page and subscriber notifications. It also adds real-time Slack notifications for status page updates.

Global Services can now be created, managed, and used throughout StatusPal. You can set a service as global or scoped to specific containers, view global services alongside container-based ones in settings, and manage their status from the dashboard.

Status page subscribers can now receive real-time Slack notifications when incidents, maintenance, or info notices are posted or updated, so they can stay informed without checking the page manually.

This release improves the way status pages render and behave, while also expanding incident management and team access controls. It also adds SCIM provisioning so organizations can keep roles and groups in sync automatically.

Public status pages now handle a few common edge cases more cleanly: new pages get the correct subdomain, uptime graphs stay intact after browser navigation, service names line up neatly with their status icons, and custom hostnames always use HTTPS once a certificate is in place.

Incident cards now show the incident’s lifecycle status at a glance, while keeping the last affected service status visible after resolution. The incident workflow also keeps service impact accurate when updates are posted to a scheduled maintenance, and incidents declared from Slack now update the linked service status correctly.

SCIM provisioning is now available for organizations using SSO, letting you sync roles and group membership from your identity provider. Admins can manage the connection from the security settings, see which users and groups are synced, and use the standard role group names directly in the setup flow.

Service status values and labels are now more consistent across incident management and notices, including clearer default incident severity wording and grouped notice badges when multiple services share the same status.

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.