To ensure quick and responsive reporting experience we may use throttling in case of exceptionally high-traffic events.

How does it work?

Throttling starts when the number of events for a specific policy exceeds the threshold of 70,000 requests per second for over 10 consecutive minutes.
It stops when the rate falls below the threshold for 30 consecutive minutes.

While throttling is active, we store a reduced volume of security events at a rate of 20,000 requests per second. With this data you can still adequately analyze the attack parameters to understand how it happened and better prepare to counteract future threats.


The security protections you set are not affected by throttling and operate normally. This feature applies only to security reporting.