Quote Originally Posted by Jayvenpup View Post
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'
Those Telstra Sydney nodes are not ideal, and although I don't get DC'ed I am still personally seeing packet loss on 202.68.69.101 (that belongs to SE/NTT).

I think we need to keep gathering evidence. The more people who can do a tracert during a failure, or keep an MTR running and post those results (blurring out IPs on the first three steps) will help everyone. It will show patterns that we can hopefully then approach SE with, or Telstra with (which is painful sometimes), or whatever we need to do.

The problem is widespread enough that it's not imagined, and there is preliminary fault-finding to show it's not local to us too.