Hi everyone,
I posted my question on the gitter Mashape Kong channel before I realise it was written “Channel deprecated”.
Please allow me to copy/paste my original message below.
Hi, I’m Ramzi and we’ve been using Kong happily for almost 2 years.
We’ve been having some latency issues recently.
We use Kong to protect access to several APIs. We have several Kong instances on 3 different geographical sites (A, B, C) to ensure availability and resiliency. The APIs are also hosted on 2 different geographical sites (A, B).
Traffic between the 3 Kong sites is load balanced by a GTM (Global Traffic Manager). Upstream requests are also load balanced by a GTM between API sites.
It works pretty well except we experience kong latency on one Kong site. Let’s say on sites A and B everything is fine (10 ms max) but on C kong latency goes up to 200 ms.
This does not seem related to one specific API. When the latency is high, it is for any API. So I don’t think it is caused by the upstream servers.
And on site C, the Kong instances show a lot of ‘upstream prematurely closed connection while reading response header from upstream’ error messages.
I suspect a network problem. But I was wondering why it has such an impact on the kong latency.
Oh and one last thing. The APIs reply pretty fast. No timeout issue I guess.
Any hint about a test or any step I could take to diagnose my problem would be very much appreciated.
Ramzi