Big-ish world latency, tracert inside

I’m sitting around ~600ms world latency. This was my traceroute as of a few minutes ago (when I was trying to post it and couldn’t because “links” … grumble)

Anyways, big world lag, looks like it’s all the Blizzard domain (137.221.75.35, as57976) as far as I can tell?

1    <1 ms    <1 ms    <1 ms  dsldevice.attlocal.net [192.168.1.254]
2     8 ms    10 ms    12 ms  162-192-104-1.lightspeed.tukrga.sbcglobal.net [162.192.104.1]
3     2 ms     2 ms     3 ms  76.239.207.206
4     3 ms     3 ms     5 ms  76.201.209.6
5     6 ms     3 ms     3 ms  12.83.82.181
6     6 ms     4 ms     4 ms  12.242.113.159
7     5 ms     5 ms     5 ms  12.247.68.74
8    49 ms    48 ms    48 ms  137.221.75.35
9   104 ms    58 ms    57 ms  xe-0-0-0-0-br01-eqda6.as57976.net [137.221.65.48]
10    49 ms    53 ms    48 ms  et-0-0-29-br02-eqda6.as57976.net [137.221.65.101]
11    49 ms    49 ms    49 ms  et-0-0-2-br02-swlv10.as57976.net [137.221.65.67]
12   103 ms    70 ms    48 ms  et-0-0-1-pe04-swlv10.cs57976.net [137.221.83.95]
13    52 ms    52 ms    52 ms  las-swlv10-ia-bons-04.as57976.net [137.221.66.23]
14    49 ms    48 ms    48 ms  137.221.105.15
15    49 ms    48 ms    48 ms  137.221.106.104

As expected, other domains / games / websites work fine. Just lagging in-game and when trying to load a page from Blizzard domain (such as the forums).

that tracert looks pretty good. let’s try running a winmtr. https://us.battle.net/support/en/article/27780 run it for 10-15 minutes, you can be in-game to make sure you’re experiencing the problem while it is going, and then post it. you’ll need to post it in a preformatted text box as well.

Huh? How does a ~550ms RTT trace look good… this shows almost the exact world latency I see in-game.

where are you getting 550ms from?

From the tracert. Just the blizz hops are 50 or 100ms each.

You don’t sum the hops. That time is the time it takes to reach that hop round trip. it is taking you 49ms round trip to reach the server. the inflated times midway are due to hops set not to respond to your test traffic or responding with low priority.

Oh, really? TIL. I’ll try the other method then, once I’m done with my work call.

np! yep the winmtr will give us similar data but then it shows us packet loss as well and can sometimes help us make sense if there is a problem a little better.

Looks not-that-bad here in the average case. But I am currently at 3940 ms (home) in-game. I couldn’t move for like 20s at a time and just dropped a void circle on vex while rubberbanding.

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                  dsldevice.attlocal.net -    0 |  856 |  856 |    0 |    0 |    5 |    0 |
|162-192-104-1.lightspeed.tukrga.sbcglobal.net -    0 |  856 |  856 |    1 |    4 |  191 |    8 |
|                          76.239.207.206 -    0 |  856 |  856 |    1 |    2 |  276 |    2 |
|                            76.201.209.6 -    0 |  856 |  856 |    2 |    4 |  284 |    3 |
|                            12.83.82.189 -    0 |  856 |  856 |    3 |    6 |   13 |    3 |
|                          12.242.113.159 -    0 |  856 |  856 |    3 |    3 |   10 |    4 |
|                            12.247.68.74 -    2 |  813 |  802 |    3 |    8 |   81 |    4 |
|              ae1-br01-eqat2.as57976.net -    0 |  856 |  856 |   23 |   26 |  116 |   24                     |
|         et-0-0-4-br02-eqch2.as57976.net -    0 |  856 |  856 |   23 |   46 |  825 |   24 |
|         et-0-0-1-pe04-eqch2.as57976.net -    0 |  856 |  856 |   23 |   26 |  136 |   61 |
|        chi-eqch2-ia-bons-04.as57976.net -    0 |  856 |  856 |   24 |   25 |   37 |   27 |
|                           24.105.62.129 -    0 |  856 |  856 |   24 |   25 |   34 |   26 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

My group is currently talking in chat about what boss is next, but on my client it’s still replaying Vex at 20% hp. Lol.

