Tickets - T118706 high latency after PoP break down :: SixXS

Ticket ID: SIXXS #10049918
Ticket Status: User

PoP: dkcph01 - Availo (Copenhagen)

T118706 high latency after PoP break down

Shadow Hawkins on Wednesday, 04 September 2013 11:13:06

After the break down of dkcph01.sixxs.net and subsequent time with connectivity issues to and from the PoP, I have noticed that my latency has increased considerably. For T1198706 is has gone from 6 ms to 12 ms, while T127010 has gone from 45 ms to 60 ms. Ping RTT to e.g. google.com has also increased. A ping6 to www.google.com is now 84 ms, compared to 44 ms for a ping4. Lastly, I have been deducted 2 x 5 ISK's for lack of connectivity - that is hardly fair, given that the PoP was offline. Regards /Uffe Andersen

T118706 high latency after PoP break down

Shadow Hawkins on Thursday, 05 September 2013 06:51:59

I'm struggling to get my ISK back to positive after a year(!) of being disconnected. I agree it's unfair to be credited for downtime when it's the PoP that was down. (My tunnel: T102854).

T118706 high latency after PoP break down

Jeroen Massar SixXS Staff

on Tuesday, 10 September 2013 07:44:25

I agree it's unfair to be credited for downtime when it's the PoP that was down

You have an AYIYA tunnel, as such you never will be deducted credits. If you want to earn credits, you should make your tunnel ping properly. See the FAQ for the details.

T118706 high latency after PoP break down

Jeroen Massar SixXS Staff

on Tuesday, 10 September 2013 07:43:20

For T1198706 is has gone from 6 ms to 12 ms, while T127010 has gone from 45 ms to 60 ms.

I don't think that 6ms and 15ms is 'considerable'. Note that these latencies are between your endpoint and the PoP. A traceroute should elaborate where this change happened if you had a before and after view of it.

A ping6 to www.google.com is now 84 ms, compared to 44 ms for a ping4.

Please note that your IPv6 path incorporates the IPv6 path, as such those 15ms you added in IPv4 also reflect in IPv6. The rest of the latency is then likely added in the IPv6 path, only traceroute(6) can tell though where that happened.

Lastly, I have been deducted 2 x 5 ISK's for lack of connectivity - that is hardly fair, given that the PoP was offline.

When a PoP is offline (thus the website states so, twitter notices etc), credits will not be deducted. Thus unless the PoP was not noticed to be offline your credits where rightly deducted.

Please note Posting is only allowed when you are logged in.