Last edited:
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
Sop cast via wiziwig
Keep the data coming in for Diablo, please. The more we have to work with the better. Seems there is nothing wrong with our international link, but rather a possible routing issue resulting in slightly higher latency in Europe somewhere. What I can say is that we talk to the telia.net network perfectly, and in our tests this part of the Diablo link is often responsible for packet loss, but we'll keep investigating...
Tracing route to 213-155-155-233.customer.teliacarrier.com [213.155.155.233]
over a maximum of 30 hops:
0 jadex64 [192.168.0.6]
1 192.168.0.1
2 105.233.14.1
3 telkom-gw-ipc-up.jhbcore.net [196.6.121.198]
4 pk002-jhb-gi-v611.borwood.net [217.78.80.225]
5 th003-lon-po-wacs.borwood.net [217.78.80.237]
6 th102-lon-vl-prcera2.borwood.net [217.78.88.26]
7 gi-0-3-0-1-63.r02.londen03.uk.bb.gin.ntt.net [213.130.48.1]
8 ae-4.r23.londen03.uk.bb.gin.ntt.net [129.250.5.40]
9 ae-3.r22.amstnl02.nl.bb.gin.ntt.net [129.250.5.198]
10 ae-1.r02.amstnl02.nl.bb.gin.ntt.net [129.250.2.113]
11 ae-0.teliasonera.amstnl02.nl.bb.gin.ntt.net [129.250.8.66]
12 * * *
Computing statistics for 275 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 jadex64 [192.168.0.6]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.0.1
0/ 100 = 0% |
2 8ms 0/ 100 = 0% 0/ 100 = 0% 105.233.14.1
0/ 100 = 0% |
3 8ms 0/ 100 = 0% 0/ 100 = 0% telkom-gw-ipc-up.jhbcore.net [196.6.121.198]
0/ 100 = 0% |
4 8ms 0/ 100 = 0% 0/ 100 = 0% pk002-jhb-gi-v611.borwood.net [217.78.80.225]
0/ 100 = 0% |
5 174ms 0/ 100 = 0% 0/ 100 = 0% th003-lon-po-wacs.borwood.net [217.78.80.237]
0/ 100 = 0% |
6 181ms 0/ 100 = 0% 0/ 100 = 0% th102-lon-vl-prcera2.borwood.net [217.78.88.26]
0/ 100 = 0% |
7 188ms 0/ 100 = 0% 0/ 100 = 0% gi-0-3-0-1-63.r02.londen03.uk.bb.gin.ntt.net [213.130.48.1]
0/ 100 = 0% |
8 185ms 0/ 100 = 0% 0/ 100 = 0% ae-4.r23.londen03.uk.bb.gin.ntt.net [129.250.5.40]
0/ 100 = 0% |
9 192ms 0/ 100 = 0% 0/ 100 = 0% ae-3.r22.amstnl02.nl.bb.gin.ntt.net [129.250.5.198]
0/ 100 = 0% |
10 197ms 0/ 100 = 0% 0/ 100 = 0% ae-1.r02.amstnl02.nl.bb.gin.ntt.net [129.250.2.113]
0/ 100 = 0% |
11 195ms 0/ 100 = 0% 0/ 100 = 0% ae-0.teliasonera.amstnl02.nl.bb.gin.ntt.net [129.250.8.66]
Trace complete.
Tracing route to 80-239-210-246.customer.teliacarrier.com [80.239.210.246]
over a maximum of 30 hops:
0 jadex64 [192.168.0.6]
1 192.168.0.1
2 105.233.14.1
3 telkom-gw-ipc-up.jhbcore.net [196.6.121.198]
4 pk002-jhb-gi-v611.borwood.net [217.78.80.225]
5 th003-lon-po-wacs.borwood.net [217.78.80.237]
6 th102-lon-vl-prcera2.borwood.net [217.78.88.26]
7 gi-0-3-0-1-63.r02.londen03.uk.bb.gin.ntt.net [213.130.48.1]
8 ldn-b5-link.telia.net [213.248.100.49]
9 ldn-bb1-link.telia.net [80.91.248.217]
10 adm-bb3-link.telia.net [213.155.136.99]
11 adm-b4-link.telia.net [213.155.137.213]
12 * * *
Computing statistics for 275 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 jadex64 [192.168.0.6]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.0.1
0/ 100 = 0% |
2 8ms 0/ 100 = 0% 0/ 100 = 0% 105.233.14.1
0/ 100 = 0% |
3 8ms 0/ 100 = 0% 0/ 100 = 0% telkom-gw-ipc-up.jhbcore.net [196.6.121.198]
0/ 100 = 0% |
4 8ms 0/ 100 = 0% 0/ 100 = 0% pk002-jhb-gi-v611.borwood.net [217.78.80.225]
0/ 100 = 0% |
5 174ms 0/ 100 = 0% 0/ 100 = 0% th003-lon-po-wacs.borwood.net [217.78.80.237]
0/ 100 = 0% |
6 183ms 0/ 100 = 0% 0/ 100 = 0% th102-lon-vl-prcera2.borwood.net [217.78.88.26]
0/ 100 = 0% |
7 188ms 0/ 100 = 0% 0/ 100 = 0% gi-0-3-0-1-63.r02.londen03.uk.bb.gin.ntt.net [213.130.48.1]
0/ 100 = 0% |
8 191ms 0/ 100 = 0% 0/ 100 = 0% ldn-b5-link.telia.net [213.248.100.49]
0/ 100 = 0% |
9 193ms 0/ 100 = 0% 0/ 100 = 0% ldn-bb1-link.telia.net [80.91.248.217]
0/ 100 = 0% |
10 --- 100/ 100 =100% 100/ 100 =100% adm-bb3-link.telia.net [213.155.136.99]
0/ 100 = 0% |
11 188ms 0/ 100 = 0% 0/ 100 = 0% adm-b4-link.telia.net [213.155.137.213]
Trace complete.
Yup, our communication with telia.net is perfect, so there is something odd happening on their end by the looks of things. We will mail them to find out, but there's zero control that we can have over that if it is the problem. We will put pressure on the relevant organisations should we definitively identify any issues, that's for sure...
Thanks! For all we know Blizzard upgraded us with latency knowing them...
Thanks! For all we know Blizzard upgraded us with latency knowing them...
If these issues are specific to your Crystal Web account then we'll take ownership of the issue and not pass the buck. We'll work on identifying and resolving the underlying issue...
We really want to have a happy gaming community...
Both iPad and android devices have issues accessing the iStore and Google Play store respectively...
What information do you guys need from me?
Well done CW.
Not revealing to much, but this is the fundamental int. Nodes:Hops
wacs_borwood_net: borwood_net : ntt_net : telia_net
CW got this right - At last a proper route to US/CA as well.
Stable/solid and consistent although the eu game-servers might be busy as its weekend, BUT still sub 200ms pings.
Well done guys!
@Crystal Web have you guys tested this with Sky Go yet? Thinking about getting it but I know in the past its buffered a hell of a lot on MTN based networks