I think this is why they use 23:59 for alert level changes; no ambiguity there! Anyway I'm off to bed now. Thanks for your help with this 🙂

VygrNetworkMonkey:

 

Heya @Behodar,

 

Midnight is the start of a day - ie: 00:00 Friday the 3rd. Friday ends at 23:59.

 

I may need to amend that date, as the more information I receive, seems to indicate it's a doozie of a cut..... 

 

Could you guys inform your helpdesk? As of 8:30pm they had no idea of this. 

surfisup1000:

 

Could you guys inform your helpdesk? As of 8:30pm they had no idea of this. 

 

Thanks @surfisup1000, they have been updated :)

Things appear to be back to normal :)

PING 1.1.1.1 (1.1.1.1): 56 data bytes
64 bytes from 1.1.1.1: icmp_seq=0 ttl=59 time=9.237 ms
64 bytes from 1.1.1.1: icmp_seq=1 ttl=59 time=9.458 ms
64 bytes from 1.1.1.1: icmp_seq=2 ttl=59 time=9.540 ms
64 bytes from 1.1.1.1: icmp_seq=3 ttl=59 time=9.273 ms

Behodar:

I've been with Voyager for ~18 months. These sorts of issues are rare :)

Yeah, it's great! Especially when you just create an "is it just me" thread, which then leads to a fix without having to 'officially' log anything at all.

Good morning everyone, 

The latency and loss receded approx 10pm last night, due to a reduction in traffic levels in the area. (Note: It's not just Voyager impacted).

We are still waiting for (and chasing up) a confirmation on a resolution - when it comes through I'll update.