This is my tracert. Is the same every time with that big spike
Tracing route to 115.69.31.45 over a maximum of 30 hops 1 1 ms <1 ms tracert 115.69.31.45 Tracing route to 115.69.31.45 over a maximum of 30 hops 1 10 ms 3 ms 1 ms 192.168.1.1 2 25 ms 25 ms 25 ms lo0.internet.ivpn.pe24.telstraclear.net [218.101 .61.122] 3 * * * Request timed out. 4 24 ms 26 ms 25 ms ie1-g-0-0-0.telstraclear.net [203.98.50.1] 5 25 ms 25 ms 25 ms ge-0-2-0-1.xcore1.acld.telstraclear.net [203.98. 50.251] 6 26 ms 26 ms 29 ms 210.80.27.5 7 60 ms 32 ms 25 ms 0.xo-1-0-0.XT3.AKL1.ALTER.NET [210.80.35.9] 8 50 ms 49 ms 64 ms 0.so-0-2-2.XT3.SYD2.Alter.Net [210.80.51.81] 9 229 ms 50 ms 70 ms 0.so-3-0-0.GW8.SYD2.ALTER.NET [210.80.33.190] 10 120 ms 85 ms 50 ms vocus-syd-gw.customer.alter.net [203.166.43.34] 11 51 ms 49 ms 63 ms as45425.syd01.nsw.VOCUS.net.au [114.31.193.54] 12 66 ms 66 ms 76 ms xr1.bne.dedicatedservers.net.au [118.127.9.188] 13 69 ms 68 ms 67 ms 118.127.9.35 14 144 ms 158 ms 144 ms pipedc2-bdr1.Brisbane.sonet.net.au [203.23.236.2 25] 15 175 ms 146 ms 149 ms pegasusdc4-bdr2.Brisbane.sonet.net.au [115.69.28 .4] 16 147 ms 144 ms 155 ms 115.69.31.45 Trace complete. C:UsersJason>tracert 115.69.31.45 Tracing route to 115.69.31.45 over a maximum of 30 hops 1 <1 ms <1 ms tracert 115.69.31.45 Tracing route to 115.69.31.45 over a maximum of 30 hops 1 18 ms 4 ms <1 ms 192.168.1.1 2 28 ms 41 ms 51 ms lo0.internet.ivpn.pe24.telstraclear.net [218.101 .61.122] 3 * * * Request timed out. 4 26 ms 27 ms 26 ms ie1-g-0-0-0.telstraclear.net [203.98.50.1] 5 25 ms 34 ms 25 ms ge-0-2-0-1.xcore1.acld.telstraclear.net [203.98. 50.251] 6 26 ms 27 ms 32 ms 210.80.27.5 7 25 ms 26 ms 26 ms 0.xo-1-0-0.XT3.AKL1.ALTER.NET [210.80.35.9] 8 80 ms 49 ms 50 ms 0.so-0-2-2.XT3.SYD2.Alter.Net [210.80.51.81] 9 57 ms 50 ms 55 ms 0.so-3-0-0.GW8.SYD2.ALTER.NET [210.80.33.190] 10 104 ms 55 ms 55 ms vocus-syd-gw.customer.alter.net [203.166.43.34] 11 55 ms 50 ms 50 ms as45425.syd01.nsw.VOCUS.net.au [114.31.193.54] 12 112 ms 70 ms 66 ms xr1.bne.dedicatedservers.net.au [118.127.9.188] 13 69 ms 67 ms 66 ms 118.127.9.35 14 145 ms 151 ms 144 ms pipedc2-bdr1.Brisbane.sonet.net.au [203.23.236.2 25] 15 164 ms 146 ms 151 ms pegasusdc4-bdr2.Brisbane.sonet.net.au [115.69.28 .4] 16 146 ms 146 ms 145 ms 115.69.31.45 Trace complete.
strange, the long hop is from a brisbane server to another brisbane server.
Test.
strange, the long hop is from a brisbane server to another brisbane server.
I don’t even know what that hop 13 is.. No Reverse DNS Lookup shows nothing. I am really quite clueless. Perhaps another sonet server? I have messaged sonet, with the traceroute perhaps they have information from that IP with incoming data on what it is. When I get a reply will post it up.
The issue is a return-path issue.
From the traceroutes being sent to me, this occurs ONLY on TelstraClear links. There is an ongoing issue with AustralianNZ connectivity via Reach (Telstra/TelstraClear) whereby data is often transitted via their US/Asian peering.
Unfortunately, this is out of our control.