Maintenance windows

A maintenance window does two things at once: it tells your status page's visitors that planned work is happening, and it stops that planned work from paging you or your team as if it were an outage.

Schedule a window

1. Go to a status page's Maintenance tab. Maintenance windows belong to your organization, not to one specific page — every published page with a covered component shows it.
2. Click Add Maintenance Window and fill in:
   • Title and description — shown on the status page as-is; write it for the people reading it, not for yourself.
   • Start and end time — pick from the in-app date/time picker.
   • Affected components — the services and/or cron monitors this maintenance covers.
3. Save. The window appears under Upcoming on every affected published page until it starts, moves to Active, then drops off once it ends.

What suppression actually does

For every service or cron monitor covered by an active window (starts_at <= now < ends_at):

• No new incident opens, and no alert fires — even if the underlying check is genuinely failing. This is intentional; it's the entire reason the feature exists.
• The status page shows that component — and, if nothing else is worse, the overall page — as under maintenance rather than down or degraded.
• Historical uptime is unaffected either way — the suppressed period doesn't count as downtime, and the day rolls up as "maintenance", not as a gap in the record.
• An incident that was already open before the window started keeps running as normal. A window only suppresses opening a new incident — it never auto-resolves or hides an existing one.

Checking itself never stops — UptimeHunt keeps evaluating the service or job throughout the window. If it's still failing after the window ends, the very next failing check opens an incident immediately, exactly as it would outside a window.

Related Documentation

• Create and publish a status page
• Publish incident updates
• Incidents
• Alerting & Integrations