Cloud node response time bug?

[ruuskil]

Hi,

When the packet engine starts, I usually get around 20-30ms response time to cloud node. However when the packet engine has been running for a few days, the response time doubles at some point and newer returns back to normal until the packet engine is restarted. I'm using Europe and Europe2 nodes.

This is not new behavior in my installation. I remember seeing this already long time ago but I hadn't had time to raise a question about it. Anyone else experiencing this?

[sy]

Hi,

Can you share the ping time for the following IP addresses while Zenarmor Engine is stopped?

Europe: 35.198.172.108
Europe2: 34.65.117.157

[ruuskil]

Engine stopped:

Ping statistics for 35.198.172.108:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 52ms, Maximum = 52ms, Average = 52ms

Ping statistics for 34.65.117.157:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 55ms, Maximum = 59ms, Average = 56ms

When the engine is running I get similar pings, which I assume is how it should be.

Now I noticed that the Zenarmor status page reports ping times of ~25ms even when the ping time from the firewall CLI is 50+ ms.