Hi, Romey, has information I passed on through support helped?
It looked from logs like the site’s throughput was backlogged and periodically rate-limited due to volume / slow performance on a webhook’s response time. I.e. too many requests for the response time of the webhook, so if you identify the webhook and either filter it more tightly or improve its response time, that would reduce throttling and increase throughput.
However, consumption by all webhooks for the site is combined when considering rate limiting, so it is also possible that it is not a single webhook responsible, but an overall increase in volume to all webhoks. (But I think when optimizing there are usually bigger targets that stand out. I would expect one or two webhooks to be consuming significantly more.)
We do have work planned to improve visibility of performance bottlenecks in the webhooks UI, and also provide throttling warnings, but that is still a little bit down in our queue.