Skip to content

Maintenance windows quickstart

By the end of this guide you’ll have a one-time maintenance window scheduled for Friday 14:00–14:30 UTC that silences any monitor tagged service:api.

  • One or more monitors tagged with service:api. Tags are an array on every monitor — set on create or via PUT.

If your monitors aren’t tagged yet:

Open the monitor → Settings → Tags → add service:api → save.

  1. Maintenance → New window.

  2. Configure:

    • Name: Friday API deploy.
    • Tags: service:api.
    • Schedule type: one-time.
    • Starts: 2026-05-10 14:00 UTC. Ends: 2026-05-10 14:30 UTC.
  3. Save.

The response includes is_currently_active: false (assuming the window is in the future) and confirms the start/end timestamps in RFC 3339.

The window appears in the Maintenance list with a status badge:

  • Scheduled — in the future.
  • Active — happening now.
  • Past — already ended.

When the window goes active, any matching monitor’s status badge in the dashboard gets a “Maintenance” overlay. Notifications are suppressed automatically.

Section titled “4. (Recommended) Publish on the status page”

For customer-visible maintenance, also create a status-page maintenance entry — see Status pages. The two objects are independent: the maintenance window suppresses internal paging, the status page maintenance shows “Scheduled” cards to customers.