Here is a question we could not answer well a year ago: what really happens with rate limiting APIs without breaking legitimate integrations? We can answer it now.Observability firstEvery mitigation decision is…
credential stuffing against a online payments platform in Latin America, peaking at 875.2 million requests per second. Mitigated in 0.714 seconds.
SYN flood against a online payments platform in the Middle East, peaking at 382.8 Gbps. Mitigated in 0.643 seconds.
HTTP GET flood against a crypto exchange platform in Southeast Asia, peaking at 369.5 million requests per second. Mitigated in 0.110 seconds.
Slowloris against a news publisher platform in Iberia, peaking at 922.4 million requests per second. Mitigated in 0.351 seconds.
UDP reflection (DNS) against a video streaming platform in Southeast Asia, peaking at 159.6 Gbps. Mitigated in 0.859 seconds.
search endpoint flood against a tax authority portal platform in Central Europe, peaking at 820.4 million requests per second. Mitigated in 0.945 seconds.
UDP reflection (NTP) against a fashion retail platform in Latin America, peaking at 208.2 Gbps. Mitigated in 0.777 seconds.
search endpoint flood against a tax authority portal platform in Latin America, peaking at 919.1 million requests per second. Mitigated in 0.667 seconds.
HTTP/2 rapid reset against a gaming community platform in Latin America, peaking at 948.9 million requests per second. Mitigated in 0.195 seconds.
Slowloris against a online casino platform in North America, peaking at 298.1 million requests per second. Mitigated in 0.257 seconds.
carpet-bombing UDP flood against a tax authority portal platform in Central Europe, peaking at 96.7 Gbps. Mitigated in 0.041 seconds.