Skip to main content

Maintenance Windows

Maintenance windows let you suppress alerts during planned work — deployments, upgrades, infrastructure changes — so your team isn't paged for downtime you already know about. While a window is active, failing checks in scope do not create incidents or send notifications.

Defining a Window

SettingDescription
Title / DescriptionWhat the maintenance is for
Start At / End AtWhen the window opens and closes
Recurrencenone, daily, weekly, or monthly
Recurrence EndOptional date after which the recurrence stops

A one-time window uses recurrence: none. Recurring windows are anchored to Start At and repeat the same slot (length End At − Start At) on the chosen cadence until the recurrence end (or indefinitely):

  • daily — repeats Start At's time-of-day every day.
  • weekly — repeats on Start At's weekday.
  • monthly — repeats on Start At's day-of-month. On shorter months the day is clamped to the last day: a monthly window anchored on the 31st runs on Feb 28 (29 in a leap year), Mar 31, Apr 30, and so on — it never drifts onto the wrong day.

Recurring times are anchored in UTC (they shift by an hour in local time across daylight-saving changes).

Response fields

Every maintenance window returned by the API also carries two read-only, server-computed fields:

FieldDescription
statusLifecycle right now: active, upcoming, or past
nextOccurrencesThe next concrete activations (startAt/endAt pairs, RFC3339 UTC) — the currently-active one first

Scope

A maintenance window can apply to:

  • Specific checks — only the listed checks are suppressed
  • Check groups — every check in the group is suppressed
  • The whole organization — when no checks or groups are attached, all checks are suppressed

Behavior

When a check fails while a window covering it is active, SolidPing skips incident processing entirely — no incident is opened, escalated, or notified. Results are still recorded, so your history and uptime metrics remain accurate; you simply won't be paged.

Windows can be listed by status (active, upcoming, past) from the dashboard or API, making it easy to see what is currently silenced and what is scheduled.