HardStuckGold [#5]
Tracing route to sydney.com [54.252.93.212]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 192.168.68.1
2 2 ms 1 ms 1 ms ultrahub.hub [192.168.1.1]
3 6 ms 4 ms 5 ms 121-74-195-254.telstraclear.net [121.74.195.254]
4 8 ms 5 ms 5 ms 99.83.67.247
5 5 ms 5 ms 4 ms 99.83.67.246
6 6 ms 4 ms 5 ms 150.222.119.46
7 13 ms 5 ms 5 ms 150.222.119.31
8 Request timed out.
9 35 ms 36 ms 36 ms 52.95.36.38
10 35 ms 37 ms 40 ms 150.222.112.179
11 37 ms 50 ms 36 ms 150.222.112.182
12 35 ms 41 ms 36 ms 52.95.39.54
13 35 ms 35 ms 38 ms 52.95.39.33
14 Request timed out.
15 Request timed out.
16 Request timed out.
17 34 ms 36 ms 33 ms ec2-54-252-93-212.ap-southeast-2.compute.amazonaws.com [54.252.93.212]
ok, well what i can tell you is it is definetly something you have to contact your isp about. whether their support will know what your talking about, let alone do anything about it, i dont know. it doesnt look like its anything in your control as it is 5 hops from router. i have these same type of issues, and they just keep sending me back to my local isp who send me to the upper isp