High world latency big lagg when in raids

[Toystore-stormreaver (Toystore)]

I use NordVPN and it has worked over the past few days. Just selecting some other location in the U.S. seems to keep it steady around 80/80 instead of 50/4500 lol

[Urnhex-thrall]

Of course. I have tried every node. Chicago, Vegas etc. It stops the 14,000 ping spikes but it still stays from 150 to 500 and has those stalls like the cable has been unplugged for 5-10 seconds. During the early morning it works fine, but in peak hours, even with VPN, it is useless.

[Beefbeefbeef-kiljaeden]

Hudson Oaks TX, unplayable for a week.

[Animalbarn-nazjatar]

The connection is so slow, blue hasn’t even seen all these posts yet. Only explanation as to the lack of response.

[Beefpotato-stormrage]

Huh, I’m just outside Austin and get a steady 60ms to 70ms world using the Denver node which is the best I’ve found, clears up the rubberbanding and spikes nicely. I’m with Grande Comm though so I guess you’d have a slightly different routing

[Zungar-silver-hand (Zungar)]

Data-Gathering for Connection Issues When Routed Through Dallas Region [Dec. 7]

Hello gang! We are looking into reported connection issues affecting players whose connections travel through Dallas. These issues have been ongoing for several days at least. If you have been experiencing sporadic lag spikes, random fail-to-connect, or other connection issues mainly over this last week, please post back with the following: ISP: Region: Looking Glass test. WinMTR test for 5-10 minutes while playing. What server do you play on?

[Animalbarn-nazjatar]

TRACEROUTE:
traceroute to 52.128.56.140 (52.128.56.140), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.291 ms 0.272 ms 0.270 ms Blizzard(24.105.18.2) 0.577 ms 0.637 ms 0.759 ms
3 137.221.105.10 (137.221.105.10) 0.571 ms 0.628 ms 0.736 ms
4 137.221.66.16 (137.221.66.16) 9.922 ms 9.928 ms 10.004 ms
5 137.221.83.70 (137.221.83.70) 25.757 ms 25.760 ms 25.759 ms
6 137.221.65.66 (137.221.65.66) 25.601 ms 25.554 ms 25.526 ms
7 137.221.74.32 (137.221.74.32) 25.488 ms * 25.324 ms
8 eqix-da1. nextlinkbroadband-2. com (206.223.118.192) 25.696 ms 25.709 ms 25.802 ms
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *

07/12/2018 21:04:10 UTC

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

— 52.128.56.140 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 2998ms

07/12/2018 21:04:10 UTC

MTR:
Start: Fri Dec 7 21:04:10 2018 Blizzard 1.|-- Blizzard 0.0% 10 0.4 0.3 0.2 0.4 0.0
2.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

07/12/2018 21:04:10 UTC

[Animalbarn-nazjatar]

TRACEROUTE:
traceroute to 52.128.56.140 (52.128.56.140), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.511 ms 0.505 ms 0.506 ms Blizzard(24.105.18.2) 0.772 ms 1.017 ms 1.038 ms
3 137.221.105.10 (137.221.105.10) 0.720 ms 1.021 ms 1.028 ms
4 137.221.66.16 (137.221.66.16) 1.216 ms 1.242 ms 1.243 ms
5 137.221.83.70 (137.221.83.70) 34.365 ms 34.386 ms 34.395 ms
6 137.221.65.66 (137.221.65.66) 25.753 ms 31.468 ms 31.443 ms
7 137.221.74.32 (137.221.74.32) 31.578 ms 31.579 ms 31.119 ms
8 eqix-da1.nextlinkbroadband-2. com (206.223.118.192) 30.898 ms 30.886 ms *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *

07/12/2018 21:07:05 UTC