I’m doing the West servers now. After a few minutes of loading screen (and getting kicked from the raid, RIP), it looks pretty bad… 7% packet loss…

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                  dsldevice.attlocal.net -    0 |  192 |  192 |    0 |    0 |    1 |    0 |
|162-192-104-1.lightspeed.tukrga.sbcglobal.net -    0 |  192 |  192 |    1 |    4 |   23 |    7 |
|                          76.239.207.206 -    0 |  192 |  192 |    1 |    2 |    6 |    2 |
|                            76.201.209.6 -    0 |  192 |  192 |    2 |    5 |  340 |    5 |
|                            12.83.82.181 -    0 |  192 |  192 |    3 |    7 |   22 |    5 |
|                          12.242.113.159 -    0 |  192 |  192 |    3 |    3 |    8 |    6 |
|                            12.247.68.74 -    4 |  168 |  162 |    4 |    8 |   64 |    4 |
|                           137.221.75.35 -    0 |  191 |  191 |   48 |   50 |  147 |   49 |
|       xe-0-0-0-0-br01-eqda6.as57976.net -    0 |  191 |  191 |   48 |   53 |  156 |   50 |
|        et-0-0-29-br02-eqda6.as57976.net -    7 |  149 |  139 |   48 |   51 |  150 |   48 |
|        et-0-0-2-br02-swlv10.as57976.net -    0 |  191 |  191 |   48 |   50 |   89 |   48 |
|        et-0-0-1-pe02-swlv10.as57976.net -    3 |  172 |  167 |   48 |   51 |  155 |   49 |
|       las-swlv10-ia-bons-02.as57976.net -    0 |  191 |  191 |   48 |   49 |   62 |   49 |
|                           137.221.105.2 -    0 |  191 |  191 |   48 |   48 |   61 |   48 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

Hey there,

Both WinMTRs look fine actually. The way you read these tests is you want to look for any packet loss or high latency that carries through the rest of the hops in the test. So that line with 7% loss only exists on that one hop and doesn’t show up in any subsequent hops, same with that 3%. The hops near the end show 191 sent / 191 received which is perfect.

It sounds like whatever is causing your latency in-game it’s not showing up in connection tests.

Lets go back to the basics first. Have you tried power cycling the network and resetting the UI to see if those help?

Is anyone else on the home network using the internet as well?

Did the issue just start today at a certain time or has it been consistently happening for days/weeks/etc?

  1. The internet connection as a whole is fine. Speed test shows ~900 Mbits. I’m wired into the modem which is AT&T fiber. No other applications or websites have any problems.

  2. It isn’t a UI thing. I haven’t changed the UI, but besides that I get the same horrible lag using your forums (even from my phone on the wifi). It takes several seconds to click a link on the forums.

The issue is totally new today; I never have any connection issues when playing the game normally. It seems to be new as of this evening (though I can’t say when during the day it may have started).

I will try powercycling my modem now.

Awesome thanks for the info.

It isn’t unheard of for in-game latency issues to not show up in connection tests, but it does happen sometimes.

If power cycling doesn’t help, do you have access to an alternate internet connection like a mobile hotspot or a VPN that you could temporarily connect through to see if the issue goes away? That would at least help narrow down if the problems are occurring somewhere between your ISP and the Blizzard network.

I am playing for a bit to see if it is resolved. Will update in a while.

Sounds good!
Replying back to you so you can post again when you’re ready.

Nope still having huge latency. Logged on just now for the first time today, joined a TW with my guildies. Immediately frozen inside the instance. Finally could move a little, world latency says >1000ms

I saw someone mention “looking-glass” on another latency-related thread, so I’ve run that tool as well. Here is the output right now:

TRACEROUTE:    TRACEROUTE:
traceroute to 69.232.252.245 (69.232.252.245), 15 hops max, 60 byte packets
 1  Blizzard Blizzard  2.576 ms  2.555 ms  2.555 ms
 2  24.105.18.130 (24.105.18.130)  2.748 ms  2.826 ms  2.908 ms
 3  137.221.105.10 (137.221.105.10)  3.018 ms  3.035 ms  3.098 ms
 4  137.221.66.20 (137.221.66.20)  3.419 ms  3.436 ms  3.440 ms
 5  137.221.83.84 (137.221.83.84)  143.247 ms  143.279 ms  143.289 ms
 6  * * *
 7  137.221.68.32 (137.221.68.32)  6.056 ms  12.300 ms  12.302 ms
 8  12.245.64.9 (12.245.64.9)  12.267 ms  11.477 ms  11.456 ms
 9  cr86.la2ca.ip.att.net (12.122.104.78)  50.244 ms  49.383 ms  49.364 ms
