Maintenance windows — suppress alerts on purpose
Planned deployments, backup scripts or migrations make your site briefly unstable. A maintenance window pauses alert triggering during a time window — checks keep running, status is logged in the timeline, but nobody gets paged in the middle of the night. You choose between recurring weekly windows and a one-off scheduled maintenance with a date range.
# Two kinds of windows
Recurring (weekly)
One weekday plus a start and end time, e.g. every Sunday 02:00–04:00. The window repeats every week at the same time. Each entry is stored as a triple of weekday, start and end — the weekday as mon, tue, wed, thu, fri, sat or sun, the times in HH:MM format. There is deliberately no free-form cron pattern.
One-off scheduled (date range)
A single period with a title, optional description, start date/time and end date/time — meant for announced downtimes such as a database migration. As soon as the current time is between start and end, alerts for the selected website are suppressed. Once it ends the window stops automatically; it does not repeat.
What is suppressed
While a window is active, alert delivery for the affected website(s) is paused — offline, slow response, SSL, security, visual change, DNS and heartbeat alerts too. The check runs in two places: downtime alerts (including subpages) and security-score alerts are not opened at all during a window; all other alerts are opened and appear in the alert list, but their notification is suppressed at delivery time – as is a notification whose window opens only after the alert started.
Account-wide or per website
Every window has a scope. Account-wide means it applies to all websites in the account. Per website applies only to the selected site. Up to 20 recurring windows can be defined per website. A one-off scheduled maintenance with no website attached likewise applies account-wide.
# How the windows are evaluated
For each potential alert, XICTRAQ checks in this fixed order whether a window currently applies. The first matching rule wins:
1 One-off maintenance covers this website RIGHT NOW -> suppressed 2 Recurring weekly window of this website matches NOW -> suppressed 3 Account-wide weekly window matches NOW -> suppressed otherwise -> alert is delivered
Server time is UTC
Recurring windows are evaluated against server time (UTC). In summer time Central Europe is two hours, in winter one hour ahead of UTC — so offset the window accordingly if it must hit local night-time exactly. One-off scheduled maintenances are entered as date/time and interpreted by the server under the same UTC convention.
# Setup
Account-wide windows
Under /app/settings/maintenance you manage both kinds in two tabs: Recurring (weekday + start/end) and One-off scheduled (title + period). In the scope selector you pick account-wide or a single website from the same form. The list shows all active windows in one place.
Per-site windows
A recurring window for just one site is created either in the maintenance overview via the scope selector or directly in the settings tab of that website. Both paths write to the same per-site list — it is exactly the same window.
# Public announcement on the status page
Alert-suppressing maintenance windows and maintenance entries on a status page are separate things. To also announce a planned maintenance publicly, additionally create a dedicated maintenance entry on the status page.
Auto banner + subscriber reminder
A status-page maintenance entry (title, description, start, end) shows there automatically as a banner once it is active, and is visible up to 14 days in advance. Confirmed subscribers of the status page receive a reminder email about 60 minutes before it starts. These status-page entries additionally support their own recurrence: none, weekly or monthly. The time of day stays the same across daylight saving changes; monthly means the same day of the month, or the last day in shorter months.