[Verizon ISP] Lag Spikes - Worse When in Dungeon

Support Technical Support
21

Same issues, Virginia Verizon Fios

1 Like
22

Same its terrible.

NJ fios

23

Same issue here, Wired connection, Pennsylvania, Verizon Fios

24

|------------------------------------------------------------------------------------------|
| WinMTR statistics |

Host - % Sent Recv Best Avrg Wrst Last
192.168.1.1 - 0 293 293 0 0 6 0
tukw-dsl-gw67.tukw.qwest.net - 0 293 293 2 4 54 25
tukw-agw1.inet.qwest.net - 0 293 293 2 5 43 3
4.68.38.173 - 99 59 1 0 4 4 4
No response from host - 100 58 0 0 0 0 0
4.7.26.166 - 0 293 293 30 34 102 31
**ae1-br01-csla1.as57976.net - 0 293 293 33 86 637 35
No response from host - 100 58 0 0 0 0 0
No response from host - 100 58 0 0 0 0 0
et-0-0-0-pe01-swlv10.as57976.net - 0 293 293 34 35 62 36
137.221.105.2 - 0 293 293 33 34 70 35
________________________________________________ ______ ______ ______ ______ ______ ______

WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

25

Same issues here, east coast Verizon Fios ISP.

26

same here maryland verizon fios have been 5 days

1 Like
28

Maryland Verizon Malganis issues. Especially in dungeons

29

Throwing my name into the hat as well. Huge latency spikes in dungeons. I am normally completely smooth. Earlier today was fine, but the evening is rough. This isn’t normal for my connection.

30

Same type of issue here, Verizon FIOS in NY. It started Saturday evening and has been occuring every day typically during peak play times - late afternoon until around 11PM or midnight. No issues with connection outside of WoW. Traceroute:

1 <1 ms <1 ms <1 ms G3100.mynetworksettings.com [192.168.1.1]
2 4 ms 1 ms 2 ms lo0-100.BFLONY-VFTTP-302.verizon-gni.net [72.75.232.1]
3 3 ms 4 ms 4 ms 100.41.26.86
4 12 ms 13 ms 10 ms 0.csi1.BFLONYFR-MSE01-BB-SU1.ALTER.NET [140.222.10.44]
5 * * * Request timed out.
6 19 ms 21 ms 19 ms nyk-bb2-link.ip.twelve99.net [62.115.137.98]
7 22 ms 21 ms 20 ms chi-b23-link.ip.twelve99.net [62.115.137.59]
8 21 ms 21 ms 22 ms blizzard-ic348622-chi-b23.ip.twelve99-cust.net [62.115.178.249]
9 540 ms 883 ms 436 ms ae1-br02-eqch2.as57976.net [137.221.69.35]
10 22 ms 21 ms 20 ms et-0-0-1-pe01-eqch2.as57976.net [137.221.69.51]
11 23 ms 23 ms 23 ms 24.105.62.129

31

Good to know I’m not going crazy! Been having major lag spikes (going up to 600 world MS) Fios Gig Connection - East Coast - PA. Hoping they fix this soon!

32

Same. Pittsburgh, PA East Coast Verizon Fios Gig speed. ISP says its not them, its you. WoW says its not them its Verizon…I am not in the mood for the back and forth excuses…where its pointing fingers at each other. Figure it out.

33

Blizzard please provide an update on this issue. Trying to run dungeons before end of season and this is preventing me from doing so.

34

This has been happening for days for me

35

Same issue here. This looks a lot like the peering issue from a few years back that only affected Verizon FIOS users in the greater DC area. I believe when all was said and done it was some sort of peering issue involving Blizzard, Verizon, and L3? But I have no idea who we had to contact to get it fixed. If I recall, Blizzard said it wasn’t a problem on their end and Verizon said it wasn’t a problem on their end.

36

I remember that, it was Warlords of Draenor. I was progging the mythic train boss at the time at 1K MS

37

Same here. 1gb/s; USE, Connecticut. Happened a few months ago too

38

24.105.62.129 (US Central) is hosed. Getting high ping and tons of packet loss from:

4.68.38.173
ae1-br01-csla1.as57976.net
137.221.65.133

39

Ditto on this.

40

Just adding on as to having same problems with massive lag spikes the past couple of days. East Coast (Maryland) Verizon.

41

Another Fios person on the East Coast, experienced a ton of lag in raids tonight while speed tests said my internet was fine.

I remember this happening during TK in TBC Classic and when I talked to the tech at Blizzard they acknowledged it was an issue, but it was one of those things that each company hoped the other would fix it as it was a weird technical issue each company wasn’t sure who’s job it was to fix it. It cleared up a couple days afterwards, but its just disappointing it to happen again and again.