Maintenance windows
Planned downtime that doesn't page anyone.
Planned downtime that stays quiet
You already know about the deploy. Getting paged for it is noise, and worse, it trains you to ignore the next page that isn't planned.
Schedule a maintenance window and the checks keep running, so you still see what happened, but the alerts stay quiet for its duration. Nobody's phone goes off for downtime you put on the calendar.
It doesn't count against your uptime
Downtime inside a window is excluded from the uptime maths, so a planned reindex doesn't dent the number your status page reports or the SLA you quote.
Windows are per monitor, so a database drill silences the database checks without muting everything else. The monitors you didn't schedule still page you as normal.
One-off or recurring
Set a window once for a specific migration, or make it recurring for the nightly job that always runs at 02:00. A recurring window repeats on its schedule without you touching it again.
Checks run throughout either way. A window changes what alerts and what counts, not what's watched.
Build trust with
public status pages.
Every monitor can back a public status page, so the people asking whether you're down can answer it themselves. Ninety days of history per monitor, on your own domain.
Every outage,
written down as it happens.
A failed check opens an incident on its own, and it keeps a timeline: when it broke, what we saw, when it recovered. Nobody has to remember to write the post-mortem's first half.