ISP: Orange
Country: EU/PL
Server: Odin
Time: 9:55 - 10:05 GMT
Date: 5 March 2018
Trace:
Code:
Tracing route to 195.82.50.9 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms router.asus.com [192.168.0.1]
2 21 ms 21 ms 20 ms wro-bng2.tpnet.pl [80.50.18.74]
3 21 ms 22 ms 21 ms wro-r1.tpnet.pl [80.50.18.73]
4 41 ms 23 ms 23 ms poz-r1.tpnet.pl [194.204.175.205]
5 35 ms 35 ms 35 ms hbg-b1-link.telia.net [213.248.96.144]
6 35 ms 35 ms 35 ms hbg-bb4-link.telia.net [213.155.135.86]
7 44 ms 44 ms 44 ms ffm-bb4-link.telia.net [62.115.138.172]
8 43 ms 43 ms 44 ms ffm-b1-link.telia.net [62.115.116.158]
9 43 ms 42 ms 45 ms kddi-ic-319844-ffm-b1.c.telia.net [62.115.32.106]
10 43 ms 42 ms 42 ms 195.82.61.14
11 42 ms 43 ms 42 ms 195.82.50.234
12 42 ms 42 ms 42 ms 195.82.50.9
Trace complete.
I have also done some pinging around all of the hops, and found out there is a marginal packet loss between hop7 ffm-bb4-link.telia.net [62.115.138.172] and hop8 ffm-b1-link.telia.net [62.115.116.158], which affects the entire connection going through this particular link - at least for me.
Ping statistics for hop7 (there was only one packet with 129 ping):
Code:
Ping statistics for 62.115.138.172:
Packets: Sent = 500, Received = 500, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 43ms, Maximum = 129ms, Average = 43ms
Ping stats for hop8 (multiple high-ping packets here):
Code:
Ping statistics for 62.115.116.158:
Packets: Sent = 500, Received = 499, Lost = 1 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 43ms, Maximum = 133ms, Average = 45ms
Ping stats for hop9:
Code:
Ping statistics for 62.115.32.106:
Packets: Sent = 500, Received = 498, Lost = 2 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 41ms, Maximum = 134ms, Average = 48ms
Ping stats for hop10 195.82.61.14:
Code:
Ping statistics for 195.82.61.14:
Packets: Sent = 500, Received = 496, Lost = 4 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 41ms, Maximum = 67ms, Average = 42ms
For now I'm using VPN set up on private dedicated server located in Amsterdam to deal with this since it goes through different route, and still checking that one for problems.