Maintenance windows

Planned downtime that doesn't page anyone.

Planned downtime that pages no one.

  • You already know about the deploy. Getting paged for it is noise, and worse, it trains you to ignore the next page that isn't planned.

    Schedule a maintenance window and the checks for the monitors it covers stop for its duration, so nothing alerts and no incident opens. Nobody's phone goes off for downtime you put on the calendar.

  • Downtime inside a window is excluded from the uptime maths, so a planned reindex doesn't dent the number your status page reports or the SLA you quote.

    Windows are per monitor, so a database drill silences the database checks without muting everything else. The monitors you didn't schedule still page you as normal.

One-off or recurring

Set a window once for a specific migration, or make it recurring for the nightly job that always runs at 02:00. A recurring window repeats on its schedule without you touching it again.

Checks run throughout either way. A window changes what alerts and what counts, not what's watched.

The rest of the platform.

Alerts on the change, not every minute.

Once when it breaks, once when it recovers, to Slack, Discord, a webhook, email, or your phone. A confirmation streak holds back the blips.

A status page your users can read.

Every monitor can back a public status page with ninety days of history, on your own domain, so the question answers itself.

Every outage, written down as it happens.

A confirmed failure opens an incident and keeps the timeline, detected to resolved. The first half of the post-mortem writes itself.

Seven kinds of check, one app.

HTTP / Website, Keyword, API, Heartbeat, Scheduler, DNS, and Port. Every one reports up, slow, or down, on the same interval, into the same alerts.

Tune it when the defaults aren't right.

Interval, slow threshold, timeout, failure streak, redirects, SSL and domain expiry. Every knob the create form has, with a sane default on each.

Everything the dashboard does, the API does.

Create, test, mute, and delete monitors over the REST API with a project key, or let your agents do the same over MCP.

Maintenance questions

No. The monitors it covers are not checked while the window is active, so nothing alerts, no incident opens, and the time is left out of your uptime. Checks resume on their own when the window ends.

No. Downtime inside a window is excluded from the uptime maths, so a scheduled deploy or reindex doesn't count against the number your status page and SLA report.

Yes. Windows are per monitor, so you can silence the checks for the thing under maintenance while every other monitor keeps alerting as normal.

Yes. A window can be one-off for a specific change, or recurring for a job that runs on a schedule, like a nightly reindex. Recurring windows repeat without further setup.

Know the second it breaks

Free to start. No credit card.