> For the complete documentation index, see [llms.txt](https://waap.docs.link11.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://waap.docs.link11.com/using-the-product/how-do-i.../set-rate-limits.md).

# Set rate limits and exemptions

Different types of rate limits are defined in different parts of the Link11 WAAP interface.

**Static rate limits for entire sites/applications:** A static rate limiting capability is available via the [Application IP Rate Limits settings](/console-walkthrough/sites/proxy-templates.md#application-ip-rate-limits) within [Proxy Templates](/console-walkthrough/sites/proxy-templates.md). This is simple, IP-based rate limiting that applies globally to every site/application based upon that Proxy Template.

**Granular rate limiting:** More powerful capabilities are available through [Rate Limit Rules](/console-walkthrough/security/rate-limit-rules.md), including variable scope, multiple criteria for tracking requestors, actions, and more. These Rules are then associated with specific locations/URLs through [Security Policies](/console-walkthrough/security/security-policies.md). 

**Global enforcement by traffic source:** Requestors who submit excessive requests across the planet can be banned for configured lengths of time. This can be done via [Dynamic Rules](/console-walkthrough/security/dynamic-rules.md). 

## Creating Rate Limiting Exemptions

To exempt one or more traffic sources from all filtering, follow the instructions here: [Bypass Link11 WAAP for Loadtesting or Other Purposes](/using-the-product/how-do-i.../bypassing-rate-limits-for-loadtesting.md).

To exempt a traffic source from rate limiting only, do the following:

1. Determine a unique tag that will identify the traffic source(s). 
   * There might already be one in use by the system. For example, to exempt an entire ASN, the [system tag](/how-link11-waap-works/tagging.md#system-tags) for that ASN can be used. 
   * If not, then create a [Global Filter](/console-walkthrough/security/global-filters.md) that will assign a unique tag to requests from the traffic source(s) in question.
2. Add the tag to the *Exclude* filter list in the applicable [Rate Limit Rules](/console-walkthrough/security/rate-limit-rules.md) and [Dynamic Rules](/console-walkthrough/security/dynamic-rules.md).