> For the complete documentation index, see [llms.txt](https://docs.statuspal.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.statuspal.io/platform/incidents-and-maintenance/filtering-incidents-and-maintenance.md).

# Filtering incidents & Maintenance

Finding a specific incident or maintenance can become challenging as they grow in number. To assist you in that task, the Incidents / Maintenance listing page has a search feature, which you can use by clicking on the "Filter" button.

<figure><img src="https://4061983002-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgIMm5p2V7PNx3dS7vwKE%2Fuploads%2Fxdqxmnbuqp4rhpJU8RdU%2FDEV%20-%20StatusHQ.jpeg?alt=media&amp;token=aa2d41cd-e97a-41a8-999c-6f038bfbab73" alt=""><figcaption></figcaption></figure>

Submitting a search term will trigger a search request looking for incidents & maintenance with a matching title.

We also offer a minimal search query language to filter incidents & maintenance by the "starts at" and "ends at" dates. Here are some examples of how you can use it:

```
starts_at:>2025-06-30
```

(finds incidents & maintenance that start after 2025-06-30)

```
ends_at:<2025-07-21
```

(finds incidents & maintenance that end before 2025-07-21)

```
starts_at:2025-05-18 DoS Attack
```

(finds incidents & maintenance that start on 2025-05-18 with title containing "DDoS Attack")

### Filtering by status

The same "Filter" panel has a **Filter by status** dropdown:

* **Active** — the incident or maintenance has started and has not ended yet, so it is currently showing as ongoing on your status page.
* **Inactive** — it is not currently ongoing, either because it has already been resolved or because it is a maintenance scheduled to start later.
* **Canceled** — a "Canceled" update was posted, so it no longer appears on your status page.
* **All** — the default, no filtering by status.

The search term and the status filter apply together: an incident has to match both to show up in the results.

### Incident IDs

Each row in the list shows the incident's ID next to its type, for example `#1234`. This is the quickest way to tell apart incidents that share a title. It is the same ID that appears in the incident's URL and in the API.