10  dlstx22crs.ip.att.net (12.122.2.81)  53.224 ms  55.929 ms  50.646 ms
11  attga21crs.ip.att.net (12.122.2.109)  54.384 ms  54.409 ms  54.414 ms
12  attga22crs.ip.att.net (12.122.2.134)  50.110 ms  57.090 ms  57.086 ms
13  12.122.141.217 (12.122.141.217)  55.530 ms  51.722 ms  51.059 ms
14  * * *
15  * * *


15/07/2020 01:35:52 UTC
--------------------

TRACEROUTE:
traceroute to 69.232.252.245 (69.232.252.245), 15 hops max, 60 byte packets
 1  Blizzard Blizzard  0.550 ms  0.525 ms  0.529 ms
 2  24.105.18.130 (24.105.18.130)  1.449 ms  1.481 ms  1.490 ms
 3  137.221.105.10 (137.221.105.10)  1.496 ms  1.502 ms  1.509 ms
 4  137.221.66.20 (137.221.66.20)  0.865 ms  0.889 ms  0.898 ms
 5  137.221.83.84 (137.221.83.84)  247.551 ms  247.560 ms  477.071 ms
 6  * * *
 7  137.221.68.32 (137.221.68.32)  5.845 ms  5.867 ms  5.901 ms
 8  12.245.64.9 (12.245.64.9)  6.040 ms  5.758 ms  5.839 ms
 9  cr86.la2ca.ip.att.net (12.122.104.78)  49.443 ms  48.608 ms  48.653 ms
10  dlstx22crs.ip.att.net (12.122.2.81)  51.672 ms  48.312 ms  48.301 ms
11  attga21crs.ip.att.net (12.122.2.109)  52.021 ms  51.909 ms  51.478 ms
12  attga22crs.ip.att.net (12.122.2.134)  54.841 ms  51.128 ms  51.140 ms
13  12.122.141.217 (12.122.141.217)  54.470 ms  50.555 ms  50.546 ms
14  * * *
15  * * *


15/07/2020 01:35:52 UTC
--------------------

PING:
PING 69.232.252.245 (69.232.252.245) 56(84) bytes of data.

--- 69.232.252.245 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 2998ms



15/07/2020 01:35:52 UTC
--------------------

PING:
PING 69.232.252.245 (69.232.252.245) 56(84) bytes of data.

--- 69.232.252.245 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 3013ms



15/07/2020 01:35:54 UTC
--------------------

TRACEROUTE:
traceroute to 69.232.252.245 (69.232.252.245), 15 hops max, 60 byte packets
 1  Blizzard Blizzard  0.628 ms  0.621 ms  0.629 ms
 2  24.105.18.130 (24.105.18.130)  1.061 ms  1.085 ms  1.096 ms
 3  137.221.105.10 (137.221.105.10)  1.117 ms  1.125 ms  1.134 ms
 4  137.221.66.20 (137.221.66.20)  1.529 ms  1.541 ms  1.549 ms
 5  137.221.83.84 (137.221.83.84)  25.601 ms  25.613 ms  25.623 ms
 6  * * *
 7  137.221.68.32 (137.221.68.32)  6.236 ms  6.084 ms  7.064 ms
 8  12.245.64.9 (12.245.64.9)  5.885 ms  6.150 ms  6.251 ms
 9  cr86.la2ca.ip.att.net (12.122.104.78)  49.665 ms  49.076 ms  49.057 ms
10  dlstx22crs.ip.att.net (12.122.2.81)  52.855 ms  48.907 ms  48.348 ms
11  attga21crs.ip.att.net (12.122.2.109)  52.037 ms  51.229 ms  51.113 ms
12  attga22crs.ip.att.net (12.122.2.134)  54.451 ms  55.128 ms  55.107 ms
13  12.122.141.217 (12.122.141.217)  50.599 ms  54.497 ms  54.520 ms
14  * * *
15  * * *


15/07/2020 01:35:57 UTC
--------------------

PING:
PING 69.232.252.245 (69.232.252.245) 56(84) bytes of data.

--- 69.232.252.245 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 3005ms



15/07/2020 01:36:00 UTC
--------------------

