Same here. I actually got kicked from the game on the day Visions launched, the lag was so bad on my server. I disabled all my add-ons, thinking that was the issue. It didn’t do anything. I’ve noticed it mainly happens to me when I’m going from one location to the next, when the text pops up. My boyfriend, whom I live with, says nothing is going on with his gameplay, and he has all his add-ons enabled still. We’re in the same house, on the same servers, on the same router, and we aren’t playing at the same time. So I have no idea, but it has made my dailies almost impossible. Haven’t even thought of trying to do a dungeon. The fact that it’s been going on a week for me, and isn’t a “known issue” for Visions is a bit discouraging.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| dsldevice.attlocal.net - 0 | 359 | 359 | 0 | 0 | 2 | 0 |
|104-186-20-1.lightspeed.chrlnc.sbcglobal.net - 0 | 360 | 360 | 1 | 4 | 17 | 2 |
| 99.144.25.246 - 0 | 360 | 360 | 1 | 2 | 11 | 2 |
| 99.133.205.118 - 0 | 360 | 360 | 1 | 3 | 555 | 2 |
| 12.83.102.145 - 0 | 360 | 360 | 2 | 4 | 7 | 5 |
| 12.122.154.134 - 0 | 360 | 360 | 8 | 11 | 18 | 14 |
| 12.123.43.197 - 0 | 360 | 360 | 7 | 7 | 9 | 8 |
| 12.247.68.74 - 0 | 360 | 360 | 7 | 12 | 147 | 11 |
| ae1-br01-eqat2.as57976.net - 4 | 318 | 308 | 28 | 38 | 109 | 57 |
| et-0-0-4-br02-eqch2.as57976.net - 3 | 324 | 315 | 27 | 61 | 1290 | 57 |
| be2-pe1-eqch2.as57976.net - 3 | 331 | 324 | 28 | 36 | 59 | 57 |
| 24.105.62.129 - 5 | 308 | 295 | 28 | 37 | 65 | 58 |
|____________|||||||
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Normally get 30 ms, but today it’s been a constant 60-300 ms. Other players reporting the same thing.
Lag was just isolated to Vale yesterday, but today it’s been bad everywhere. Ran a tracert and the slow down appears to be occurring on Bliz server.
Either way, game is borderline unplayable, so I logged off. Guess that’s their plan for fixing this?
Same here in Fort Worth, TX - holding around 150ms world.
Add me to the list of affected players. Game keeps locking up, 3-5 seconds at a time. ms is off the charts, up and down. Playing is awful.
Just to try and help support out.
Charlotte NC area, AT&T Fiber (1 GB). Local ping looks like 20-30ms on an EST server (Thrall-US). World MS ranges from 100-200ms. Getting bad stuttering and delayed effects.
I suppose the next step would be to post WinMTR logs so that they can analyze the routing. Although, just taking a quick glance and asking others while in raids/instances, it doesn’t seem to affect everyone. In fact, the majority of the posts are from CST or PST server locations, with exception to the few on EST. So the likely culprit is possibly a hand off at one of these server locations.
TRACEROUTE:
traceroute to Blizzard Blizzard, 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.350 ms 0.354 ms 0.359 ms
2 24.105.18.131 (24.105.18.131) 0.662 ms 0.774 ms 0.900 ms
3 137.221.105.16 (137.221.105.16) 0.915 ms 0.921 ms 0.927 ms
4 137.221.66.22 (137.221.66.22) 1.086 ms 1.122 ms 1.130 ms
5 137.221.83.68 (137.221.83.68) 5.956 ms 5.974 ms 5.980 ms
6 137.221.65.68 (137.221.65.68) 5.816 ms 5.811 ms 5.883 ms
7 137.221.68.32 (137.221.68.32) 27.027 ms 26.453 ms 26.417 ms
8 12.245.64.9 (12.245.64.9) 5.726 ms 6.243 ms 6.237 ms
9 * * *
10 * * *
11 * * *
12 99.24.64.169 (99.24.64.169) 48.040 ms 47.981 ms 49.171 ms
13 * * *
14 * * *
15 * * *
22/01/2020 23:47:22 UTC
--------------------
TRACEROUTE:
traceroute to Blizzard Blizzard, 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.322 ms 0.302 ms 1.180 ms
2 24.105.18.131 (24.105.18.131) 0.597 ms 0.685 ms 0.768 ms
3 137.221.105.16 (137.221.105.16) 0.846 ms 0.863 ms 0.953 ms
4 137.221.66.22 (137.221.66.22) 1.177 ms 1.687 ms 1.709 ms
5 137.221.83.68 (137.221.83.68) 56.048 ms 56.098 ms 56.113 ms
6 137.221.65.68 (137.221.65.68) 5.911 ms 5.804 ms 13.725 ms
7 137.221.68.32 (137.221.68.32) 5.861 ms 5.897 ms 6.235 ms
8 12.245.64.9 (12.245.64.9) 5.866 ms 6.027 ms 6.043 ms
9 * * *
10 * * *
11 * * *
12 99.24.64.169 (99.24.64.169) 48.163 ms 48.177 ms 48.070 ms
13 * * *
14 * * *
15 * * *
22/01/2020 23:47:22 UTC
--------------------
PING:
PING Blizzard Blizzard 56(84) bytes of data.
--- Blizzardping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 2998ms
22/01/2020 23:47:22 UTC
--------------------
PING:
PING Blizzard Blizzard 56(84) bytes of data.
--- Blizzardping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 2999ms
22/01/2020 23:47:22 UTC
--------------------
TRACEROUTE:
traceroute to Blizzard Blizzard, 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.323 ms 0.351 ms 1.514 ms
2 24.105.18.131 (24.105.18.131) 0.583 ms 0.683 ms 0.793 ms
3 137.221.105.16 (137.221.105.16) 1.024 ms 1.047 ms 1.140 ms
4 137.221.66.22 (137.221.66.22) 1.516 ms 1.529 ms 1.542 ms
5 137.221.83.68 (137.221.83.68) 6.673 ms 6.698 ms 6.724 ms
6 137.221.65.68 (137.221.65.68) 6.621 ms 7.672 ms 7.619 ms
7 137.221.68.32 (137.221.68.32) 65.951 ms 65.985 ms 65.997 ms
8 12.245.64.9 (12.245.64.9) 7.507 ms 7.542 ms 7.577 ms
9 * * *
10 * * *
11 * * *
12 99.24.64.169 (99.24.64.169) 48.198 ms 48.226 ms 48.228 ms
13 * * *
14 * * *
15 * * *
22/01/2020 23:47:27 UTC
--------------------
PING:
PING Blizzard Blizzard 56(84) bytes of data.
--- Blizzardping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 3012ms
22/01/2020 23:47:27 UTC
--------------------
TRACEROUTE:
traceroute to Blizzard Blizzard, 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.676 ms 0.669 ms 0.717 ms
2 24.105.18.131 (24.105.18.131) 1.927 ms 1.989 ms 2.058 ms
3 137.221.105.16 (137.221.105.16) 1.999 ms 2.012 ms 2.025 ms
4 137.221.66.22 (137.221.66.22) 1.895 ms 1.956 ms 1.972 ms
5 137.221.83.68 (137.221.83.68) 6.098 ms 6.153 ms 6.171 ms
6 137.221.65.68 (137.221.65.68) 7.331 ms 5.859 ms 5.873 ms
7 137.221.68.32 (137.221.68.32) 6.168 ms 6.034 ms 6.024 ms
8 12.245.64.9 (12.245.64.9) 5.904 ms 5.936 ms 5.949 ms
9 * * *
10 * * *
11 * * *
12 99.24.64.169 (99.24.64.169) 48.010 ms 48.151 ms 48.434 ms
13 * * *
14 * * *
15 * * *
22/01/2020 23:47:31 UTC
--------------------
PING:
PING Blizzard Blizzard 56(84) bytes of data.
--- Blizzardping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 2998ms
22/01/2020 23:47:33 UTC
--------------------
MTR:
Start: Wed Jan 22 23:47:22 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.6 1.1 0.4 4.5 1.3
2.|-- 24.105.18.131 0.0% 10 0.7 1.2 0.7 3.2 0.7
3.|-- 137.221.105.16 0.0% 10 0.9 1.7 0.8 8.9 2.5
4.|-- 137.221.66.22 0.0% 10 1.1 5.3 1.0 40.0 12.2
5.|-- 137.221.83.68 0.0% 10 5.8 12.2 5.7 63.8 18.2
6.|-- 137.221.65.68 0.0% 10 20.8 12.0 5.8 40.4 11.3
7.|-- 137.221.68.32 0.0% 10 6.3 6.1 5.9 6.3 0.0
8.|-- 12.245.64.9 0.0% 10 29.7 10.4 5.7 29.7 9.5
9.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
11.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
12.|-- 99.24.64.169 0.0% 10 71.8 53.4 48.1 72.7 10.0
13.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
22/01/2020 23:47:22 UTC
--------------------
MTR:
Start: Wed Jan 22 23:47:22 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.4 0.6 0.4 2.8 0.7
2.|-- 24.105.18.131 0.0% 10 0.6 0.9 0.5 3.5 0.7
3.|-- 137.221.105.16 0.0% 10 0.9 1.0 0.9 1.2 0.0
4.|-- 137.221.66.22 0.0% 10 1.0 21.1 1.0 123.7 41.8
5.|-- 137.221.83.68 0.0% 10 6.0 7.5 5.8 16.4 3.2
6.|-- 137.221.65.68 0.0% 10 17.7 12.4 5.7 36.8 9.6
7.|-- 137.221.68.32 0.0% 10 6.1 6.9 5.8 13.2 2.2
8.|-- 12.245.64.9 0.0% 10 31.1 10.5 5.8 31.1 9.9
9.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
11.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
12.|-- 99.24.64.169 0.0% 10 70.9 52.9 48.2 71.7 9.7
13.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
22/01/2020 23:47:22 UTC
--------------------
TRACEROUTE:
traceroute to Blizzard Blizzard, 15 hops max, 60 byte packets
1 Blizzard Blizzard 1.820 ms 1.789 ms 1.785 ms
2 24.105.18.3 (24.105.18.3) 2.692 ms 2.708 ms 2.709 ms
3 137.221.105.12 (137.221.105.12) 2.738 ms 2.744 ms 2.749 ms
4 137.221.66.20 (137.221.66.20) 2.739 ms 2.742 ms 2.741 ms
5 137.221.83.68 (137.221.83.68) 7.607 ms 7.618 ms 7.618 ms
6 137.221.65.68 (137.221.65.68) 7.377 ms 6.285 ms 6.259 ms
7 137.221.68.32 (137.221.68.32) 6.248 ms 5.960 ms 5.942 ms
8 12.245.64.9 (12.245.64.9) 5.845 ms 6.283 ms 6.268 ms
9 * * *
10 * * *
11 * * *
12 99.24.64.169 (99.24.64.169) 47.992 ms 48.076 ms 48.083 ms
13 * * *
14 * * *
15 * * *
22/01/2020 23:47:38 UTC
--------------------
MTR:
Start: Wed Jan 22 23:47:27 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.4 0.6 0.4 1.2 0.0
2.|-- 24.105.18.131 0.0% 10 0.9 0.7 0.6 0.9 0.0
3.|-- 137.221.105.16 0.0% 10 1.2 1.0 0.8 1.2 0.0
4.|-- 137.221.66.22 0.0% 10 1.0 4.6 0.9 26.3 8.1
5.|-- 137.221.83.68 0.0% 10 6.1 6.7 5.7 12.5 2.0
6.|-- 137.221.65.68 0.0% 10 6.3 13.6 5.9 49.1 13.6
7.|-- 137.221.68.32 0.0% 10 5.9 6.2 5.9 6.9 0.0
8.|-- 12.245.64.9 0.0% 10 5.9 15.4 5.8 32.1 12.3
9.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
11.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
12.|-- 99.24.64.169 0.0% 10 48.6 58.4 48.1 75.7 12.8
13.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
22/01/2020 23:47:27 UTC
--------------------
PING:
PING Blizzard Blizzard 56(84) bytes of data.
--- Blizzardping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 3001ms
22/01/2020 23:47:38 UTC
--------------------
MTR:
Start: Wed Jan 22 23:47:28 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.4 0.7 0.4 1.3 0.0
2.|-- 24.105.18.131 0.0% 10 1.1 1.4 0.6 4.7 1.2
3.|-- 137.221.105.16 0.0% 10 0.9 1.1 0.8 1.3 0.0
4.|-- 137.221.66.22 0.0% 10 1.3 5.5 1.1 26.3 8.3
5.|-- 137.221.83.68 0.0% 10 6.0 8.1 5.9 16.9 4.3
6.|-- 137.221.65.68 0.0% 10 6.2 8.0 5.8 16.8 4.0
7.|-- 137.221.68.32 0.0% 10 6.2 6.3 6.0 6.5 0.0
8.|-- 12.245.64.9 0.0% 10 5.9 15.6 5.8 32.2 12.1
9.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
11.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
12.|-- 99.24.64.169 0.0% 10 49.0 58.9 48.3 75.7 12.4
13.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
22/01/2020 23:47:28 UTC
--------------------
TRACEROUTE:
traceroute to Blizzard Blizzard, 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.283 ms 0.256 ms 0.259 ms
2 24.105.18.3 (24.105.18.3) 2.818 ms 2.841 ms 2.845 ms
3 137.221.105.12 (137.221.105.12) 0.905 ms 0.955 ms 0.963 ms
4 137.221.66.20 (137.221.66.20) 0.967 ms 1.475 ms 1.500 ms
5 137.221.83.68 (137.221.83.68) 5.840 ms 5.860 ms 5.868 ms
6 137.221.65.68 (137.221.65.68) 5.744 ms 5.804 ms 5.793 ms
7 137.221.68.32 (137.221.68.32) 5.807 ms 5.803 ms 6.176 ms
8 12.245.64.9 (12.245.64.9) 5.627 ms 5.658 ms 5.704 ms
9 * * *
10 * * *
11 * * *
12 99.24.64.169 (99.24.64.169) 48.100 ms 48.257 ms 48.263 ms
13 * * *
14 * * *
15 * * *
22/01/2020 23:47:42 UTC
--------------------
PING:
PING Blizzard Blizzard 56(84) bytes of data.
--- Blizzardping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 2998ms
22/01/2020 23:47:42 UTC
--------------------
MTR:
Start: Wed Jan 22 23:47:35 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.4 0.4 0.3 0.8 0.0
2.|-- 24.105.18.131 0.0% 10 0.6 0.7 0.5 1.2 0.0
3.|-- 137.221.105.16 0.0% 10 0.9 2.0 0.8 12.1 3.5
4.|-- 137.221.66.22 0.0% 10 1.0 2.5 0.9 15.5 4.5
5.|-- 137.221.83.68 0.0% 10 5.7 10.8 5.7 46.6 12.8
6.|-- 137.221.65.68 0.0% 10 5.8 16.0 5.7 60.5 19.4
7.|-- 137.221.68.32 0.0% 10 6.1 6.3 5.9 7.5 0.3
8.|-- 12.245.64.9 0.0% 10 33.1 8.6 5.8 33.1 8.6
9.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
11.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
12.|-- 99.24.64.169 0.0% 10 72.0 50.7 48.1 72.0 7.5
13.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
22/01/2020 23:47:35 UTC
--------------------
MTR:
Start: Wed Jan 22 23:47:38 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.3 0.5 0.0
2.|-- 24.105.18.3 0.0% 10 0.6 0.6 0.5 0.7 0.0
3.|-- 137.221.105.12 0.0% 10 1.0 0.9 0.7 1.1 0.0
4.|-- 137.221.66.20 0.0% 10 0.9 8.9 0.9 61.0 19.2
5.|-- 137.221.83.68 0.0% 10 6.6 13.6 5.7 37.7 12.6
6.|-- 137.221.65.68 0.0% 10 5.7 13.6 5.7 62.4 18.3
7.|-- 137.221.68.32 0.0% 10 5.9 5.9 5.8 6.0 0.0
8.|-- 12.245.64.9 10.0% 10 32.9 14.0 5.7 33.6 12.6
9.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
11.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
12.|-- 99.24.64.169 0.0% 10 76.8 58.7 48.1 76.8 13.6
13.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
22/01/2020 23:47:38 UTC
--------------------I too have had bad lag issues since Tuesday reset. I have verified issue is not on my end. No connection/lag issues for many other games / sites.
Same here. In Panda Land this morning and in the middle of killing a mob, I noticed that the mobs health wasn’t moving and I wasn’t getting hit. Realized that the game just locked up. Wouldn’t let me exit game. Had to exit thru ctr+alt+del. I just thought I needed to delete cache again. I noticed in my wow retail folder there was a new one called “blob_storage”. Wth is blob storage? Also, there are 2 error folders. I tried to share/copy/paste the screen shot but I’m getting older (50 lol) and I cant figure out how to share the screen shot. TIA 
Howdy!
Everyone in this thread is utilizing AT&T U-verse. Can you please run a WinMTR for 10 minutes during this issue and report back the results here for us to review! It would help us track this issue down faster as it appears to be a ISP handoff issue.
Thank you.
It’s not your internet. It is Blizzards server. We now have a latency of 3000 here in Australia, and our friends at home in the US are in the red also. Think the servers need to be re-started maybe?
Biggums please start your own thread with a WinMTR. This is not related to your ISP that we are aware of. We do not have any outstanding world wide issues. Our goal here in this thread is to help track down the AT&T U-verse issue. If we find it’s linked to other ISPs due to the route we certainly will update this thread. Thanks.
1 Like
WinMTR Statistics
WinMTR statistics
| Host | % | Sent | Recv | Best | Avrg | Wrst | Last |
| dsldevice.attlocal.net | 0 | 586 | 586 | 0 | 0 | 1 | 0 |
| 99-95-188-1.lightspeed.brhmal.sbcglobal.net | 6 | 479 | 452 | 16 | 27 | 618 | 18 |
| 99.173.217.64 | 6 | 487 | 461 | 18 | 26 | 642 | 20 |
| 99.133.13.102 | 6 | 475 | 447 | 0 | 31 | 622 | 23 |
| 12.83.101.137 | 5 | 495 | 472 | 22 | 32 | 619 | 25 |
| 12.123.43.197 | 4 | 511 | 492 | 24 | 34 | 625 | 26 |
| 12.247.68.74 | 2 | 551 | 542 | 25 | 38 | 578 | 27 |
| ae1-br01-eqat2.as57976.net | 7 | 463 | 432 | 42 | 50 | 238 | 43 |
| et-0-0-4-br02-eqch2.as57976.net | 6 | 475 | 447 | 42 | 55 | 582 | 43 |
| be2-pe2-eqch2.as57976.net | 3 | 535 | 522 | 42 | 50 | 665 | 43 |
| 24.105.62.129 | 4 | 511 | 492 | 0 | 52 | 636 | 44 |
Ok. I am sooooooooo aggrivated atm. I did the WinMTR, went to Pastebin and I must have not done it correctly because it will not let me paste the results. It says links are not allowed. I’m NOT tech savvy and feel stupid so I need some help. The last 2/3 WoW updates have really screwed the game for me and I’m trying to do what has been suggested but I cant figure out the simplest crap! Signed: Frustrated
Seems that Blizz is “working on it”. I cancelled my sub until it’s fixed.
1 Like
you can either post the entire pastebin link, then highlight it and click the preformatted text button at the top of the reply box that looks like this </>, or you can just post the letters at the end of the pastebin link
I have been having disconnects/low framerate, so I went to delete the cache (I have been doing this daily for about 1 week). There were some folders under “retail” that I am unfamiliar with and curious about. I am so not computer savvy =) so I was hoping someone can help me. 2 screen shots to follow.
sigh I cannot get it copied/pasted or otherwise shared, but, it shows in the “retail” folder: blob_storage, the usual cache, wtf, etc and 2 error folders. Is this normal?