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

Support Technical Support
21

I see some of the same issues I’m having (made a new thread about it) and see the same “tokyojp” jumps you guys are showing. Hoping there’s a solution found.

22

Just wanted to chime in quickly and say this issue is still ongoing. I show relatively stable ping, but sometimes I can’t do anything and disconnects are common.

very frustrating

23

Same thing happening to me. I play on NA servers from Brazil and my normal ping is around 120. Been getting 400+ for a couple days now.

Tracing route to 137.221.105.2 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms MyRouter.Home [192.168.1.1]
2 9 ms 8 ms 4 ms 186-230-221-116.ded.intelignet.com.br [186.230.221.116]
3 7 ms 7 ms 7 ms 10.40.64.64
4 8 ms 7 ms 27 ms 10.40.64.22
5 12 ms 7 ms 7 ms 10.223.238.236
6 7 ms 7 ms 7 ms et2-0-0.sanpaolo2.spa.seabone .net [149.3.181.9]
7 8 ms 8 ms 10 ms et0-0-5.sanpaolo8.spa.seabone .net [195.22.219.17]
8 9 ms 9 ms 9 ms ntt-verio.sanpaolo8.spa.seabone .net [149.3.181.65]
9 117 ms 118 ms 117 ms ae-8.r24.nycmny01.us.bb.gin. ntt .net [129.250.2.12]
10 191 ms 191 ms 194 ms ae-4.r22.sttlwa01.us.bb.gin.ntt.n et [129.250.4.13]
11 282 ms 283 ms 282 ms ae-13.r30.tokyjp05.jp.bb.gin.ntt .net [129.250.4.143]
12 273 ms 273 ms 273 ms ae-2.r00.tokyjp08.jp.bb.gin.ntt .net [129.250.6.127]
13 275 ms 273 ms 273 ms ae-1.a00.tokyjp03.jp.bb.gin.ntt .net [129.250.5.51]
14 292 ms 279 ms 277 ms 61.213.179.114
15 274 ms 274 ms 274 ms et-0-0-48-br01-eqty2.blizzardonline .net [137.221.81.33]
16 382 ms 439 ms 280 ms xe-0-0-0-1-br01-eqla1.as57976 .net [137.221.65.56]
17 279 ms 279 ms 279 ms et-0-0-2-br01-swlv10.as57976 .net [137.221.65.69]
18 281 ms 279 ms 279 ms et-0-0-31-pe01-swlv10.as57976 .net [137.221.83.67]
19 280 ms 279 ms 279 ms 137.221.105.2

Trace complete.

24

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

Host - % Sent Recv Best Avrg Wrst Last
router.asus.c - 0 313 313 0 0 3 0
No response from host - 100 62 0 0 0 0 0
64-126-3-37.static.everestkc.n - 5 265 253 6 9 52 8
ibr33-te-0-2-0.mci.surewest.c - 5 261 248 5 9 36 8
ae-28.a01.chcgil09.us.bb.gin.ntt.n - 6 257 243 25 28 74 34
ae-9.r08.chcgil09.us.bb.gin.ntt.n - 5 265 253 155 159 187 158
ae-0.r20.chcgil09.us.bb.gin.ntt.n - 5 261 248 25 30 125 28
ae-7.r23.sttlwa01.us.bb.gin.ntt.n - 27 149 109 70 72 99 72
ae-0.r22.sttlwa01.us.bb.gin.ntt.n - 6 257 243 70 72 125 71
ae-13.r30.tokyjp05.jp.bb.gin.ntt.n - 6 253 238 158 161 215 159
ae-2.r00.tokyjp08.jp.bb.gin.ntt.n - 3 289 283 163 165 206 164
ae-1.a00.tokyjp03.jp.bb.gin.ntt.n - 5 261 248 161 164 205 162
61.213.179.114 - 6 257 243 158 166 215 159
et-0-0-48-br01-eqty2.blizzardonline.n - 5 261 248 163 172 354 164
xe-0-0-0-1-br01-eqla1.as57976.n - 8 239 221 164 235 2282 176
et-0-0-2-br01-swlv10.as57976.n - 4 266 256 162 214 4476 164
137.221.65.133 - 3 285 278 162 170 271 178
be1-pe01-eqch2.as57976.n - 5 269 258 164 166 208 164
24.105.62.129 - 3 281 273 164 167 216 166
________________________________________________ ______ ______ ______ ______ ______ ______

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

Fresh MTR, looks like the troubles usually start here:
xe-0-0-0-1-br01-eqla1.as57976.n - 8