TRACEROUTE:
traceroute to 69.232.252.245 (69.232.252.245), 15 hops max, 60 byte packets
 1  Blizzard Blizzard  0.485 ms  0.473 ms  0.467 ms
 2  37.244.23.3 (37.244.23.3)  0.638 ms  0.812 ms  1.042 ms
 3  24.105.62.148 (24.105.62.148)  0.957 ms  2.447 ms  2.453 ms
 4  137.221.66.12 (137.221.66.12)  2.089 ms  2.097 ms  2.095 ms
 5  137.221.69.56 (137.221.69.56)  1.970 ms  1.972 ms  1.998 ms
 6  137.221.69.34 (137.221.69.34)  2.048 ms  2.134 ms  2.106 ms
 7  12.246.90.153 (12.246.90.153)  2.263 ms  2.356 ms  2.341 ms
 8  cr1.cgcil.ip.att.net (12.122.133.194)  29.910 ms  29.102 ms  29.045 ms
 9  cl2oh21crs.ip.att.net (12.122.2.226)  22.820 ms  22.828 ms  22.897 ms
10  nsvtn22crs.ip.att.net (12.122.2.50)  23.336 ms  23.344 ms  23.403 ms
11  attga21crs.ip.att.net (12.122.2.5)  24.917 ms  25.694 ms  25.672 ms
12  attga22crs.ip.att.net (12.122.2.134)  23.301 ms  27.300 ms  27.297 ms
13  12.122.141.217 (12.122.141.217)  25.300 ms  29.698 ms  29.691 ms
14  * * *
15  * * *


15/07/2020 01:36:05 UTC
--------------------

MTR:
Start: Wed Jul 15 01:35:52 2020 Blizzard  1.|-- Blizzard          0.0%    10    0.5   0.7   0.3   3.2   0.7
  2.|-- 24.105.18.130          0.0%    10    1.1   0.9   0.5   2.5   0.5
  3.|-- 137.221.105.10         0.0%    10    0.9   1.1   0.8   2.7   0.5
  4.|-- 137.221.66.20          0.0%    10    0.5   5.8   0.4  53.1  16.6
  5.|-- 137.221.83.84          0.0%    10  404.6 247.6  59.5 917.1 263.7
  6.|-- ???                   100.0    10    0.0   0.0   0.0   0.0   0.0
  7.|-- 137.221.68.32          0.0%    10    6.1   6.6   6.0   7.8   0.3
  8.|-- 12.245.64.9            0.0%    10    5.8   6.3   5.7   9.5   1.1
  9.|-- cr86.la2ca.ip.att.net  0.0%    10   52.6  50.5  46.3  53.7   2.6
 10.|-- dlstx22crs.ip.att.net  0.0%    10   46.1  49.1  46.1  52.1   2.2
 11.|-- attga21crs.ip.att.net  0.0%    10   55.9  53.5  49.8  56.4   2.5
 12.|-- attga22crs.ip.att.net  0.0%    10   49.2  51.4  49.2  55.2   2.1
 13.|-- 12.122.141.217         0.0%    10   50.7  52.6  49.7  56.5   2.3
 14.|-- ???                   100.0    10    0.0   0.0   0.0   0.0   0.0
 15.|-- ???                   100.0    10    0.0   0.0   0.0   0.0   0.0
 16.|-- 76.239.207.207         0.0%    10   51.8  53.1  50.6  68.8   5.5
 17.|-- ???                   100.0    10    0.0   0.0   0.0   0.0   0.0


15/07/2020 01:35:52 UTC
--------------------

MTR:
Start: Wed Jul 15 01:35:52 2020 Blizzard  1.|-- Blizzard          0.0%    10    0.5   0.4   0.3   0.6   0.0
  2.|-- 24.105.18.130          0.0%    10    7.7   2.4   0.5   9.1   3.2
  3.|-- 137.221.105.10         0.0%    10    0.9   1.0   0.7   1.7   0.0
  4.|-- 137.221.66.20          0.0%    10    0.7   5.6   0.5  48.3  15.0
  5.|-- 137.221.83.84          0.0%    10  304.2 323.3   7.8 1046. 356.3
  6.|-- ???                   100.0    10    0.0   0.0   0.0   0.0   0.0
  7.|-- 137.221.68.32          0.0%    10    6.1   8.3   6.0  23.2   5.4
  8.|-- 12.245.64.9            0.0%    10    5.8   6.0   5.8   6.3   0.0
  9.|-- cr86.la2ca.ip.att.net  0.0%    10   48.0  50.6  47.7  55.0   2.4
 10.|-- dlstx22crs.ip.att.net  0.0%    10   49.9  49.7  46.1  52.9   2.2
 11.|-- attga21crs.ip.att.net  0.0%    10   51.6  52.8  49.2  56.5   2.4
 12.|-- attga22crs.ip.att.net  0.0%    10   52.9  53.2  49.2  56.1   2.4
 13.|-- 12.122.141.217         0.0%    10   54.3  52.7  49.2  56.2   2.4
 14.|-- ???                   100.0    10    0.0   0.0   0.0   0.0   0.0
 15.|-- ???                   100.0    10    0.0   0.0   0.0   0.0   0.0
 16.|-- 76.239.207.207         0.0%    10   51.4  54.5  50.5  77.1   8.2
 17.|-- ???                   100.0    10    0.0   0.0   0.0   0.0   0.0


