# Incident Rate Limiting

Squadcast has the following Incident Rate Limits for trigger calls 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>](/services/alert-suppression.md) incidents and [<mark style="color:blue;">Duplicate</mark>](/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 be counted towards rate limits. It has multiple layers to it, as listed below:

* **Resolve API (Webhook) Rate Limits:** Rate limits for resolve requests now mirror the existing limits for trigger requests.
* **Batch Resolution Cap:** A single resolve API (Webhook) request is now limited to a maximum of the latest 100 incidents.
* **Plan-Based Time Filters:** A time-range filter tied to the organization's data retention plan. For example, if you are in the Pro plan, the data retention period of 3 months will be the boundary.
  {% 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>](/services/alert-suppression.md#discarding-suppressed-incidents) function to avoid hitting the [<mark style="color:blue;">**Incident Rate Limits**</mark>](/terraform-and-api-documentation/incident-rate-limiting.md) as Suppressed events that are discarded don’t get counted against the allowed Incident Rate Limits.

*Have any questions?* [*Ask the community*](https://community.squadcast.com/view/home)*.*


---

# Agent Instructions: 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:

```
GET https://support.squadcast.com/terraform-and-api-documentation/incident-rate-limiting.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.