Maintenance windows

Planned work should not look like an unexplained outage.

Schedule a named time window, select affected monitors, and distinguish intentional maintenance from the ordinary scheduled-check path.

Start monitoring Read the documentation

Deployment windowAPI maintenance

Selected monitors · 22:00–23:30 UTC

Scheduled

Start and end

Define a bounded maintenance schedule.

Selected monitors

Scope the window only to affected services.

Suppressed checks

Pause the ordinary scheduled path while active.

Public state

Represent planned work on eligible status pages.

01Schedule

Scope planned work precisely.

Choose the start, end, and monitors affected by a deployment or maintenance activity instead of muting the whole workspace.

Maintenance schedulePingBeacons

Deployment windowAPI maintenance22:00–23:30 UTCScheduled

Selected monitorsPublic APICheckout serviceWorker heartbeat

02Active behavior

Pause ordinary scheduled checks and alerts.

During the active window, assigned monitors are skipped by the existing maintenance-aware scheduled check path.

Check historyPingBeacons

14:08:02200 OK184 ms

14:03:02200 OK206 ms

13:58:01503412 ms

03Communication

Show maintenance as maintenance.

When an assigned component appears publicly, its status can communicate planned work rather than presenting it as an ordinary outage.

Public statusPingBeacons

Example Operations

All systems operationalUpdated moments ago

WebsiteOperational

Public APIOperational

Scheduled jobsOperational

SSL certificateOperational

API maintenance · Tomorrow, 22:00 UTC

Start with PingBeacons

Schedule planned work without rewriting the incident story.

Select the affected monitors, define the window, and keep intentional downtime clear.

Start monitoring Explore features