Hey all,
Does this happen only when connecting cross realm, or does it happen on local servers as well? Would it be possible to run an MTR to the local servers as well?
Results to OCE servers, no ping problems at all to OCE servers for me.
WinMTR statistics
| Host | % | Sent | Recv | Best | Avrg | Wrst | Last |
| be10-3999.core1.vdc01.syd.aussiebb.net | 0 | 601 | 601 | 0 | 2 | 475 | 2 |
| be10-3999.core1.vdc01.syd.aussiebb.net | 0 | 600 | 600 | 13 | 18 | 378 | 16 |
| be10-3999.core1.vdc01.syd.aussiebb.net | 100 | 600 | 1 | 277 | 277 | 277 | 277 |
| be10-3999.core1.vdc01.syd.aussiebb.net | 0 | 600 | 600 | 13 | 18 | 177 | 16 |
| be10-3999.core1.vdc01.syd.aussiebb.net | 0 | 600 | 600 | 14 | 19 | 76 | 18 |
| Network Unreachable | 1 | 600 | 599 | 14 | 22 | 106 | 42 |
| et-0-0-48-br01-eqsy4.as57976.net | 0 | 600 | 600 | 14 | 24 | 148 | 18 |
| et-0-0-0-pe02-eqsy4.as57976.net | 0 | 600 | 600 | 14 | 20 | 81 | 15 |
| 103.4.115.248 | 0 | 600 | 600 | 14 | 18 | 37 | 16 |
Fíz,
It looks like some of the information is missing, potentially, and there are about 5 hops with an identical name, muddying the test. Did you cut any information from the test? If so, can you re run it and post all of the information? (The first lines are not your external IP address, it’s just a router IP, so it’s safe to post here.)
If you did not modify the test before uploading it, can you try a traceroute instead and reply with that?
Nothing was cut or replaced with that winMTR test, that was the results it gave me. Here is a traceroute to the same IP address:
Tracing route to 103.4.115.248 over a maximum of 30 hops
1 1 ms 1 ms <1 ms 192.168.1.1
2 14 ms 14 ms 14 ms 100.92.0.1
3 * * * Request timed out.
4 14 ms 14 ms 14 ms 180.150.2.95
5 15 ms 14 ms 19 ms be10-3999.core1.vdc01.syd.aussiebb .net [180.150.2.88]
6 24 ms 18 ms 21 ms as55497.nsw.ix.asn.au [218.100.52.65]
7 35 ms 15 ms 16 ms et-0-0-48-br01-eqsy4.as57976 .net [137.221.85.33]
8 15 ms 16 ms 14 ms et-0-0-0-pe02-eqsy4.as57976 .net [137.221.85.69]
9 14 ms 14 ms 14 ms 103.4.115.248
Trace complete.
(spaces were added before the ‘.net’ as to not qualify as hyperlinks in the post, letting me reply)
Hey again Fíz,
Those look like they go to the Oceanic servers and it seems like you mentioned that connection was fine? The test certainly looks fine. You’re not having problems connecting to that server, right? If so, can you please post another test to the server you are having problems with? (Looks like 24.105.62.129?)
Yes connection to OCE is fine as I said earlier, you asked for the OCE tests, haha.
Here is to US Central servers:
Tracing route to 24.105.62.129 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.1.1
2 14 ms 14 ms 14 ms 100.92.0.1
3 * * * Request timed out.
4 15 ms 15 ms 15 ms 180.150.2.95
5 16 ms 14 ms 16 ms be10-3999.core1.vdc01.syd.aussiebb .net [180.150.2.88]
6 108 ms 108 ms 108 ms HundredGigE0-0-0-16.core1.vdc03.mel.aussiebb .net [202.142.143.83]
7 108 ms 109 ms 109 ms be1.core2.vdc03.mel.aussiebb .net [180.150.0.197]
8 * 108 ms 109 ms be2.core2.ia-dcb.portmel.aussiebb .net [202.142.143.216]
9 108 ms 107 ms 108 ms be1.core1.ia-dcb.portmel.aussiebb .net [202.142.143.40]
10 109 ms 109 ms 115 ms HundredGigE0-0-0-8.core1.vdc01.per.aussiebb .net [180.150.0.145]
11 109 ms 109 ms 107 ms be1.core2.vdc01.per.aussiebb .net [202.142.143.207]
12 110 ms 108 ms 108 ms be2.core2.nextdc-p1.per.aussiebb .net [202.142.143.205]
13 131 ms 149 ms 140 ms be3.core1.sg1-equinix.sin.aussiebb .net [180.150.2.85]
14 108 ms 107 ms 109 ms be1.core2.sg1-equinix.sin.aussiebb .net [180.150.2.87]
15 108 ms 107 ms 107 ms xe-0-0-20-2.a00.sngpsi07.sg.bb.gin.ntt .net [116.51.26.237]
16 142 ms 145 ms 108 ms ae-4.r00.sngpsi07.sg.bb.gin.ntt .net [129.250.2.75]
17 125 ms 109 ms 108 ms ae-1.r21.sngpsi07.sg.bb.gin.ntt .net [129.250.3.91]
18 176 ms 175 ms 185 ms ae-17.r31.tokyjp05.jp.bb.gin.ntt .net [129.250.2.243]
19 175 ms 175 ms 174 ms ae-3.r01.tokyjp08.jp.bb.gin.ntt .net [129.250.6.133]
20 176 ms 177 ms 175 ms ae-2.a00.tokyjp03.jp.bb.gin.ntt .net [129.250.5.55]
21 178 ms 178 ms 179 ms 61.213.179.114
22 260 ms 308 ms 260 ms et-0-0-48-br01-eqty2.blizzardonline .net [137.221.81.33]
23 258 ms 258 ms 258 ms xe-0-0-0-1-br01-eqla1.as57976 .net [137.221.65.56]
24 268 ms 259 ms 258 ms et-0-0-2-br01-swlv10.as57976 .net [137.221.65.69]
25 273 ms 273 ms 273 ms 137.221.65.133
26 259 ms 259 ms 259 ms be1-pe01-eqch2.as57976 .net [137.221.69.67]
27 259 ms 260 ms 260 ms 24.105.62.129
Trace complete.
I was having spikes on top of the extra latency I had today, ran another traceroute and the first Blizzard hop had a higher ping, is there any progress on this route?
Tracing route to 24.105.62.129 over a maximum of 30 hops
1 1 ms 1 ms 1 ms 192.168.1.1
2 15 ms 17 ms 15 ms 100.92.0.1
3 * * * Request timed out.
4 14 ms 16 ms 16 ms 180.150.2.95
5 50 ms 97 ms 23 ms be10-3999.core1.vdc01.syd.aussiebb .net [180.150.2.88]
6 108 ms 109 ms 109 ms HundredGigE0-0-0-16.core1.vdc03.mel.aussiebb .net [202.142.143.83]
7 109 ms 108 ms 110 ms be1.core2.vdc03.mel.aussiebb .net [180.150.0.197]
8 109 ms 110 ms 108 ms be2.core2.ia-dcb.portmel.aussiebb .net [202.142.143.216]
9 132 ms 114 ms 108 ms be1.core1.ia-dcb.portmel.aussiebb .net [202.142.143.40]
10 109 ms 108 ms 110 ms HundredGigE0-0-0-8.core1.vdc01.per.aussiebb .net [180.150.0.145]
11 108 ms 109 ms 108 ms be1.core2.vdc01.per.aussiebb .net [202.142.143.207]
12 108 ms 108 ms 109 ms be2.core2.nextdc-p1.per.aussiebb .net [202.142.143.205]
13 133 ms 109 ms 108 ms be3.core1.sg1-equinix.sin.aussiebb .net [180.150.2.85]
14 109 ms 109 ms 110 ms be1.core2.sg1-equinix.sin.aussiebb .net [180.150.2.87]
15 108 ms 115 ms 110 ms xe-0-0-20-2.a00.sngpsi07.sg.bb.gin.ntt .net [116.51.26.237]
16 109 ms 108 ms 108 ms ae-4.r00.sngpsi07.sg.bb.gin.ntt .net [129.250.2.75]
17 165 ms 108 ms 109 ms ae-1.r21.sngpsi07.sg.bb.gin.ntt .net [129.250.3.91]
18 196 ms 175 ms 178 ms ae-17.r31.tokyjp05.jp.bb.gin.ntt .net [129.250.2.243]
19 178 ms 179 ms 179 ms ae-3.r01.tokyjp08.jp.bb.gin.ntt .net [129.250.6.133]
20 180 ms 182 ms 179 ms ae-2.a00.tokyjp03.jp.bb.gin.ntt .net [129.250.5.55]
21 179 ms 179 ms 178 ms 61.213.179.114
22 260 ms 260 ms 353 ms et-0-0-48-br01-eqty2.blizzardonline .net [137.221.81.33]
23 260 ms 260 ms 347 ms xe-0-0-0-1-br01-eqla1.as57976 .net [137.221.65.56]
24 366 ms 259 ms 260 ms et-0-0-2-br01-swlv10.as57976 .net [137.221.65.69]
25 278 ms 302 ms 273 ms 137.221.65.133
26 259 ms 290 ms 259 ms be1-pe01-eqch2.as57976 .net [137.221.69.67]
27 262 ms 260 ms 261 ms 24.105.62.129
Trace complete.
Hey there,
To be clear, there is a jump from 180-260 when the signal crosses the ocean. This is normal and unavoidable due to the physical distance through an undersea cable the signal must travel through.
The root of our problem here is that the latency is 180+ before it reaches Japan which is where the journey across the ocean begins. This is indicated by the following:
My best advice would be to contact your ISP and ask for a Tier 3 agent who is able to work with their network engineers on routing issues. They may be able to root out the problem and resolve it.
Be sure to focus on the problem routing before the jump across the ocean which is unavoidable.
I do sincerely hope this information helps.