> ## Documentation Index
> Fetch the complete documentation index at: https://docs.anomalyarmor.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Blackout Windows

> Suppress all alerts during planned maintenance or holidays

<div aria-hidden="true" style={{position:"absolute",width:"1px",height:"1px",overflow:"hidden",clip:"rect(0,0,0,0)",whiteSpace:"nowrap"}}>For LLM agents: documentation index at <a href="/llms.txt" tabIndex={-1}>/llms.txt</a>, full text at <a href="/llms-full.txt" tabIndex={-1}>/llms-full.txt</a>. Append .md to any page URL for plain markdown.</div>
Blackout windows let you temporarily suppress all alert notifications company-wide. Use them during planned maintenance, deployments, holidays, or any period when alerts would create unnecessary noise.

## How Blackouts Work

* Blackouts suppress **all** alerts for the entire company during the window
* Unlike [operating schedules](/alerts/schedules) (which are per-rule), blackouts are global
* Suppressed alerts are still recorded in the alert log with reason "blackout period"
* Blackouts can be one-time or yearly recurring

## Creating a Blackout

<Steps>
  <Step title="Navigate to Blackouts">
    Go to **Alerts** in the sidebar, then click the **Blackouts** tab.
  </Step>

  <Step title="Click New Blackout">
    Click **New Blackout** to open the blackout form.
  </Step>

  <Step title="Name the Blackout">
    Give it a clear, descriptive name (e.g., "Holiday Freeze 2026" or "Database Migration Window").
  </Step>

  <Step title="Set Start and End Times">
    Use the datetime picker to define the window. All times are interpreted in your company's configured timezone.
  </Step>

  <Step title="Choose Recurrence">
    Select the recurrence type:

    * **None** for a one-time blackout
    * **Yearly** for events that repeat annually
  </Step>

  <Step title="Save">
    Click **Save** to activate the blackout. It will begin suppressing alerts at the configured start time.
  </Step>
</Steps>

## Recurrence Options

| Type   | Behavior                     | Use Case                                |
| ------ | ---------------------------- | --------------------------------------- |
| None   | Fires once, then expires     | Deployment windows, one-off maintenance |
| Yearly | Repeats same dates each year | Company holidays, annual freeze periods |

<Note>
  Yearly recurring blackouts match the month and day, adjusting for timezone. A blackout from Dec 24-26 will repeat every year on those dates.
</Note>

## Managing Blackouts

* Active blackouts suppress alerts immediately when the window starts
* Toggle **is\_active** to temporarily disable a blackout without deleting it
* Past one-time blackouts remain in the list for audit purposes but have no effect

<Tip>
  Create recurring yearly blackouts for predictable events like company holidays. Use one-time blackouts for ad-hoc maintenance windows.
</Tip>

## Blackouts vs Operating Schedules

| Feature       | Operating Schedules          | Blackout Windows      |
| ------------- | ---------------------------- | --------------------- |
| Scope         | Per-rule                     | Company-wide          |
| Timing        | Recurring weekly pattern     | Specific date ranges  |
| Use case      | Business hours               | Maintenance, holidays |
| Configuration | Assigned to individual rules | Applies globally      |

<Warning>
  Blackouts override operating schedules. If an event falls within both an active schedule and an active blackout, the blackout takes precedence and the alert is suppressed.
</Warning>

## Common Questions

### How do I silence alerts during a planned deployment?

Create a one-time blackout in **Alerts > Blackouts** with the start and end times of your deployment window. The blackout suppresses all alerts company-wide until it ends. Suppressed events are still logged in **Alerts > History** with reason "blackout period".

### What's the difference between a blackout and an operating schedule?

Blackouts are company-wide date ranges, typically used for maintenance windows and holiday freezes. [Operating schedules](/alerts/schedules) are per-rule recurring weekly patterns, typically used for business-hours-only alerting. If both apply, the blackout wins and the alert is suppressed.

### Can blackouts repeat every year for holidays?

Yes. Set **Recurrence** to **Yearly** when creating the blackout and it will repeat on the same month and day each year, adjusting for timezone. This is the recommended pattern for company holiday code freezes.

### Do suppressed alerts still show up anywhere?

Yes. All blackout-suppressed events are written to **Alerts > History** with the reason "blackout period", so you can audit what happened during the window without receiving the notifications in real time.

## Next Steps

<CardGroup cols={2}>
  <Card title="Alert Rules" icon="list-check" href="/alerts/alert-rules">
    Configure per-rule schedules and conditions
  </Card>

  <Card title="Best Practices" icon="lightbulb" href="/alerts/best-practices">
    Reduce alert fatigue across your team
  </Card>
</CardGroup>