Maintenance windows

A maintenance window tells SutramX that downtime is planned. While a window is in progress, monitors in its scope keep being checked, but down alerts are held back, the monitors show Maintenance, and your status pages show the work as planned maintenance instead of an outage.

What a maintenance window does#

Schedule a maintenance window#

1. Go to Incidents in the sidebar and open the Maintenance tab.
2. Click Schedule Maintenance.
3. Fill in the form (see the fields below).
4. Click Schedule.

You can also get there from a monitor: open its ⋮ menu and choose Maintenance (from the monitor list) or Schedule maintenance… (from the monitor's page).

Only the workspace owner can create, edit, cancel or delete maintenance windows, because a window silences alerts. Other members can see them.

Fields#

Scope#

• All monitors covers every monitor in the workspace, including monitors you add later.
• Specific monitors covers the monitors you tick. Use the search box and Select all visible to pick many at once.
• Monitor groups covers every monitor that is in the chosen groups at the time, including monitors added to the group after you schedule the window.

You can select up to 500 monitors, or up to 500 groups, per window.

Overlapping windows#

Windows may overlap. If a new window overlaps a scheduled or active window for some of the same monitors, the form shows "Heads up: this overlaps … existing maintenance window" and lists them. You can still save; both windows apply.

Recurring windows#

Use Daily or Weekly for routine work such as nightly backups or a weekly deploy slot.

• Each occurrence keeps the same local start time and duration, in the window's Time zone. Daylight-saving changes are handled.
• When an occurrence ends, the window rolls forward to the next matching day and its status returns to Scheduled.
• The series stops after Repeat until. With no end date it repeats indefinitely.
• Past occurrences stay excluded from uptime, even if you cancel the series later.

Example: a weekly window on Sunday 02:00–04:00 in Europe/London. Set Start time to the next Sunday at 02:00, End time to 04:00 the same day, Repeat to Weekly, Repeat on to Sunday and Time zone to Europe/London.

For alert silencing that repeats every night, such as "no pages between 22:00 and 07:00", use quiet hours instead. See Quiet hours and deployment windows.

Window status#

Edit, end, cancel or delete#

Each window in the list has these actions:

• Edit opens the form. If you move a window's times, its reminder and start notices are sent again for the new time.
• Cancel (for a scheduled window) stops it from running. Alerts will not be silenced for it.
• End now (for a window in progress) ends it immediately by cancelling it. Alerts resume straight away for the affected monitors; if a monitor is still down, its held-back down alert goes out on its next check. Because the window is cancelled, its time no longer counts as maintenance in uptime figures.
• Delete removes the window permanently.

Recurring windows have different stop actions:

• Skip this occurrence (for a scheduled occurrence) or End this occurrence (for one in progress) stops only the current or next occurrence. The series continues.
• Cancel series stops all future occurrences.

Maintenance notifications#

SutramX tells your team about maintenance:

Details:

• No reminder is sent for a window created (or moved) less than 24 hours before it starts, or for Daily recurring windows.
• Emails go to the workspace owner and your verified alert recipients for All monitors windows. For monitor or group windows, they go to the owner and the recipients of the monitors in scope.
• The Maintenance Alerts switch in the Notification Preferences section of Alerts → On-call & escalation turns maintenance emails on or off. Chat-channel start and end notices are sent either way.
• Webhooks receive the events maintenance.started and maintenance.ended. See Webhooks.

Maintenance on status pages#

Status pages show maintenance automatically for the monitors they display:

• During a window, affected components show Under maintenance. If nothing else is wrong, the page banner reads Under maintenance.
• Ongoing windows and windows starting in the next 30 days that touch the page's monitors are listed with their title, description, times and affected components (up to 20 windows).

A window only appears on a status page if it covers at least one monitor shown on that page and Show on public status pages is on. An internal-only window still silences alerts, but status pages show the affected monitors' real state. See Status pages overview.

Create windows with the API#

Maintenance windows are available at https://api.sutramx.com/maintenance (GET, POST, PUT /maintenance/<id>, DELETE /maintenance/<id>, and POST /maintenance/<id>/skip-occurrence for recurring windows). Times are ISO 8601. Creating and changing windows needs an owner session; workspace API keys are not owners.

{
  "title": "Database upgrade",
  "description": "Upgrading Postgres to the next major version.",
  "startTime": "2026-10-10T01:00:00Z",
  "endTime": "2026-10-10T03:00:00Z",
  "timezone": "UTC",
  "scopeType": "group",
  "groupIds": ["3f2b9c1e-8a4d-4f6e-9b2a-1c3d5e7f9a0b"],
  "impact": "high",
  "recurrence": { "type": "none" }
}

The response may include a warnings array, for example when the window overlaps another one.

Common questions#

Why did I get an alert during maintenance? The monitor was not in the window's scope (check the group membership), the window had not started yet, or the alert came from a different monitor. Open the incident: a suppressed incident shows it was held back by a maintenance window.

The window ended and I got a down alert straight away. The monitor was still down when the window ended. SutramX sends the held-back alert so a failed upgrade doesn't go unnoticed.

Do maintenance windows stop checks? No. To stop checks completely, pause the monitor. Paused time is also excluded from uptime, but the monitor shows Paused rather than Maintenance on status pages.

Do heartbeat monitors respect maintenance? Yes. A run missed during the window does not alert unless the job is still missing when the window ends.