@Jose Ramon Roca Garcia @Ventura Morcillo Valle @Bastien Noel @GH FARRELL Lisalee T (Tunde) FARRELL Lisalee T (Tunde) Catalao, Pablo badtiming
Thank you for reaching out. Posting this as an answer for visibility.
I have update from the product team that the underlying issue has been resolved and they will share a Root Cause Analysis soon. I will update this answer as soon as we receive the RCA.
Please tag me in your response if you are still facing this issue.
[Update 10/11]
We received the Root Cause Analysis for this issue from the Product Group:
In light of discovery of the new Rapid Reset Http2 attack , rate limiting was introduced to thwart such attacks. Platform team was in process of releasing the protection for http2 vulnerability ,We initially rolled out a rate limiting strategy which caused a genuine customer traffic to be throttled and resulted in too aggressive behavior. Rate limiting strategy was tweaked over a period of time, which is now stable
and thus reducing the false positive. This rate limiting was introduced in context of https://msrc.microsoft.com/blog/2023/10/microsoft-response-to-distributed-denial-of-service-ddos-attacks-against-http/2/
Thank you!
Regards,
Chaitanya
@Jose Ramon Roca Garcia It will help if you could mark this as answered as it will be easier for the community members to understand the resolution for this issue.