Pausing and resuming monitors
Temporarily stop checks without deleting the monitor.
Pausing stops check execution for a monitor without losing its history, notifications, or settings. Useful when you're taking a service offline for an extended change and don't want incident noise.
Pause or resume
- Open Uptime in the sidebar.
- Find the monitor in the table.
- Click the row's action menu and choose Pause (or Resume on a paused monitor).
The same action is exposed on the monitor's detail page header. Only admins and superadmins can pause monitors — the endpoint is POST /api/v1/monitors/pause/:monitorId and it toggles the isActive flag.
What happens while paused
- No checks run. The job is skipped by the scheduler until the monitor is resumed.
- Status changes to
paused. Uptime %, status window, and response-time charts freeze at the last recorded values. - No new incidents are opened. Open incidents are not auto-resolved by pausing — resolve them manually if needed.
- Notifications are not sent for the paused monitor.
Filtering paused monitors
The monitors list has a status filter that lets you show only Active or only Paused monitors. The dropdown sets isActive=true|false on the list query.
For suppressing alerts during a planned window without stopping checks, use a maintenance window instead — checks still run and data is recorded, but notifications are muted.