15/07/2020 01:35:52 UTC
--------------------

PING:
PING 69.232.252.245 (69.232.252.245) 56(84) bytes of data.

--- 69.232.252.245 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 2999ms



15/07/2020 01:36:05 UTC
--------------------

TRACEROUTE:
traceroute to 69.232.252.245 (69.232.252.245), 15 hops max, 60 byte packets
 1  Blizzard Blizzard  0.696 ms  0.700 ms  0.703 ms
 2  37.244.23.3 (37.244.23.3)  1.096 ms  1.113 ms  1.115 ms
 3  24.105.62.148 (24.105.62.148)  2.431 ms  4.114 ms  4.132 ms
 4  137.221.66.12 (137.221.66.12)  2.379 ms  2.397 ms  2.402 ms
 5  137.221.69.56 (137.221.69.56)  597.796 ms  597.804 ms  597.811 ms
 6  137.221.69.34 (137.221.69.34)  2.469 ms  2.065 ms  2.041 ms
 7  12.246.90.153 (12.246.90.153)  2.271 ms  2.847 ms  2.813 ms
 8  cr1.cgcil.ip.att.net (12.122.133.194)  30.519 ms  30.567 ms  30.892 ms
 9  cl2oh21crs.ip.att.net (12.122.2.226)  24.136 ms  23.660 ms  23.641 ms
10  nsvtn22crs.ip.att.net (12.122.2.50)  24.004 ms  23.462 ms  23.268 ms
11  attga21crs.ip.att.net (12.122.2.5)  25.025 ms  24.873 ms  23.819 ms
12  attga22crs.ip.att.net (12.122.2.134)  28.913 ms  23.415 ms  23.296 ms
13  12.122.141.217 (12.122.141.217)  29.291 ms  28.890 ms  28.895 ms
14  * * *
15  * * *


15/07/2020 01:36:08 UTC
--------------------

MTR:
Start: Wed Jul 15 01:35:55 2020 Blizzard  1.|-- Blizzard          0.0%    10    0.4   1.3   0.4   9.1   2.7
  2.|-- 24.105.18.130          0.0%    10    0.8   0.9   0.6   2.0   0.3
  3.|-- 137.221.105.10         0.0%    10    0.9   1.0   0.8   1.3   0.0
  4.|-- 137.221.66.20          0.0%    10    0.6   0.7   0.5   1.2   0.0
  5.|-- 137.221.83.84          0.0%    10  149.1 287.3  22.4 786.1 234.4
  6.|-- ???                   100.0    10    0.0   0.0   0.0   0.0   0.0
  7.|-- 137.221.68.32          0.0%    10    6.1  11.2   6.0  25.7   8.2
  8.|-- 12.245.64.9            0.0%    10    5.8   5.9   5.8   6.2   0.0
  9.|-- cr86.la2ca.ip.att.net  0.0%    10   48.2  51.5  46.1  68.5   6.5
 10.|-- dlstx22crs.ip.att.net  0.0%    10   49.9  50.3  46.1  58.1   3.5
 11.|-- attga21crs.ip.att.net  0.0%    10   51.6  53.3  49.0  66.8   5.2
 12.|-- attga22crs.ip.att.net  0.0%    10   53.0  53.0  50.3  56.2   2.0
 13.|-- 12.122.141.217         0.0%    10   54.5  52.6  49.1  55.3   2.0
 14.|-- ???                   100.0    10    0.0   0.0   0.0   0.0   0.0
 15.|-- ???                   100.0    10    0.0   0.0   0.0   0.0   0.0
 16.|-- 76.239.207.207         0.0%    10   54.8  53.7  50.9  60.9   3.5
 17.|-- ???                   100.0    10    0.0   0.0   0.0   0.0   0.0


