Maintenance windows

Planned work should page nobody.

Pause a monitor while you deploy, migrate or reboot. It keeps its history, stops running its policy, and resumes exactly as it was, either when you say so or at a time you set in advance.

Nothing is lost. The monitor keeps every past incident and every data point. Pausing is not deleting and not recreating.
Optional auto-resume. Set a time and the monitor comes back on its own, so a forgotten pause does not become a blind spot.
Per monitor. Pause only what the work touches. Everything else keeps watching normally.

Start free All features

01 · During the window

What pausing actually does.

No pages

The escalation policy does not run, so a planned restart does not wake the on-call engineer or fill a channel.

No false incidents

An outage you caused on purpose does not become a record that has to be explained later.

History preserved

Past incidents, uptime and response-time data all remain. The monitor picks up where it left off.

Resumes as it was

The same interval, the same policy, the same connections. There is nothing to reconfigure afterwards.

02 · When to reach for it

Planned work, not unplanned trouble.

Deployments and migrations

Anything where you already know the service will be unavailable for a period.

Server reboots and patching

Kernel updates and host restarts that take a machine down predictably.

Database maintenance

Schema changes and reindexing that make a backend refuse connections for a while.

Provider maintenance

Scheduled work by a hosting or network provider that you did not initiate but do know about.

Auto-resume for long jobs

Set the end time when you start, so the monitor is watching again the moment the window closes.

Not for a noisy service

If a monitor is alerting too often, the fix is a confirmation threshold or dampening. Pausing it hides the problem instead.

Questions

Common questions

Does pausing a monitor delete its history?

No. The monitor keeps every past incident and all of its uptime and response-time data. Pausing only stops it checking and stops its policy running. When it resumes it uses exactly the same configuration as before.

Can a maintenance window end automatically?

Yes. You can set an auto-resume time when you pause, which means the monitor starts watching again on its own. That avoids the common failure where a monitor is paused for a deploy and quietly stays paused for weeks.

What is the difference between a maintenance window and a schedule gate?

A maintenance window pauses the monitor itself, so no checks run and no incident is recorded. A schedule gate leaves the monitor running normally and only controls whether an alert is allowed through a particular branch of the policy.

Should I pause a monitor that alerts too often?

Better to fix the alerting. Raising the consecutive failure threshold or adding flap dampening addresses the noise while keeping the monitor watching. Pausing removes your visibility along with the noise.