Communicate
Maintenance Windows
Schedule maintenance windows to suppress alerts and update status pages during planned downtime.
Overview
Maintenance windows let you plan downtime for your services without triggering false alerts. When you know that a service will be unavailable, for a database migration, infrastructure update, or deployment, you can schedule a maintenance window in advance. While the window is in progress, the monitors you selected keep being checked and their results are recorded, but they open no incidents. The status pages you attach the window to show it, and their subscribers are told.
This keeps your team focused on the planned work instead of responding to expected downtime alerts. It also communicates transparently to your users that the outage is planned and under control.
How Maintenance Windows Work
A window is Scheduled until its start time, In progress until its end time, and then Completed. You can also cancel it. Uptimy moves windows along on its own, so you don't have to start or finish them by hand.
While a window is in progress:
- The monitors selected under Affected services open no incidents, so no workflows run for them. Their checks keep running and results are recorded. Every other monitor alerts as usual.
- Incidents that were already open stay open and resolve when their monitor recovers.
- Status pages the window is attached to show a Maintenance in progress banner, unless the page shows an open critical or high incident. Monitors on the page keep showing their live status.
When the window ends, incidents open again as usual. A healthcheck that is still down at that point opens an incident within about 10 minutes.
Creating a Maintenance Window
Open Maintenance in the app and click Schedule maintenance. Fill in the following fields to define your window.
| Field | Description |
|---|---|
| Title | A short, recognizable name shown to your team and customers (e.g., "Primary database cluster migration"). |
| Description | Required. The work being performed and its expected impact. It is shown on your status pages and in the notice subscribers get. |
| Start time | When maintenance begins, in your local time zone. The window starts on its own at this time. |
| End time | When maintenance is expected to finish, in your local time zone. The window completes on its own at this time. |
| Affected services | The healthchecks and heartbeats whose alerts are suppressed while the window is in progress. Each one can have an optional impact description. Status pages list them by name. |
| Publish to status pages | The pages that show the window. Leave it empty to keep the window internal: it then shows on no page and no subscriber is told. |
From the command line, pass the monitors with --services and the pages with --status-page. Without --services the window suppresses nothing, and without --status-page it shows on no page.
# Schedule a maintenance window for one healthcheck, shown on one status page
uptimyctl maintenances create \
--title "Database migration" \
--description "Upgrading the primary database to v5.2. Writes may fail for a few minutes." \
--start-at "2026-12-01T02:00:00Z" \
--finish-at "2026-12-01T04:00:00Z" \
--services '[{"uuid":"<application-uuid>","name":"API","functionality":"Writes may fail"}]' \
--status-page <status-page-uuid>--services takes a JSON array with one object per monitor. uuid is a healthcheck's application UUID (from uptimyctl applications list) or a heartbeat's UUID (from uptimyctl heartbeats list), name is the name shown on status pages, and functionality is the impact description. Repeat --status-page for each page.
Install uptimyctl from github.com/uptimy/uptimyctl to manage maintenance windows from your terminal or CI/CD pipelines.
Recurring Maintenance
Recurring maintenance windows are not built in yet. For regular maintenance tasks like weekly patching or nightly backup periods, teams automate repeated windows by creating them on a schedule with the CLI or API. For example, a scheduled GitHub Actions job can run the uptimyctl maintenances create command shown above ahead of each cycle.
Choosing the Right Schedule
Schedule maintenance during your lowest-traffic periods. Review your analytics to find the best window. For global services, consider rotating maintenance times across regions so that no single user group is always affected.
Subscriber Notifications
Subscribers of the status pages a window is attached to hear about it without any workflow. They get a notice:
- When it is published: the window is attached to their page, when you create it or later. The notice has the title, description, start time and end time.
- When its status changes: the window starts, completes, or is cancelled, whether on schedule or by hand.
- When you post a public update: each update you post as Public. Internal updates never go out.
Keeping Subscribers Informed
Notices go out by email, Slack, Discord, Teams or webhook, whichever each subscriber chose. Status page subscribers come with Growth and above; pages on Free and Starter have none. See Status Pages for how visitors subscribe.
Starting and Ending
Windows start and complete on their own. Uptimy checks every minute, so a window starts within a minute of its start time and completes within a minute of its end time. Each automatic change notifies subscribers the same way a change by hand does. You can still step in from the window in the app:
- Start now starts it before its start time.
- Complete ends it early and re-enables alerts ahead of schedule.
- To run longer, change End in Edit details before the window ends. It keeps going until the new end time. Once a window has completed it stays completed, so schedule a new one if you need more time after that.
- Cancel calls it off. A cancelled window suppresses nothing and leaves your status pages.
On Your Status Pages
A window shows only on the status pages it is attached to. Each page lists upcoming and in-progress windows under Scheduled maintenance, with the description, affected services, start and end time, and public updates. Completed windows stay listed for 7 days. In the app, past windows stay on the Maintenance page under Past.
Common Use Cases
- Database migrations: Schedule a window before running schema changes or major version upgrades. Select all services that depend on the database so their alerts are suppressed.
- Infrastructure updates: Plan windows for Kubernetes node upgrades, load balancer changes, or network reconfigurations that may cause brief service disruptions.
- Deployment windows: If your deployment process causes temporary downtime or restarts, schedule a short maintenance window around each deployment to avoid false alerts.
- Security patching: Schedule windows around weekly or monthly OS and dependency patching across your fleet, automating creation via the CLI if the cadence is regular.
- Certificate rotation: Schedule maintenance around TLS certificate renewals to suppress SSL check alerts during the brief period when the old certificate is replaced.
- Capacity scaling: Plan windows for adding or removing capacity, resizing instances, or migrating workloads between availability zones.
CLI Reference
Maintenance windows can be managed from the command line using uptimyctl. This is useful for integrating maintenance scheduling into your CI/CD pipelines or deployment scripts.
# Create a maintenance window before a deployment
uptimyctl maintenances create \
--title "Deployment" \
--description "Deploying v2.5.0. The API may restart briefly." \
--start-at "2026-12-15T14:00:00Z" \
--finish-at "2026-12-15T14:30:00Z" \
--services '[{"uuid":"<application-uuid>","name":"API","functionality":"Brief restarts"}]' \
--status-page <status-page-uuid>
# Start a window early
uptimyctl maintenances start <uuid>
# Run longer: move the end time
uptimyctl maintenances update <uuid> --finish-at "2026-12-15T15:00:00Z"
# Complete a window early
uptimyctl maintenances resolve <uuid>
# Cancel a window
uptimyctl maintenances cancel <uuid>
# List maintenance windows
uptimyctl maintenances listBest Practices
- Always schedule maintenance windows before starting planned work, not after alerts start firing.
- Write clear descriptions that explain what work is being performed and the expected impact. Your users read them.
- Select all affected services to ensure complete alert suppression.
- Attach the window to your status pages so subscribers know about planned downtime in advance.
- Automate window creation via the CLI or API for predictable maintenance tasks like weekly patching or nightly backups.
- Complete windows early when work finishes ahead of schedule to re-enable alerts promptly.
- If work might run over, move the end time before the window ends. Alerts are never suppressed past the end time.
Alert Suppression Scope
Maintenance windows only suppress alerts for the monitors you select under Affected services. Other monitors continue to alert normally. Double-check your selection before the window starts to avoid unexpected alerts from related services that were not included.