15/07/2020 01:35:54 UTC
--------------------

TRACEROUTE:
traceroute to 69.232.252.245 (69.232.252.245), 15 hops max, 60 byte packets
 1  Blizzard Blizzard  0.460 ms  0.463 ms  0.678 ms
 2  37.244.23.3 (37.244.23.3)  1.216 ms  1.222 ms  1.229 ms
 3  24.105.62.148 (24.105.62.148)  1.233 ms  1.371 ms  1.394 ms
 4  137.221.66.12 (137.221.66.12)  2.581 ms  2.602 ms  2.609 ms
 5  137.221.69.56 (137.221.69.56)  106.264 ms  106.316 ms  106.323 ms
 6  137.221.69.34 (137.221.69.34)  5.883 ms  3.644 ms  3.623 ms
 7  12.246.90.153 (12.246.90.153)  2.479 ms  2.746 ms  2.795 ms
 8  cr1.cgcil.ip.att.net (12.122.133.194)  23.293 ms  22.837 ms  22.817 ms
 9  cl2oh21crs.ip.att.net (12.122.2.226)  24.416 ms  23.890 ms  23.870 ms
10  nsvtn22crs.ip.att.net (12.122.2.50)  33.144 ms  41.367 ms  39.053 ms
11  attga21crs.ip.att.net (12.122.2.5)  30.756 ms  30.771 ms  30.775 ms
12  attga22crs.ip.att.net (12.122.2.134)  36.361 ms  37.319 ms  37.339 ms
13  12.122.141.217 (12.122.141.217)  48.347 ms  47.301 ms  47.299 ms
14  * * *
15  * * *


15/07/2020 01:36:11 UTC
--------------------

PING:
PING 69.232.252.245 (69.232.252.245) 56(84) bytes of data.

--- 69.232.252.245 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 2998ms



15/07/2020 01:36:08 UTC
--------------------

PING:
PING 69.232.252.245 (69.232.252.245) 56(84) bytes of data.

--- 69.232.252.245 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 2998ms



15/07/2020 01:36:11 UTC
--------------------

MTR:
Start: Wed Jul 15 01:36:00 2020 Blizzard  1.|-- Blizzard          0.0%    10    0.2   0.4   0.2   0.7   0.0
  2.|-- 37.244.23.131          0.0%    10    0.5   0.6   0.5   0.7   0.0
  3.|-- 24.105.62.148          0.0%    10    1.1   1.1   1.0   1.3   0.0
  4.|-- 137.221.66.8           0.0%    10    1.5   4.1   1.1  29.9   9.0
  5.|-- 137.221.69.50          0.0%    10   38.5  69.7   1.5 558.4 172.9
  6.|-- 137.221.69.34          0.0%    10    2.4  11.6   1.5  53.2  20.6
  7.|-- 12.246.90.153          0.0%    10    2.3   2.1   1.8   2.4   0.0
  8.|-- cr1.cgcil.ip.att.net   0.0%    10   30.0  27.7  23.9  37.5   4.0
  9.|-- cl2oh21crs.ip.att.net  0.0%    10   23.6  26.4  23.6  29.6   2.1
 10.|-- nsvtn22crs.ip.att.net  0.0%    10   24.1  26.0  23.0  30.1   2.6
 11.|-- attga21crs.ip.att.net  0.0%    10   23.7  26.9  23.5  30.6   2.6
 12.|-- attga22crs.ip.att.net  0.0%    10   24.9  26.1  22.8  29.8   2.0
 13.|-- 12.122.141.217         0.0%    10   24.0  25.9  23.2  29.2   2.0
 14.|-- ???                   100.0    10    0.0   0.0   0.0   0.0   0.0
 15.|-- 76.201.209.7          80.0%    10   23.0  23.2  23.0  23.4   0.0
 16.|-- 76.239.207.207         0.0%    10   24.4  26.0  24.4  31.2   2.1
 17.|-- ???                   100.0    10    0.0   0.0   0.0   0.0   0.0


15/07/2020 01:36:00 UTC
--------------------