pretty sad packet loss all around too, I am on a wired connection.

here’s another where I actually was disconnected…

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

Host - % Sent Recv Best Avrg Wrst Last
router.asus.c - 0 227 227 0 0 3 1
No response from host - 100 45 0 0 0 0 0
64-126-3-37.static.everestkc.n - 7 175 163 4 10 58 8
ibr33-te-0-2-0.mci.surewest.c - 10 164 149 5 11 80 42
ae-28.a01.chcgil09.us.bb.gin.ntt.n - 9 169 155 25 30 98 38
ae-9.r08.chcgil09.us.bb.gin.ntt.n - 9 168 154 157 160 230 197
ae-0.r20.chcgil09.us.bb.gin.ntt.n - 9 168 154 24 33 112 68
ae-7.r23.sttlwa01.us.bb.gin.ntt.n - 36 92 59 70 73 129 74
ae-0.r22.sttlwa01.us.bb.gin.ntt.n - 9 168 154 69 74 128 103
ae-13.r30.tokyjp05.jp.bb.gin.ntt.n - 10 165 150 158 161 215 159
ae-2.r00.tokyjp08.jp.bb.gin.ntt.n - 9 172 158 162 165 213 188
ae-1.a00.tokyjp03.jp.bb.gin.ntt.n - 10 163 148 161 165 234 163
61.213.179.114 - 6 185 175 156 166 234 188
et-0-0-48-br01-eqty2.blizzardonline.n - 9 167 153 163 181 843 183
xe-0-0-0-1-br01-eqla1.as57976.n - 19 127 103 164 244 1802 178
et-0-0-2-br01-swlv10.as57976.n - 9 159 145 161 252 4883 165
137.221.65.133 - 9 172 158 163 170 221 164
be1-pe01-eqch2.as57976.n - 8 176 163 162 167 204 182
24.105.62.129 - 8 172 159 164 168 224 183
________________________________________________ ______ ______ ______ ______ ______ ______

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

and disconnected 2 more times in one BG, game is literally unplayable

25

Just wanted to chime in here and say I am having the same issues. It’s a bad hop going to a tokyojp? Last night my ping shot to 2k and 4k, I had to log off, 100k from level 120, pretty upset. Hope this gets resolved soon. I ran a tracert when I woke up this morning and it was still showing 500 - 600ms.

26

I’m also experiencing this as well in KC. My ms/world is usually 30/30 and for the past few days It 160+. I use Consilidated Communications. Does this mean I need to call them to have them open a ticket with NTT? Certainly they should all be aware of this issue by now?

27

I contacted consolidated communications the other day and was promptly told “everything looks fine on our end” so I’m not exactly expecting a lot of help from them.

Tbh there isn’t much to show, even if I show them the WinMTR log. They will see a ping spike on one node in my route and probably say “well what can we do about that?”

28

So is something we just have to wait for NTT/Blizzard to fix? This will suck if this is my new ping!

29

the ping isn’t great, but the disconnects and massive packet loss is my main problem now. I can’t complete a single activity without a disconnect for the most part.

30

Yep I had to remove myself from Heroic EP cuz I couldn’t do sh*t for dps

31

A post was merged into an existing topic: High Latency when routed through Cogent Communications

32

Daedalios, your problem is a bit different and is actually a routing problem with Cogent Communications. You should post your MTR in my thread I created 2 weeks ago for the exact same problem.

33

I’ve posted in your thread as well with my WinMTR log.

I thought you used to be able to play on EU servers from the US, but I don’t see them in the list anymore. When did that change?

34

I’m at work, is this still on-going? I’ll be sad when I get home and still have 500 ms all night :confused:.

35

It was earlier today when I checked so… and its saturday so i doubt anything is going to happen with it.

36

8/10/19
Still no change Digital path won’t do anything about it. Because they dont know how to fix it. I called them they sent "case file / ticket " in I doubt it. Someone in the call center explained to me they dont have "T2-T3 techs " there its just the call people and tech. The ones taking our class can’t do anything about it because they legit are just given a guide line sheet and they follow it to trouble shoot routers and get their connection back lol .Their techs can’t and dont know how to fix peering and routing issues. THE BEST fix tbh at this point is to leave that ISP swap over to succeed ( they mostly cover the same area BETTER PRICES AND it works when you get online ). Digital path in general is trash lol , if you look at their reviews everywhere its just hot dung lol. All this ISP is good for is looking at idk the weather because Google its self with them takes 3.6 seconds to load thats worse then dial up my phones hot spot is LEGIT better then this internet.