> For the complete documentation index, see [llms.txt](https://support.incidents.cloud.solarwinds.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.incidents.cloud.solarwinds.com/~/changes/lGFY3mJPy207GveiFTeX/terraform-and-api-documentation/incident-rate-limiting.md).

# Incident Rate Limiting

Squadcast has the following Incident Rate Limits in place. This limit is calculated over **1-minute fixed time windows**.

| Pricing Plans | Rate Limits (incidents/min) |
| ------------- | --------------------------- |
| Trial         | 15                          |
| Free          | 15                          |
| Pro           | 300                         |
| Premium       | 500                         |
| Enterprise    | 1000                        |

When Incident Rate limits are exceeded, our system throttles your alert requests for the reasons listed below:

* To not overwhelm the system and provide a fair service for all the accounts on Squadcast in terms of resource consumption
* To ensure that there is no violation of the platform
* To not bombard the user with notifications for irrelevant or unnecessary incidents
* To ensure that only meaningful and actionable alerts are sent into Squadcast

## What kind of events do the Incident Rate Limits include? <a href="#what-kind-of-events-do-the-incident-rate-limits-include" id="what-kind-of-events-do-the-incident-rate-limits-include"></a>

{% hint style="info" %}
**Incident Rate Limits Calculation**

[<mark style="color:blue;">Suppressed</mark>](/~/changes/lGFY3mJPy207GveiFTeX/services/alert-suppression.md) incidents and [<mark style="color:blue;">Duplicate</mark>](/~/changes/lGFY3mJPy207GveiFTeX/services/alert-deduplication-rules/alert-deduplication-rules.md) events will be counted towards the Incident Rate Limits Calculation.
{% endhint %}

{% hint style="info" %}
**Note**: Auto-resolve events coming in via alert source integration webhooks will not be counted towards rate limits.
{% endhint %}

## How can I ensure that I don’t exceed the Incident Rate Limits? <a href="#how-can-i-ensure-that-i-dont-exceed-the-incident-rate-limits" id="how-can-i-ensure-that-i-dont-exceed-the-incident-rate-limits"></a>

There are a few ways to control the kind of events that come into Squadcast. This is also done to ensure that you reduce alert fatigue and send in actionable events only.

* Configure your third-party tools to send in only the alerts you will need to take action on instead of sending in every single alert. For example, you don’t need all of the warning alerts and will probably need just the ones that impact customer SLAs or your internal SLOs.
* Use the [<mark style="color:blue;">**Discard**</mark>](/~/changes/lGFY3mJPy207GveiFTeX/services/alert-suppression.md#discarding-suppressed-incidents) function to avoid hitting the [<mark style="color:blue;">**Incident Rate Limits**</mark>](/~/changes/lGFY3mJPy207GveiFTeX/terraform-and-api-documentation/incident-rate-limiting.md) as Suppressed events that are discarded don’t get counted against the allowed Incident Rate Limits.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://support.incidents.cloud.solarwinds.com/~/changes/lGFY3mJPy207GveiFTeX/terraform-and-api-documentation/incident-rate-limiting.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.