On our end we had deployed some rules to mitigate large amounts of high bandwidth traffic from individual customers (targeting abuse of the platform, e.g. streaming video) which we have been confident in for quite some time now, but we had forgotten a condition to only include certain requests with responses in our analysis of traffic that were above a certain size in a recent change. This caused the system to look at more than the target abuse and some mitigation spilled over to your site. This has now been fixed with some adjustments to the system.

On our end we had deployed some rules to mitigate large amounts of high bandwidth traffic from individual customers (targeting abuse of the platform, e.g. streaming video) which we have been confident in for quite some time now, but we had forgotten a condition to only include certain requests with responses in our analysis of traffic that were above a certain size in a recent change. This caused the system to look at more than the target abuse and some mitigation spilled over to your site. This has now been fixed with some adjustments to the system.