TRACEROUTE:
traceroute to 52.128.56.140 (52.128.56.140), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.369 ms 0.362 ms 0.363 ms Blizzard(24.105.18.2) 0.743 ms 0.877 ms 0.961 ms
3 137.221.105.10 (137.221.105.10) 0.719 ms 0.843 ms 0.893 ms
4 137.221.66.16 (137.221.66.16) 0.679 ms 0.856 ms 0.873 ms
5 137.221.83.70 (137.221.83.70) 25.832 ms 25.835 ms 25.837 ms
6 137.221.65.66 (137.221.65.66) 25.780 ms 25.735 ms 25.711 ms
7 137.221.74.32 (137.221.74.32) 25.502 ms 25.515 ms 25.588 ms
8 eqix-da1.nextlinkbroadband-2. com (206.223.118.192) 26.034 ms 26.030 ms 26.025 ms
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *

07/12/2018 21:07:05 UTC

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

— 52.128.56.140 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 2998ms

07/12/2018 21:07:05 UTC

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

— 52.128.56.140 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 3008ms

07/12/2018 21:07:05 UTC

TRACEROUTE:
traceroute to 52.128.56.140 (52.128.56.140), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.262 ms 0.300 ms 0.317 ms Blizzard(24.105.18.2) 1.078 ms 1.193 ms 1.299 ms
3 137.221.105.10 (137.221.105.10) 1.204 ms 1.306 ms 1.320 ms
4 137.221.66.16 (137.221.66.16) 1.147 ms 1.232 ms 1.248 ms
5 137.221.83.70 (137.221.83.70) 44.606 ms 44.662 ms 44.693 ms
6 137.221.65.66 (137.221.65.66) 25.625 ms 61.085 ms 61.134 ms
7 137.221.74.32 (137.221.74.32) 25.552 ms 25.634 ms 25.671 ms
8 eqix-da1.nextlinkbroadband-2. com (206.223.118.192) 25.922 ms 26.009 ms 26.025 ms
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *

07/12/2018 21:07:09 UTC

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

— 52.128.56.140 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 3005ms

07/12/2018 21:07:10 UTC

TRACEROUTE:
traceroute to 52.128.56.140 (52.128.56.140), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.306 ms 0.293 ms 0.305 ms Blizzard(24.105.18.2) 0.850 ms 0.927 ms 1.111 ms
3 137.221.105.10 (137.221.105.10) 0.529 ms 0.666 ms 0.698 ms
4 137.221.66.16 (137.221.66.16) 0.859 ms 0.872 ms 0.883 ms
5 137.221.83.70 (137.221.83.70) 25.725 ms 25.761 ms 25.772 ms
6 137.221.65.66 (137.221.65.66) 25.524 ms 25.812 ms 25.797 ms
7 137.221.74.32 (137.221.74.32) 25.487 ms 25.806 ms 25.804 ms
8 * eqix-da1.nextlinkbroadband-2. com (206.223.118.192) 25.897 ms 25.941 ms
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *

07/12/2018 21:07:13 UTC

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

— 52.128.56.140 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 2998ms

07/12/2018 21:07:15 UTC

MTR:
Start: Fri Dec 7 21:07:05 2018 Blizzard 1.|-- Blizzard 0.0% 10 0.5 0.5 0.3 1.1 0.0 Blizzard 0.0% 10 0.8 0.7 0.5 1.1 0.0
3.|-- 137.221.105.10 0.0% 10 0.8 0.8 0.6 0.9 0.0
4.|-- 137.221.66.16 0.0% 10 0.9 0.7 0.5 0.9 0.0
5.|-- 137.221.83.70 0.0% 10 25.8 25.7 25.5 25.9 0.0
6.|-- 137.221.65.66 0.0% 10 25.9 25.7 25.5 26.0 0.0
7.|-- 137.221.74.32 20.0% 10 26.5 25.9 25.5 26.5 0.0
8.|-- eqix-da1.nextlinkbroadband-2. com 10.0% 10 26.1 26.0 25.5 27.8 0.5
9.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

07/12/2018 21:07:05 UTC

