How does it look today?
We are working on switching out our HTTP engines to counter this. It's an issue that started to rise a few weeks ago and we honestly have no clue why. It must be an issue that has it's root in external services, because we really haven't change anything to cause this.
We have just switched one of the HTTP engines. We will do more work related to this, as fast as we can.