MTR:
Start: Wed Jul 15 01:36:07 2020 Blizzard  1.|-- Blizzard           0.0%    10    0.2   0.3   0.2   0.3   0.0
  2.|-- 37.244.23.3            0.0%    10    0.4   0.6   0.4   0.7   0.0
  3.|-- 24.105.62.148          0.0%    10    0.9   1.2   0.8   2.4   0.3
  4.|-- 137.221.66.12          0.0%    10    2.2   3.9   2.0  19.4   5.4
  5.|-- 137.221.69.56          0.0%    10   24.9  45.2   1.8 296.0  93.3
  6.|-- 137.221.69.34          0.0%    10    2.1  19.5   2.0 118.2  39.0
  7.|-- 12.246.90.153          0.0%    10    2.4   2.4   2.3   2.7   0.0
  8.|-- cr1.cgcil.ip.att.net   0.0%    10   27.0  26.9  24.0  29.8   2.0
  9.|-- cl2oh21crs.ip.att.net  0.0%    10   23.1  26.3  23.1  30.1   2.9
 10.|-- nsvtn22crs.ip.att.net  0.0%    10   26.0  26.0  23.6  29.2   1.8
 11.|-- attga21crs.ip.att.net  0.0%    10   30.1  26.8  22.6  30.3   2.5
 12.|-- attga22crs.ip.att.net  0.0%    10   29.5  26.2  23.0  30.8   2.6
 13.|-- 12.122.141.217         0.0%    10   30.1  27.2  23.4  30.9   2.4
 14.|-- ???                   100.0    10    0.0   0.0   0.0   0.0   0.0
 15.|-- 76.201.209.7          80.0%    10   24.1  24.4  24.1  24.7   0.0
 16.|-- 76.239.207.207         0.0%    10   25.3  26.7  24.4  33.5   3.5
 17.|-- ???                   100.0    10    0.0   0.0   0.0   0.0   0.0


15/07/2020 01:36:07 UTC
--------------------

MTR:
Start: Wed Jul 15 01:36:10 2020 Blizzard  1.|-- Blizzard           0.0%    10    2.9   0.6   0.3   2.9   0.7
  2.|-- 37.244.23.3            0.0%    10    0.5   0.6   0.4   0.8   0.0
  3.|-- 24.105.62.148          0.0%    10    0.9   1.6   0.9   2.5   0.3
  4.|-- 137.221.66.12          0.0%    10    2.0  13.5   1.9 116.9  36.3
  5.|-- 137.221.69.56          0.0%    10    2.0  16.3   1.8 120.7  37.0
  6.|-- 137.221.69.34          0.0%    10   26.5   4.6   2.0  26.5   7.7
  7.|-- 12.246.90.153          0.0%    10    2.3   2.4   2.3   2.6   0.0
  8.|-- cr1.cgcil.ip.att.net   0.0%    10   27.2  26.0  23.4  29.8   2.1
  9.|-- cl2oh21crs.ip.att.net  0.0%    10   29.3  27.0  23.0  31.3   2.5
 10.|-- nsvtn22crs.ip.att.net  0.0%    10   23.3  26.7  23.3  29.3   2.0
 11.|-- attga21crs.ip.att.net  0.0%    10   24.6  25.5  22.9  29.2   2.0
 12.|-- attga22crs.ip.att.net  0.0%    10   30.0  26.8  23.5  30.0   2.4
 13.|-- 12.122.141.217         0.0%    10   28.3  27.7  24.5  30.6   1.8
 14.|-- ???                   100.0    10    0.0   0.0   0.0   0.0   0.0
 15.|-- ???                   100.0    10    0.0   0.0   0.0   0.0   0.0
 16.|-- 76.239.207.207         0.0%    10   24.5  25.4  24.4  33.3   2.7
 17.|-- ???                   100.0    10    0.0   0.0   0.0   0.0   0.0


15/07/2020 01:36:10 UTC
--------------------

I’m running “pathping” as well and will post that.

EDIT: Here is pathping:

Tracing route to 37.244.23.3 over a maximum of 30 hops

  0  DESKTOP-2M8CPLC.attlocal.net [192.168.1.83] 
  1  dsldevice.attlocal.net [192.168.1.254] 
  2  162-192-104-1.lightspeed.tukrga.sbcglobal.net [162.192.104.1] 
  3  76.239.207.206 
  4  76.201.209.6 
  5  12.83.82.181 
  6  12.242.113.159 
  7  12.247.68.74 
  8  ae1-br01-eqat2.as57976.net [137.221.75.33] 
  9  et-0-0-4-br02-eqch2.as57976.net [137.221.65.46] 
 10  et-0-0-1-pe01-eqch2.as57976.net [137.221.69.51] 
 11  chi-eqch2-ia-bons-01.as57976.net [137.221.66.9] 
 12  37.244.23.3 

