Seems that since last update on Tuesday of this week a lot of ppl have high ms.
Most cases the route from their ISP hops to Tokyo for some reason.
Blockquote
Hope you can fix this, thx in advance.
Hey, Firecroll !
This is something we are currently tracking as it is affecting both WoW and Overwatch .
Once we have more information on this issue we will be providing updates on the forums.
Thank you for the WinMTR test!
https ://voip.review/2019/07/16/ntt-corporation-launches-new-global-technology-services-provider/
NTT launched a new “smart” routing technology this week, looks like is not that smart after all…
1 Like
I’m quoting my reply from the Overwatch forums here, so we can have more information in both threads for you:
Thanks for the tests everyone,
For those of you who are having this issue, it currently looks like the vast majority of you are going through NTT nodes such as the ones I quoted earlier:
|ae-10.r22.asbnva02.us.bb.gin.ntt.net|0|282|282|10|14|46|21|ae-12.r31.tokyjp05.jp.bb.gin.ntt.net
For those of you who are seeing this problem, you need to check your test to see if you are going through nodes that end in jp.bb.gin.ntt.net Japan on the way to a US server. That’s what the jp in these tests stands for.
We cannot fix this ourselves because it is not our provider. We are still collecting reports to see if we can help work around it or reach out to people, but please keep in mind that this part of the internet is not our responsibility, as much as we know it’s frustrating for you all.
For the time being you should:
Run a winMTR while you are having problems and see if you are being routed to Japan using the information above. If you are, post it here*
If you are, you need to report this to a tier 2 or 3 technician with your ISP - complete with a copy of your test. You need to tell them to contact NTT on your behalf to have them fix the routing.
Use a VPN to work around the issue if it is legal in your country. We can’t walk you through how to set these up, as they are third party software but they are the most common work around for a problem like this.
That should help with the latency while the ISPs work on this.
*If you do NOT go through the Japanese NTT nodes, you are having a different issue and should post your own thread.
Here are mine going through the JP NTT nodes, guess I’ll try a VPN trick for the moment…
|------------------------------------------------------------------------------------------|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Fresh MTR, looks like the troubles usually start here:
pretty sad packet loss all around too, I am on a wired connection.
here’s another where I actually was disconnected…
|------------------------------------------------------------------------------------------|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Went through a VPN tonight and had very few problems outside of some DCs in Ashran Brawl, but that probably has more to do with the limitations of the VPN than anything else.
Small scale pvp and normal play were totally fine… so yea, I really hope this gets fixed sometime soon so I don’t have to play through a VPN.
Cmon! Is not the first time that world of warcraft had an upgrade or something and this happend. Is not our ISP provider, because I can perfectly play other games, who has servers in US.
The 3 issues NTT, Level 3 and cogent are peering partner issues and routing . How routing works your ISP is responsible for the route it takes to the servers. Blizzard’s ISP is responsible for the return path to you. Any issues with routing to the blizzards servers are generally the persons ISP’s.
The locations of other games are a different. Which means the routing to their servers are different.
My ISP contacted NTT, their response was it’s due to Blizzard, and I need to contact them to get this routing issue fixed. Good times.
Unfortunately that is not correct. It would be great if blizzard had control over routing to their servers they could pick the best route for each area Unfortunately they only have control over the return path. Routing to blizzard is done by Your ISP that is how routing works. Blizzard has very little to no control over inbound traffic. NTT is routing traffic to LA through the same cable the goes to Japan the cable connects LA and Seattle to Japan . while its not actually making it all the way to japan the distance it adds to the connection is considerable.
1 Like
I’m having the same issue, i’m from Argentina btw, my normal ping is 180ms, im sitting at 340 now
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.0.1 - 0 | 463 | 463 | 0 | 0 | 6 | 0 |
| No response from host - 100 | 92 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 92 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 92 | 0 | 0 | 0 | 0 | 0 |
| 86-165-89-200.fibertel.com.ar - 0 | 463 | 463 | 5 | 12 | 78 | 16 |
| ae6.baires3.bai.seabone.net - 0 | 463 | 463 | 7 | 11 | 76 | 9 |
| et11-1-0.sanpaolo8.spa.seabone.net - 0 | 463 | 463 | 31 | 37 | 96 | 36 |
| ntt-verio.sanpaolo8.spa.seabone.net - 0 | 463 | 463 | 32 | 37 | 97 | 35 |
| ae-8.r24.nycmny01.us.bb.gin.ntt.net - 0 | 463 | 463 | 149 | 155 | 242 | 154 |
| ae-4.r22.sttlwa01.us.bb.gin.ntt.net - 1 | 459 | 458 | 217 | 223 | 311 | 224 |
| ae-13.r30.tokyjp05.jp.bb.gin.ntt.net - 0 | 462 | 462 | 292 | 298 | 478 | 295 |
| ae-2.r00.tokyjp08.jp.bb.gin.ntt.net - 0 | 463 | 463 | 289 | 291 | 465 | 290 |
| ae-1.a00.tokyjp03.jp.bb.gin.ntt.net - 0 | 463 | 463 | 305 | 311 | 532 | 311 |
| 61.213.179.114 - 0 | 463 | 463 | 309 | 316 | 505 | 309 |
| et-0-0-48-br01-eqty2.blizzardonline.net - 0 | 463 | 463 | 311 | 318 | 753 | 313 |
| xe-0-0-0-1-br01-eqla1.as57976.net - 3 | 421 | 412 | 308 | 376 | 4532 | 471 |
| et-0-0-2-br01-swlv10.as57976.net - 0 | 456 | 456 | 313 | 342 | 3066 | 314 |
| 137.221.65.133 - 0 | 463 | 463 | 311 | 316 | 535 | 311 |
| be1-pe01-eqch2.as57976.net - 0 | 463 | 463 | 313 | 316 | 515 | 314 |
| 24.105.62.129 - 0 | 463 | 463 | 314 | 316 | 517 | 315 |
|________________________________________________|______|______|______|______|______|______|
1 Like
Same here, also from Argentina. For me, it started happening on tuesday after reset.
|------------------------------------------------------------------------------------------|
Host - %
Sent
Recv
Best
Avrg
Wrst
Last
192.168.0.1 - 1
4060
4058
0
1
124
1
No response from host - 100
815
0
0
0
0
0
No response from host - 100
815
0
0
0
0
0
No response from host - 100
815
0
0
0
0
0
222-165-89-200.fibertel.com.ar - 1
4060
4058
9
16
135
16
249-165-89-200.fibertel.com.ar - 1
4060
4058
10
14
153
14
6-165-89-200.fibertel.com.ar - 1
4060
4058
11
14
153
13
150-165-89-200.fibertel.com.ar - 1
4060
4058
11
18
149
16
ae6.baires3.bai.seabone.net - 0
4068
4068
11
15
255
15
et11-1-0.sanpaolo8.spa.seabone.net - 1
4006
3990
37
43
258
40
ntt-verio.sanpaolo8.spa.seabone.net - 1
4064
4063
40
43
256
42
ae-8.r24.nycmny01.us.bb.gin.ntt.net - 1
4037
4029
145
152
322
150
ae-4.r22.sttlwa01.us.bb.gin.ntt.net - 1
3919
3881
0
202
419
200
ae-13.r30.tokyjp05.jp.bb.gin.ntt.net - 0
4068
4068
283
288
478
348
ae-2.r00.tokyjp08.jp.bb.gin.ntt.net - 0
4068
4068
283
288
480
288
ae-1.a00.tokyjp03.jp.bb.gin.ntt.net - 0
4068
4068
283
290
479
290
61.213.179.114 - 0
4068
4068
283
294
492
335
et-0-0-48-br01-eqty2.blizzardonline.net - 0
4067
4067
295
307
1491
299
xe-0-0-0-1-br01-eqla1.as57976.net - 3
3691
3611
298
378
4978
301
et-0-0-2-br01-swlv10.as57976.net - 1
3963
3951
295
328
4699
299
137.221.65.133 - 1
3893
3856
299
323
4237
301
be1-pe01-eqch2.as57976.net - 0
4068
4068
295
300
482
300
24.105.62.129 - 0
4068
4068
295
301
482
300
________________________________________________
______
______
______
______
______
______
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Last time something like this happened was on april. Apparently it was a routing problem in somepoint between blizz servers and Arg.
it was treated in this thread: https://us.forums.blizzard.com/en/wow/t/argentina-latency-increased-since-03-26-2019/143094/11
I have the same issue with a ping of 303 in Buenos Aires.
I uses CablevisiĂłn-Fibertel.
Why does a Tokyo-IP appear here?
Thank you!
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.0.1 - 0 | 112 | 112 | 0 | 0 | 7 | 0 |
| No response from host - 100 | 22 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 22 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 22 | 0 | 0 | 0 | 0 | 0 |
| 86-165-89-200.fibertel.com.ar - 1 | 108 | 107 | 8 | 14 | 36 | 15 |
| ae6.baires3.bai.seabone.net - 1 | 108 | 107 | 8 | 12 | 31 | 9 |
| et0-0-2.sanpaolo8.spa.seabone.net - 1 | 108 | 107 | 35 | 40 | 89 | 35 |
| ntt-verio.sanpaolo8.spa.seabone.net - 3 | 100 | 97 | 36 | 37 | 53 | 37 |
| ae-8.r24.nycmny01.us.bb.gin.ntt.net - 2 | 104 | 102 | 161 | 163 | 180 | 164 |
| ae-4.r22.sttlwa01.us.bb.gin.ntt.net - 3 | 100 | 97 | 0 | 224 | 248 | 225 |
| ae-13.r30.tokyjp05.jp.bb.gin.ntt.net - 2 | 104 | 102 | 307 | 311 | 336 | 310 |
| ae-2.r01.tokyjp08.jp.bb.gin.ntt.net - 1 | 108 | 107 | 316 | 318 | 336 | 318 |
| ae-2.a00.tokyjp03.jp.bb.gin.ntt.net - 0 | 111 | 111 | 298 | 302 | 331 | 301 |
| 61.213.179.114 - 0 | 111 | 111 | 294 | 300 | 355 | 296 |
| et-0-0-48-br01-eqty2.blizzardonline.net - 2 | 104 | 102 | 309 | 313 | 353 | 316 |
| xe-0-0-0-1-br01-eqla1.as57976.net - 0 | 111 | 111 | 304 | 361 | 816 | 350 |
| et-0-0-2-br01-swlv10.as57976.net - 0 | 111 | 111 | 314 | 318 | 371 | 315 |
| 137.221.65.133 - 8 | 84 | 78 | 317 | 419 | 3469 | 317 |
| be1-pe01-eqch2.as57976.net - 0 | 111 | 111 | 314 | 316 | 321 | 315 |
| chi-eqch2-ia-bons-02.as57976.net - 0 | 111 | 111 | 306 | 308 | 322 | 307 |
| 24.105.62.129 - 0 | 111 | 111 | 308 | 310 | 317 | 308 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
The OP suggested I post my route in here as well, very bad disconnects and packet loss for the last two weeks:
|------------------------------------------------------------------------------------------|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Fresh MTR, looks like the troubles usually start here:
pretty sad packet loss all around too, I am on a wired connection.
here’s another where I actually was disconnected…
|------------------------------------------------------------------------------------------|
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
I got my ISP to try and contact NTT. Hopefully something gets done. I played through a VPN today and had perfect latency. Don’t really want to pay for a VPN to play WoW… but it’ll suffice as a bandaid for now - hope it gets fixed soon.
This is an issue that Blizzard is tracking. The backbone provider NTT is routing American signals to Japan and back. Check this thread for more details:
Seems that since last update on Tuesday of this week a lot of ppl have high ms.
Most cases the route from their ISP hops to Tokyo for some reason.
Blockquote
Traza a 24.105.62.129 sobre caminos de 30 saltos como m ximo.
1 <1 ms <1 ms <1 ms SAMBASVR [192.168.1.1]
2 11 ms 10 ms 10 ms host103.181-88-172.telecom.net.ar [181.88.172.103]
3 10 ms 10 ms 10 ms host96.181-89-5.telecom.net.ar [181.89.5.96]
4 10 ms 10 ms 10 ms host194.181-96-72.telecom.net.ar …
Got off the phone with my ISP today and they contacted NTT, who said Blizzard is to blame, as to their knowledge, Blizzard is relaying that Tokyo is the fastest route to their servers.
Unfortunately that is not how routing works. Your ISP is responsible for routing to Blizzard servers. My educated guess is NTT is trying to save peering costs by connecting using their own network.
While you are being routed incorrectly you are also having issues on what looks like your ISp’s network. 5 percent packet loss that is propagating through the trace is significant