Deploy and migrate without false alarms
Server upgrades, migrations and big deploys mean planned downtime. Schedule a maintenance window and the monitor pauses on its own: no alerts, no dent in your uptime, and checks resume when the window ends.
Not checked · no alerts · not counted in uptime
- No alerts during the window
- Checks are skipped while the window is active, so nobody gets an email for downtime you planned.
- Uptime stays honest
- Time inside a window doesn't count against your uptime percentage or your status page.
- Set it and forget it
- Schedule windows up to a year ahead, each up to 7 days long. Monitoring resumes by itself when one ends.
How it works
- 1
Open the monitor
Go to its Maintenance tab.
- 2
Pick a start and an end
In your own time zone.
- 3
Do your work
The monitor shows “Maintenance” and comes back on its own.
Questions and answers
A period when a monitor is intentionally not checked because you expect it to be down. No alerts are sent and the time doesn't affect uptime.
Yes, up to a year ahead, with up to 20 upcoming windows per monitor.
Up to 7 days. To end one early, delete it and checks resume right away.
Yes. A job that is late during a maintenance window doesn't trigger an alert.
More features
- Website monitoringWebsites and APIs, with the reason for every failure
- Cron job monitoringHeartbeats for cron jobs, backups and scripts
- SSL certificate monitoringEmail reminders before a certificate expires
- Keyword monitoringCatch broken pages that still return 200 OK
- Status pageA public status page and uptime badges
Plan your next deploy with a maintenance window
Free for 10 monitors. No credit card required.
Start monitoring free