Downtimes
A downtime is a scheduled window during which APIContext pauses monitoring and suppresses alerts. Use downtimes to prevent false positives during planned maintenance, deployments, or known outage windows.
Two scopes
| Scope | What it pauses | Who can set it |
|---|---|---|
| Schedule-level | A single monitor's schedule in a specific project | Project Editors and above |
| Organization-level | All monitors across every project in the organization | Organization Admins |
Schedule-level downtimes are the most common: they let you silence a specific monitor while its target API is under maintenance. Organization-level downtimes are for broader events like infrastructure-wide maintenance windows.
How downtimes affect data
During a downtime window:
- Monitors do not run: no API calls are made, so there are no results to record
- Alerts are suppressed: even if a monitor was already in a failure state, no new alerts fire
- Quality scores are unaffected: the paused period is excluded from CASC score calculations, so a planned outage does not lower your score
When the downtime ends, monitoring resumes automatically on the next scheduled interval.
See also
- Managing downtimes guide: creating and editing schedule-level downtimes
- Schedules concept: how monitoring frequency and regions work
- Alerts and Webhooks concept: how alert suppression interacts with downtimes