Changelog
Follow up on the latest improvements andΒ updates.
RSS
This release expands access to StatusPal Monitoring V2, tightens how legacy custom domains are handled, and includes a few improvements to incident workflows.
π Custom domains
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
StatusPal Monitoring V2 is now available for new organizations. Existing organizations can request access by contacting us.
π Incident templates
Incident templates now let you choose a separate internal template title while keeping the incident title used for the actual incident.
π¨ Incidents
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.
π³ Clearer custom seat pricing
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.
𧩠Filter incidents by status
The
/incidents
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.
βοΈ A sharper notice editor
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.
π Smarter outgoing webhooks
Two improvements to the webhooks we shipped last cycle:
- notice.createdpayloads now include the affected service statuses, so subscribers get the full picture in a single event.
- When one notice update changes several services at once, those changes are now batched into a single webhook instead of firing one per service.
The language selector on team invites now appears only when it's useful β when you're inviting a Viewer and your status page supports more than one language.
Other roles default to English, so inviting teammates is simpler.
A few updates to give you more control over integrations, team access, and how you sign in.
π Outgoing webhooks
Push real-time status events to your own systems. Create a webhook, point it at any HTTPS endpoint, and choose which events you want:
- Service status changes (ok / minor / major / maintenance)
- New notices (incidents, maintenance, info)
- Notice updates posted to a timeline
- Changes to an existing notice
Scope each webhook to all of your status pages or just specific ones. Every payload is signed with a secret so you can verify it came from us. Prefer to manage them programmatically? There's a full REST API, documented in our OpenAPI reference.
π₯ Member groups
Organize team members into groups and control exactly what each group can reach: scope them to all status pages or a specific set, and decide whether they get access to Incident Management and Monitoring. A cleaner way to manage permissions as your team grows.
π Manage your sign-in methods
From your profile you can now link or unlink Google and GitHub, and set a password to enable email + password sign-in. Mix and match however you like, we'll always keep at least one sign-in method active on your account.
We are consolidating our changelog under this new portal.
Previous entries can be found at:
and
However, for any new changes, please follow this portal from now on.