MTR:
Start: Fri Dec 7 21:07:05 2018 Blizzard 1.|-- Blizzard 0.0% 10 0.4 0.4 0.3 0.5 0.0 Blizzard 0.0% 10 0.6 0.7 0.6 1.0 0.0
3.|-- 137.221.105.10 0.0% 10 0.7 0.7 0.5 1.0 0.0
4.|-- 137.221.66.16 0.0% 10 0.8 0.7 0.6 0.8 0.0
5.|-- 137.221.83.70 0.0% 10 25.6 29.5 25.5 54.1 8.9
6.|-- 137.221.65.66 0.0% 10 25.9 25.8 25.6 26.0 0.0
7.|-- 137.221.74.32 10.0% 10 25.9 25.6 25.4 25.9 0.0
8.|-- eqix-da1.nextlinkbroadband-2. com 10.0% 10 25.8 25.9 25.6 26.7 0.0
9.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

07/12/2018 21:07:05 UTC

MTR:
Start: Fri Dec 7 21:07:09 2018 Blizzard 1.|-- Blizzard 0.0% 10 0.4 0.3 0.2 0.5 0.0 Blizzard 0.0% 10 0.6 0.7 0.5 1.0 0.0
3.|-- 137.221.105.10 0.0% 10 0.6 0.6 0.5 0.8 0.0
4.|-- 137.221.66.16 0.0% 10 0.7 1.0 0.6 4.2 0.9
5.|-- 137.221.83.70 0.0% 10 25.8 34.6 25.6 92.0 20.7
6.|-- 137.221.65.66 0.0% 10 25.5 35.0 25.5 119.3 29.6
7.|-- 137.221.74.32 0.0% 10 27.0 25.8 25.3 27.0 0.5
8.|-- eqix-da1.nextlinkbroadband-2. com 0.0% 10 25.8 25.9 25.7 26.8 0.0
9.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

07/12/2018 21:07:09 UTC

MTR:
Start: Fri Dec 7 21:07:10 2018 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.5 0.3 1.3 0.0 Blizzard 0.0% 10 0.8 0.7 0.5 1.0 0.0
3.|-- 137.221.105.10 0.0% 10 0.6 0.8 0.6 1.2 0.0
4.|-- 137.221.66.16 0.0% 10 0.7 0.7 0.5 0.9 0.0
5.|-- 137.221.83.70 0.0% 10 32.4 30.8 25.7 60.9 10.9
6.|-- 137.221.65.66 0.0% 10 25.7 26.0 25.5 26.9 0.0
7.|-- 137.221.74.32 20.0% 10 25.5 25.6 25.4 25.8 0.0
8.|-- eqix-da1.nextlinkbroadband-2. com 10.0% 10 25.7 25.8 25.6 26.0 0.0
9.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

07/12/2018 21:07:10 UTC

[Sanctimonia-tichondrius]

Same, Cableone Mississippi. Unplayable.

I would also like to add that the latency will “settle” then as soon as anything remotely intense happens - bam 21,000ms … yeah… 5,000ms is now small fries. It goes that high. I’ve seen it.

The WinMTRs repeatedly show Dallas or something with the name “Dallas” being a monstrous hiccup in latency, but not the to point of DC, just 21,000ms.

[Subfocus-ragnaros]

hey blizzard hope u can fix this

[Kojage-nazjatar]

Hey, can you do a trace to 24.105.62.129 for me real quick? I want to see where it goes. I have a ticket open with Level3 and heck at this point I’ll pretend you’re my customer just to give them more traces.

[Bleezus-nazjatar]

Woops, was on an alt.

[Kurozuma-zuljin]

