Quote Originally Posted by Shibi View Post
And just in case a SE community rep does read this,

My further testing is also showing 20% packet loss ( timestamp 2022-06-06T22:34:18+1000 ) at the SE/NTT router 202.68.69.101 in addition to the above.

So, it's possible there are two faults at play here. The busy Telstra router in Kent Street which SE can't deal with, but also a problem in the game's datacentre. I also see the 202.68.69.101 packet loss problem from my ABB side, but it's not enough to kick me off on it's own - it does explain the lag spikes though!

Hopefully a community rep reads this and can please pull the strings to have the NTT/SE NOC look at AEST/AWST peak-time packet loss on SE's 202.68.69.101 IP

Thank you SE.
I double checked to see if our issue was 'ken' as well but is more vague but still the same node before and after 'ken'