Kansas City, to Japan, to Central WoW Server...?

Support Technical Support
1

So I ran WinMTR and and a few trace routes and noticed a strange thing after some bad pings/packet loss/disconnects… I am routing through a server in Japan to the Central WoW server 24.105.62.129 (US Central)

|------------------------------------------------------------------------------------------|
| WinMTR statistics |

Host - % Sent Recv Best Avrg Wrst Last
router.asus - 0 14 14 0 0 0 0
No response from host - 100 2 0 0 0 0 0
64-126-3-37.static.everestkc - 0 14 14 7 9 13 13
ibr33-te-0-2-0.mci.surewest - 0 14 14 7 9 12 12
ae-28.a01.chcgil09.us.bb.gin.ntt - 0 14 14 26 28 36 30
ae-9.r08.chcgil09.us.bb.gin.ntt - 0 14 14 159 162 171 162
ae-0.r20.chcgil09.us.bb.gin.ntt - 0 14 14 27 28 31 27
ae-7.r23.sttlwa01.us.bb.gin.ntt - 0 9 9 72 73 76 72
ae-0.r22.sttlwa01.us.bb.gin.ntt. - 0 14 14 71 73 77 77
ae-13.r30.tokyjp05.jp.bb.gin.ntt. - 0 14 14 159 162 184 184
ae-2.r00.tokyjp08.jp.bb.gin.ntt. - 0 14 14 164 166 177 168
ae-1.a00.tokyjp03.jp.bb.gin.ntt. - 0 14 14 161 165 179 167
61.213.179.114 - 0 14 14 159 166 230 159
et-0-0-48-br01-eqty2.blizzardonline - 0 14 14 165 170 198 198
xe-0-0-0-1-br01-eqla1.as57976- 0 13 13 166 234 639 639
et-0-0-2-br01-swlv10.as57976- 0 14 14 164 175 224 164
137.221.65.133 - 0 14 14 165 166 169 165
be1-pe01-eqch2.as57976 - 0 14 14 165 169 190 190
24.105.62.129 - 0 14 14 166 167 170 167
________________________________________________ ______ ______ ______ ______ ______ ______

WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
(edit: I’ve clipped out all of the .net’s as they were being recognized as hyperlinks)
so as you can see, I have 3 Tokyip bounces, which I’ve confirmed are definitely in Japan.

Any idea why I’d have such a strange path? what the heck can I do??

2

You are not the only one, ive been arguing all afternoon with the Blizz support on twitter and they dont believe me.

3

how can they argue with WinMTR reports??

4

It is unlikely this is actually in Japan. from Seattle to Tokyo the ping is around 120 one way major node to major node. There and back would add 240+ ms. you averages are to low to actually be going to Japan. Your averages to the server is only 169 ms. To go to japan and back to the US would add 9,562‬ ,miles to the trip

5

See? this is what ive been dealing in twitter

1 Like
6

It can not be going to Japan because of the amount of distance and ping it would add to the winMTR. If it was going to japan the ping jump total would be a lot higher then WINmtr is reporting

7

Ok I agree its unlikely its going to Japan, but why would WinMTR be showing that?

Is this an ISP issue? or a blizzard issue?

8

Looks like NTT moved the Nodes from Japan to the US without changing the nodes names.

Looks like NTT is having a issue between these two nodes.

ae-0.r22.sttlwa01.us.bb.gin.ntt. - 0 14 14 71 73 77 77
ae-13.r30.tokyjp05.jp.bb.gin.ntt. - 0 14 14 159 162 184 184

Normally your ISP would have to open a ticket with their peering partner NTT.

9

well, disconnects strike again. apparently I’ll be on the phone with my ISP again tomorrow?

10

Looks like my ISP uses NTT too, im having the same issue and im from South America.
10 162 ms 173 ms 162 ms ae-8.r24.nycmny01.us.bb.gin.ntt. net [129.250.2.12]
11 203 ms * 205 ms ae-4.r22.sttlwa01.us.bb.gin.ntt. net [129.250.4.13]
12 289 ms 288 ms 290 ms ae-13.r30.tokyjp05.jp.bb.gin.ntt. net [129.250.4.143]
13 294 ms 289 ms 289 ms ae-2.r00.tokyjp08.jp.bb.gin.ntt. net [129.250.6.127]
14 306 ms 289 ms 289 ms ae-1.a00.tokyjp03.jp.bb.gin.ntt. net [129.250.5.51]

11

Looks like a Issue between NTT nodes. It is acting like NTT did not change the initial routing it is routing to Washington state then back to the servers

12

well, then im screwed cause my ISP customer support sucks. I hope someone else can do something. Maybe Blizz

13

well it’s gotten really bad tonight, constant disconnects :rage:

14

Mind if i add you there is something i want to ask.

15

is this the same problem the oceanic players have been experiencing with lag and disconnects since the launch of BFA?

Because that would be really discouraging, I just got back into the game, I’d rather not have some technical bs drive me away again!

16

Alright, so MTR and in game is generally showing me at 170 ping today, but I’ve had disconnects and severe lag on abilities/actions.

Is there anything I can do besides get a new ISP? I don’t even have anything to show them, they can’t do anything with an MTR report that says I’ve got a 170 ping to my destination.

17

Do a WinMTR to a dota2 server and you will see that it is not your problem, i bet it wont go trough than NTT node that we are having problems.

18

Looks like I’m still going through NTT, but pings are about 100 lower than the central WoW server

|------------------------------------------------------------------------------------------|
| WinMTR statistics |

Host - % Sent Recv Best Avrg Wrst Last
router.asus.c - 4 32 31 3 3 7 3
No response from host - 100 7 0 0 0 0 0
64-126-3-37.static.everestkc.n - 0 35 35 10 15 62 13
ibr33-te-0-2-0.mci.surewest.c - 0 35 35 11 14 38 11
ae-28.a01.chcgil09.us.bb.gin.ntt.n - 0 35 35 28 32 66 29
ae-9.r08.chcgil09.us.bb.gin.ntt.n - 0 35 35 28 32 66 30
ae-0.telia.chcgil09.us.bb.gin.ntt.n - 0 35 35 27 33 59 45
nyk-bb4-link.telia.n - 0 35 35 47 51 75 51
ash-bb4-link.telia.n - 0 35 35 46 50 66 50
rest-b1-link.telia.n - 0 35 35 49 53 72 54
valve-ic-333077-ash-b1.c.telia.n - 0 35 35 48 51 77 51
164-78-208-1.valve.n - 0 35 35 53 91 413 53
________________________________________________ ______ ______ ______ ______ ______ ______

WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

19

And of course I’m playing right now and its totally fine, no lag, no disconnects, I’m even on my wifi instead of a wired connection… but tonight it will probably run like garbage again, ugh

20

But it’s not going through the same node, i. The Blizzard test goes from Seattle to JPN, i. The dota2 test it doesnt