Computing statistics for 300 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           DESKTOP-2M8CPLC.attlocal.net [192.168.1.83] 
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  dsldevice.attlocal.net [192.168.1.254] 
                                0/ 100 =  0%   |
  2    1ms     0/ 100 =  0%     0/ 100 =  0%  162-192-104-1.lightspeed.tukrga.sbcglobal.net [162.192.104.1] 
                                0/ 100 =  0%   |
  3    2ms     0/ 100 =  0%     0/ 100 =  0%  76.239.207.206 
                                0/ 100 =  0%   |
  4    3ms     0/ 100 =  0%     0/ 100 =  0%  76.201.209.6 
                                0/ 100 =  0%   |
  5    7ms    99/ 100 = 99%    99/ 100 = 99%  12.83.82.181 
                                0/ 100 =  0%   |
  6  ---     100/ 100 =100%   100/ 100 =100%  12.242.113.159 
                                0/ 100 =  0%   |
  7    8ms     0/ 100 =  0%     0/ 100 =  0%  12.247.68.74 
                                0/ 100 =  0%   |
  8   27ms     0/ 100 =  0%     0/ 100 =  0%  ae1-br01-eqat2.as57976.net [137.221.75.33] 
                                0/ 100 =  0%   |
  9   29ms     0/ 100 =  0%     0/ 100 =  0%  et-0-0-4-br02-eqch2.as57976.net [137.221.65.46] 
                                0/ 100 =  0%   |
 10   30ms     0/ 100 =  0%     0/ 100 =  0%  et-0-0-1-pe01-eqch2.as57976.net [137.221.69.51] 
                                0/ 100 =  0%   |
 11  ---     100/ 100 =100%   100/ 100 =100%  chi-eqch2-ia-bons-01.as57976.net [137.221.66.9] 
                                0/ 100 =  0%   |
 12   25ms     0/ 100 =  0%     0/ 100 =  0%  37.244.23.3 

Trace complete.

EDIT 2: Gonna just keep posting various tools here. This is PingPlotter, again targeting 37.244.23.3:

https://imgur.com/a/iHFUQaA

I’m sitting in Boralus and people are occasionally moving, then running in place. Been like this for 15 minutes, world latency at >2000. Can’t be that hard to tell what’s going on since it’s so severe, right? I’m happy to run whatever you think is helpful in terms of diagnostics.

EDIT: thanks, I’ll look at the ipv6 setting and probably file a ticket tomorrow. Had to turn in for the evening. Thanks Jambrix. Super weird that this just started all of a sudden Monday night while I was playing.

Looking-glass, pathping, and PingPlotter all appear fine. The tests show you shouldn’t be getting more than 50-60ms, just like in your original tests. So whatever is causing the high latency in-game it’s not showing up in connection tests.

Can you check in-game under System → Network and see if “Enable IPv6 when available” is checked on? If it is turned on, try disabling it then restart WoW and see if things are better.
The tests run on IPv4, so if your WoW was using IPv6 and there’s an issue with the IPv6 route it wouldn’t show up in the tests.

There was also this suggestion which I mentioned in an earlier post:

Beyond that I would probably recommend that you go ahead and submit a ticket so we can get your DXDIAG and MSINFO files to look for anything specifically on the system itself that might be causing the high latency.

I have ATT Fiber. And I have had terrible random latency. Just effecting Blizzard Games.

1 Like

Just some updates:

  1. I did not have the Enable IPv6 option checked.

  2. I reset my UI (renamed cache/wtf/interface folders), reproduced just fine with no addons.

  3. I do not have access to a VPN. I can tether from my phone but I don’t want to even think about how fast I’d use up my priority data on my unlimited plan…

  4. 90% of the time it seems to happen when I switch “realms” - e.g. join an instance, or go back to Boralus. I can easily reproduce it like:

  • Log in at Boralus - everything is fine, people are moving, I can use abilities
  • Zone into Siege of Boralus - also fine, mobs are moving, I can use abilities
  • Zone back out to Boralus - immediately 2000 latency, cannot use abilities, all people are stuck in place.

I will open a ticket I guess.