High Latency Since 7/16 - Routing through NTT Japan

[Drakuloth]

I’m quoting my reply from the Overwatch forums here, so we can have more information in both threads for you:

@Drakuloth

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:

Zzzz:

|ae-10.r22.asbnva02.us.bb.gin.ntt.net|0|282|282|10|14|46|21|
|ae-5.r23.lsanca07.us.bb.gin.ntt.net|0|282|282|74|82|109|84|
| ae-12.r31.tokyjp05.jp.bb.gin.ntt.net |0|282|282|176|179|282|177|

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 , as in this example trace. The reason for this is that your ISP is sending you to a backbone provider. That backbone provider is sending your connection to 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:

1. 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*
2. 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.
3. 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.