This is getting frustrating. Since last night, even though on the drop down menu on the launcher it says “Americas” under the realm, when I queue up for a game it places me on an Asian server. At first I thought it was my internet as to why I was getting almost 400 ping and bouncing to 2000+, but then as people spoke, not a single person was speaking English. I finally asked them what server I was on and someone said “China”. I am absolutely unable to connect to a US game on any mode, even though I have the American realm selected. I changed my realm to EU to see if the problem persisted, but I was greeted with my typical ping on an EU server (120).
What is going on here? I have never had this happen in any game I have played ever.
Something is broken that routes your traffic to Blizzard. This can be spotted in a WinMTR test. Instead of routing your connection to LA or Chicago, your ISP is sending you somewhere closer to China, which makes you connect there.
My friend had me run some looking glass thing, these are the results. It is weird because I was playing just fine then all this started to happen.
TRACEROUTE:
traceroute to 24.101.136.140 (24.101.136.140), 15 hops max, 60 byte packets
1 Blizzard Blizzard 2.930 ms 2.937 ms 2.938 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
12/01/2019 20:20:15 UTC
TRACEROUTE:
traceroute to 24.101.136.140 (24.101.136.140), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.285 ms 0.275 ms 0.278 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
12/01/2019 20:20:15 UTC
MTR:
Start: Sat Jan 12 20:20:15 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.7 0.0
2.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
12/01/2019 20:20:15 UTC
MTR:
Start: Sat Jan 12 20:20:15 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.4 0.0
2.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
12/01/2019 20:20:15 UTC
Unfortunately, there is almost no data in the test you posted. However, if you run the winmtr we might be able to figure it out.