Pauses that end, lists that filter

When pausing, How long? sets when the service starts again by itself: for 30 minutes, 1 hour, 3 hours, until tomorrow or until a time of your choice, at most 90 days. Until I resume is still there. This works straight from the service list as well. The console counts down to the end. Extend and Resume now change a running pause. A note for your team is visible only in the console and never appears on a status page.

You can put an end on a manually set status, too. After that the status page shows the measured status again. If a maintenance is still running then, it shows the maintenance status instead.

If your plan has no room when the pause ends, the service stays paused. The dashboard shows it, and the owner and admins of your organization get an email. Timed pauses and statuses work through the API and MCP as well. When planning a maintenance, you can now give its end as a duration.

Incidents are split into the tabs Open, Resolved, Internal and All, each with a count. You filter by severity, service, tag, status page and time range, by whether an incident was detected automatically or reported by hand, and search the title. Entries are grouped by day. The filters are part of the address, so you can share a filtered list as a link.

Select all results resolves or deletes everything that matches the filter, across pages too, up to 500 incidents at once. When a new incident comes in, the list no longer jumps. A notice at the top shows it instead.

Maintenances are split the same way into Upcoming & running, Past, Cancelled and All, with filters for type, service, tag, status page and time range.