Hi there,
Having issues since this morning with high latency on Zul’Jin(US). My ping usually sits around 30-50ms and now it’s stuck around 140-150ms.
ISP: Altima Telecom
I’m from Gatineau, QC ( Canada )
Here’s my WinMTR:

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                             192.168.0.1 -    0 | 1076 | 1076 |    0 |    0 |    2 |    0 |
|                           199.241.132.1 -    0 | 1076 | 1076 |    4 |   13 |   96 |   10 |
|                           10.170.192.58 -    1 | 1072 | 1071 |    7 |   13 |   34 |   18 |
|                  ip41265d25.globale.net -   76 |  267 |   65 |    0 |   16 |   29 |   16 |
|                  ip41265de5.globale.net -   89 |  236 |   26 |    0 |   16 |   21 |   17 |
|   be4834.rcr21.ymq02.atlas.cogentco.com -    0 | 1076 | 1076 |    8 |   14 |   31 |   13 |
|hu0-4-0-1.ccr21.ymq01.atlas.cogentco.com -    0 | 1076 | 1076 |    7 |   14 |   34 |   13 |
|   be2088.ccr21.alb02.atlas.cogentco.com -    0 | 1076 | 1076 |   13 |   19 |   45 |   19 |
|   be2915.ccr41.jfk02.atlas.cogentco.com -    0 | 1076 | 1076 |   15 |   22 |   43 |   22 |
|   be3362.ccr31.jfk04.atlas.cogentco.com -    0 | 1076 | 1076 |   16 |   22 |   47 |   23 |
|be2556.rcr11.b001587-1.jfk04.atlas.cogentco.com -    0 | 1076 | 1076 |   17 |   23 |   46 |   22 |
|                            38.88.194.29 -    0 | 1076 | 1076 |   19 |   25 |   51 |   23 |
|              ae1-br01-eqny8.as57976.net -    0 | 1072 | 1072 |  132 |  145 | 4629 |  138 |
|         et-0-0-2-br02-eqch2.as57976.net -    1 | 1047 | 1042 |    0 |   57 | 4839 |   71 |
|              be2-pe02-eqch2.as57976.net -    1 | 1068 | 1066 |  130 |  136 |  157 |  137 |
|        chi-eqch2-ia-bons-04.as57976.net -    1 | 1057 | 1052 |  133 |  139 |  159 |  139 |
|                           24.105.62.129 -    1 | 1065 | 1062 |  131 |  136 |  154 |  134 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

By the way, why is my route going from New York to Georgia then Amsterdam(Netherlands)? Wtf lol
Thank you.

[Vudumajik-area-52]

Im in MS with cable one as well. I downloaded a vpn and can play fine. I suggest you do the same until this gets fixed. Nordvpn is offering a free 7 day trial and then after that you have to pay. It sucks but unless you get the 2 year sub, you’ll have to pay 11$ a month for it which almost doubles your wow sub…the things we do to play this game…lol

[Schaeffer-wyrmrest-accord]

In southern Miss, also Cableone. Can barely play, the spikes get so bad. Gotten up to 6k world while my home is 50.

[Platos-azuremyst]

In Texas and also having the same issue. My ISP is NextLink. Been like this for the week. I’m actually still really enjoying the game but this is the kind of thing that will force me to unsub and it seems to be affecting a lot of users.

[Twinkle-wyrmrest-accord]

Also in Texas, ever since the background patch for 8.1 started and finished on tuesday, the game has had incredible lag spikes. Particularly in raids, i will sit at 30 ping, and when the boss is pulled, it shoots to 5k ping, completely unplayable.

[Malise-cairne (Malise)]

South Western Arkansas and also experiencing this.

[Platos-azuremyst]

This does appear to be connected to sharding as well. Some shards I’m getting perfection connection. Then as soon as I phase…700ms. I’m in Waxahachie TX, on NextLink. Please fix this ASAP. Connection issues will force people away from the game. I stopped playing Fortnite for similar issues. This has to be resolved.

[Itsuki-drenden (Itsuki)]

I won’t recommend one myself, but one I saw mentioned by a user in Customer Support was this one.

Stuck character!

It’s worth a shot. I think the one people were using (that had a free trial) was called Tunnel Bear. https://www.tunnelbear.com/