Kitz Forum
Internet => General Internet => Topic started by: N0STIE on September 11, 2016, 04:38:32 AM
-
Hi,
I am having an issue with high ping while gaming (about 170ms) to just 1 game hosting that only occurs at late afternoon and early evening (5pm-10pm). Outside these hours everything seems to be normal (About 20-25ms)
All I know is that this particular website (challengeme.gg) uses game servers located in Frankfurt, Germany. It only happens on this servers, it is all good everywhere else.
Example of IP server: 52.59.226.33:27040
-
This is what I get, starting from my own router.
traceroute to 52.59.226.33 (52.59.226.33), 30 hops max, 56 byte packets
1 sent:15 loss:0% last:26.449 ms avg:21.45 ms
firebrick (81.187.147.xxx)
2 sent:15 loss:0% last:40.345 ms avg:66.94 ms
f.gormless.thn.aa.net.uk (90.155.53.56)
3 sent:15 loss:0% last:69.206 ms avg:62.482 ms
g.aimless.thn.aa.net.uk (90.155.53.47)
4 sent:14 loss:0% last:73.005 ms avg:74.967 ms
ge-4-3-6.edge5.London1.Level3.net (195.50.116.49)
5 sent:14 loss:78.6% last:78.687 ms avg:78.289 ms
ae-1-3101.ear1.Frankfurt1.Level3.net (4.69.163.70)
6 sent:14 loss:0% last:54.749 ms avg:77.463 ms
212.162.42.226
7 sent:14 loss:0% last:101.042 ms avg:92.917 ms
54.239.106.102
8 sent:14 loss:0% last:58.397 ms avg:76.324 ms
54.239.106.117
9 sent:14 loss:0% last:79.13 ms avg:77.279 ms
54.239.5.172
10 sent:14 loss:0% last:79.264 ms avg:73.09 ms
ec2-52-59-226-33.eu-central-1.compute.amazonaws.com (52.59.226.33)
-
This is mine when it is fine. I am getting loads of time outs before it gets to the final destination, why is that?
I'll post a tracert later in the evening. Strange, because I wasn't able to ping this IP before.
Tracing route to ec2-52-59-226-33.eu-central-1.compute.amazonaws.com [52.59.226.33]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 * * * Request timed out.
4 6 ms 6 ms 6 ms 31.55.185.216
5 6 ms 6 ms 6 ms core1-hu0-10-0-0.colindale.ukcore.bt.net [195.99.127.130]
6 6 ms 6 ms 6 ms peer6-hu0-7-0-0.telehouse.ukcore.bt.net [62.172.103.15]
7 6 ms 6 ms 6 ms 109.159.253.83
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 22 ms 22 ms 21 ms 176.32.106.249
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 22 ms 22 ms 21 ms 54.239.5.174
17 22 ms 22 ms 22 ms ec2-52-59-226-33.eu-central-1.compute.amazonaws.com [52.59.226.33]
Trace complete.
-
Why do you see timeouts? Perhaps some routers just don't respond to pings, by policy. Or it's packet loss, which seems very unlikely seeing as we can get further out with the traceroute.
-
Tracing route to ec2-52-59-226-33.eu-central-1.compute.amazonaws.com [52.59.226.33]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 * * 6 ms 31.55.185.197
4 6 ms 7 ms 6 ms 31.55.185.216
5 6 ms 7 ms 7 ms core1-hu0-10-0-0.colindale.ukcore.bt.net [195.99.127.130]
6 6 ms 6 ms 7 ms peer6-hu0-7-0-0.telehouse.ukcore.bt.net [62.172.103.15]
7 6 ms 6 ms 6 ms 109.159.253.83
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 22 ms 23 ms 22 ms 176.32.106.247
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 97 ms 101 ms 96 ms 54.239.5.134
17 126 ms 124 ms 122 ms ec2-52-59-226-33.eu-central-1.compute.amazonaws.com [52.59.226.33]
Trace complete.
I don't get it, if the problem is inside their network, why is it only me having this issue?
-
Yes, please do post an early evening traceroute or two.
Could anyone else volunteer to traceroute to that address?
-
mtr is best tool for this but anyway, some tests done below, the french location has small packet loss, rest look fine.
from sky home line
Host Loss% Snt Last Avg Best Wrst StDev
1. router.asus.com 0.0% 486 0.2 0.1 0.1 0.7 0.0
2. 97e7fe4a.skybroadband.com 98.3% 486 26348 25839 25103 26903 580.3
3. be377.pr3.hobir.isp.sky.com 0.0% 486 10.0 10.9 9.6 16.5 0.5
4. ae51.edge6.London1.Level3.net 0.0% 486 10.5 10.7 9.8 49.1 2.8
5. ae-1-3101.ear1.Frankfurt1.Level3.net 82.5% 486 20.1 20.6 19.6 60.8 4.4
6. 212.162.42.226 0.0% 486 19.8 20.3 19.4 64.7 3.1
7. 54.239.106.102 0.0% 486 43.0 36.6 23.3 96.1 8.3
54.239.106.146
8. 54.239.106.117 0.0% 486 23.3 23.3 22.7 28.9 0.4
54.239.106.161
9. 54.239.5.172 0.0% 486 22.7 23.2 22.7 40.3 1.1
54.239.4.216
10. ec2-52-59-226-33.eu-central-1.compute.amazonaws.com 0.0% 486 22.9 23.0 22.6 24.4 0.1
from uk london linode, sorry about the bash overwrite at end the route stretched to last line of terminal.
Host Loss% Snt Last Avg Best Wrst StDev
1. router1-lon.linode.com 0.0% 512 0.8 0.7 0.5 12.1 0.8
2. switch-lonr1.linode.com 0.0% 512 1.7 1.0 0.7 5.7 0.5
3. 194.8.93.2 0.0% 512 1.7 1.5 1.0 7.7 0.5
4. 194.8.92.6 0.0% 512 1.4 1.4 1.2 17.9 1.1
5. 194.8.92.5 34.4% 512 1.0 1.8 0.9 91.4 6.2
6. 195.66.237.175 0.0% 512 2.1 2.1 1.7 25.3 1.9
7. 52.95.61.32 92.6% 512 18.3 20.6 15.1 42.5 4.6
8. 52.95.61.41 80.5% 512 15.0 15.5 14.8 23.0 0.8
52.95.61.53
52.95.61.29
9. 176.32.106.247 0.0% 512 15.1 16.5 14.7 31.0 2.1
176.32.106.249
10. 54.239.107.86 58.6% 512 27.4 29.1 15.1 126.2 10.9
11. 54.239.107.81 58.6% 512 16.2 16.3 15.9 26.3 1.0
12. 54.239.107.168 0.0% 511 26.3 30.8 17.2 346.3 19.2
54.239.107.34
54.239.107.120
54.239.107.8
root@vps1 ~ # .183 0.0% 511 17.1 16.9 16.7 24.0 0.4
from france
Host Loss% Snt Last Avg Best Wrst StDev
1. 163-172-37-1.rev.poneytelecom.eu 51.4% 516 488.2 436.0 318.3 568.2 64.5
2. 195.154.1.240 0.4% 516 2.7 1.9 0.6 5.5 0.5
3. amazon.par.franceix.net 0.0% 516 1.9 2.4 0.9 34.7 2.7
4. 178.236.3.79 0.4% 516 18.8 19.7 17.7 27.4 1.1
5. 178.236.3.74 0.4% 516 18.9 19.9 18.4 24.3 0.7
6. 176.32.106.169 0.6% 516 20.7 19.3 17.7 34.5 1.1
176.32.106.167
7. ???
8. 176.32.106.247 0.4% 516 20.8 19.4 17.8 29.9 1.1
9. ???
10. ???
11. 54.239.107.8 0.4% 515 47.7 46.1 26.2 420.4 39.4
12. 54.239.107.29 1.0% 515 30.0 27.3 25.8 33.4 0.9
13. 54.239.5.134 1.9% 515 25.9 26.9 25.7 35.6 0.8
14. ec2-52-59-226-33.eu-central-1.compute.amazonaws.com 0.6% 515 26.2 26.8 25.6 29.1 0.4
from holland
Host Loss% Snt Last Avg Best Wrst StDev
1. 163-172-212-1.rev.poneytelecom.eu 0.0% 524 0.3 0.3 0.2 2.1 0.1
2. 195.154.2.16 0.0% 524 1.1 1.0 0.6 8.7 0.6
3. bb1-ams1-bb1.dc3.poneytelecom.eu 0.0% 523 14.3 12.9 12.6 17.7 0.4
4. amazon.par.franceix.net 0.0% 523 14.0 14.1 14.0 34.6 1.6
5. 178.236.3.81 0.0% 523 24.5 23.8 22.9 78.0 2.6
6. 178.236.3.76 0.0% 523 24.5 23.1 22.9 28.2 0.5
7. 176.32.106.177 0.0% 523 23.2 23.2 22.9 34.6 1.2
8. ???
9. 176.32.106.247 0.0% 523 24.3 23.3 22.8 34.4 1.2
10. ???
11. ???
12. ???
13. ???
14. 54.239.5.174 1.7% 523 24.1 23.8 23.4 36.1 1.5
15. ec2-52-59-226-33.eu-central-1.compute.amazonaws.com 0.0% 523 23.5 23.4 23.4 24.2 0.0
-
Why do you see timeouts?
This can happen if the modem is set to block ICMP Echo request or the target server also blocks ICMP requests
-
Can I just ask briefly what ISP you are on? Not been mentioned as of yet, so I am just wondering. Looking at your tracerts I would say BT but that could be BTW, not BTr.
My traceroute:
Traceroute to 52.59.226.33, 20 hops max, 38 byte packets
1 losubs.subs.bng1.th-lon.zen.net.uk (62.3.80.17) 16.025 ms 16.181 ms 16.493 ms
2 ae1-177.cr2.th-lon.zen.net.uk (62.3.80.38) 16.430 ms 16.181 ms 16.493 ms
3 amazon-gw-a.lonap.net (5.57.80.8) 16.431 ms 17.336 ms 18.867 ms
4 * 54.239.101.150 (54.239.101.150) 40.858 ms 37.609 ms
5 * * *
6 54.239.42.160 (54.239.42.160) 31.643 ms 30.674 ms 29.644 ms
7 176.32.106.247 (176.32.106.247) 30.894 ms 30.643 ms 29.706 ms
8 54.239.107.20 (54.239.107.20) 46.418 ms 42.201 ms 42.795 ms
9 54.239.107.13 (54.239.107.13) 29.707 ms 30.643 ms 30.862 ms
10 54.239.107.122 (54.239.107.122) 43.982 ms 52.072 ms 47.574 ms
11 54.239.107.139 (54.239.107.139) 30.924 ms 30.675 ms 30.831 ms
12 54.239.5.134 (54.239.5.134) 30.924 ms 30.675 ms 34.454 ms
13 ec2-52-59-226-33.eu-central-1.compute.amazonaws.com (52.59.226.33) 29.738 ms 30.706 ms 29.644 ms
Trace complete.
Traceroute from OVH Rouxbais datacentre (France):
traceroute to 52.59.226.33 (52.59.226.33), 30 hops max, 60 byte packets
1 rbx1-3a-a9.fr.eu (91.121.86.252) 1.082 ms 1.051 ms 1.041 ms
2 be11-149.rbx-g1-a9.fr.eu (37.187.231.65) 0.995 ms be11-149.rbx-g2-a9.fr.eu (37.187.231.67) 1.326 ms 1.324 ms
3 be100-1187.ldn-1-a9.uk.eu (91.121.128.87) 4.280 ms be100-1188.ldn-5-a9.uk.eu (91.121.128.89) 4.627 ms 4.624 ms
4 195.66.225.175 (195.66.225.175) 4.230 ms 4.229 ms 195.66.237.175 (195.66.237.175) 4.849 ms
5 * * *
6 * * *
7 176.32.106.247 (176.32.106.247) 16.845 ms 16.858 ms *
8 * * *
9 * * *
10 * * *
11 * * *
12 54.239.5.172 (54.239.5.172) 15.608 ms 15.582 ms 54.239.4.216 (54.239.4.216) 14.458 ms
-
Can I just ask briefly what ISP you are on? Not been mentioned as of yet, so I am just wondering. Looking at your tracerts I would say BT but that could be BTW, not BTr.
BT