A Maintenance Window is a feature that allows you to define specific time periods when you do not want UptimeRobot to monitor your servers, websites, or applications. These could be one-time or recurring periods. This feature is exclusively available with our paid plans.
This is particularly useful when you have regular tasks that cause expected downtime, such as:
Backups
Batch jobs
Restarts
Upgrades
etc.
Setting up maintenance windows not only prevents you from receiving false alerts during these routine tasks but also ensures that these expected downtimes do not impact your overall uptime statistics. For most monitor types (HTTP, Keyword, Port, Ping, API, etc.), if a check would have failed during the window, no incident is created and the monitor's status is left exactly as it was going into the window.
Heartbeat/cron monitors are the one exception to watch for. If a heartbeat monitor is already showing DOWN when the maintenance window starts, it stays DOWN for the entire window, even after the job it's tracking resumes running — it only flips back to UP on the first check that happens outside the window. To avoid a heartbeat monitor showing DOWN unnecessarily, start the maintenance window before you stop the job it's monitoring, and expect the UP status to register only after the window ends, not the moment the job resumes.
Checks also run less frequently while a monitor is inside a maintenance window, so don't expect the same check cadence you'd see outside of one.
Before setting up a Maintenance Window, please check the time zone of your account to ensure the correct scheduling. This can be found under 'Account Settings' in the basic account details section.
Finally, once you've set up a Maintenance Window, remember to associate it with the monitors you want it to apply to. This can be done efficiently using the 'Bulk Actions' functionality to apply it to multiple monitors at once.