×

Switch Account

Excessive Slowness/Latency with Netflix, World of Warcraft, browsing in general...

Excessive Slowness/Latency with Netflix, World of Warcraft, browsing in general...

Reply
Contributor
Contributor
Posts: 2
Registered: ‎02-10-2013

Excessive Slowness/Latency with Netflix, World of Warcraft, browsing in general...

Message 1 of 20
(5,907 Views)

Hi there,

 

For the last few days I've been experiencing extreme slowness and latency when, primarly, using Netflix and World of Warcraft, but today the issue has graduated to web browsing as well. It's taking sites MINUTES to load - including the Verizon forums themselves.

 

For reference, I'm a FiOS 20/5 user in Germantown, MD (Montomery County) and have been since May 2009. I've done a number of speed tests using Speakeasy.net, and the averge of those speed tests in the last two house is 3.92 down, 4.01 up, so DL is well below promised speeds.

 

Here's a list of issues, per application/task:

 

  • Netflix: Loading movies/tv shows takes as much as 3 minutes to load in HD, and as quickly as about 25 seconds. Normally a movie is loaded in less than 10 seconds.
  • World of Warcraft: Logging in takes longer than normal by 40-50 seconds, and in game my "World" latency is between 5600ms and 22000ms (22000ms happened just 30 minutes ago).
  • Web Browsing: Some sites, like the Washington Post and CNN, come up relatively quickly. Other sites, like Verizon's message boards, Battle.net, Speakeasy.net, and even Facebook, are taking several minutes to load in some cases.

I've rebooted my router/modem several times over the last few days, to no avail. I've also done a pathping and tracert to my server (Aggramar in the Vindication Battle Group) in World of Warcraft. Here are the results:

 

******* TRACEROUTE *******

1 192.168.1.1 (192.168.1.1) 1.399 ms 1.061 ms 7.617 ms
2 l100.washdc-vfttp-92.verizon-gni.net (71.191.59.1) 8.171 ms 10.010 ms 6.793 ms
3 g0-12-3-6.washdc-lcr-21.verizon-gni.net (130.81.184.172) 12.986 ms 36.828 ms 9.716 ms
4 ae1-0.res-bb-rtr1.verizon-gni.net (130.81.209.206) 14.963 ms 85.361 ms 9.823 ms
5 0.xe-4-3-0.br1.iad8.alter.net (152.63.37.37) 47.622 ms 10.271 ms 9.527 ms
6 192.205.36.141 (192.205.36.141) 20.133 ms 19.443 ms 25.278 ms
7 cr2.wswdc.ip.att.net (12.122.81.250) 84.665 ms 66.571 ms 83.375 ms
8 cr1.cgcil.ip.att.net (12.122.18.21) 48.891 ms 38.524 ms 58.928 ms
9 gar2.clboh.ip.att.net (12.122.133.197) 31.891 ms 32.250 ms 32.486 ms
10 12.122.251.22 (12.122.251.22) 35.875 ms
12.122.251.50 (12.122.251.50) 39.869 ms 48.805 ms
11 63.240.130.214 (63.240.130.214) 34.940 ms
63.240.130.210 (63.240.130.210) 49.196 ms
63.240.130.214 (63.240.130.214) 35.483 ms
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *

 

******* PATHPING *******

1 192.168.1.1 (192.168.1.1) 2.968 ms 1.658 ms 1.069 ms 1.047 ms 1.008 ms 1.337 ms * 1.811 ms 1.061 ms 1.445 ms 1.042 ms 1.114 ms * 4.489 ms 1.092 ms 1.100 ms 1.113 ms 1.096 ms * 1.476 ms 1.119 ms 1.084 ms 3.680 ms 1.163 ms * 1.265 ms 1.772 ms 1.127 ms 1.057 ms 1.086 ms (13% loss)
2 l100.washdc-vfttp-92.verizon-gni.net (71.191.59.1) 9.869 ms 7.069 ms 7.604 ms 7.495 ms 6.991 ms 7.904 ms 7.194 ms 11.779 ms 10.028 ms 13.831 ms 12.474 ms 9.471 ms 8.074 ms 9.665 ms 22.767 ms 25.168 ms 32.809 ms 34.267 ms 30.153 ms 12.742 ms 10.240 ms 26.973 ms 10.699 ms 12.046 ms 9.163 ms 7.425 ms 8.793 ms 8.790 ms 10.582 ms 9.862 ms (0% loss)
3 g0-12-3-6.washdc-lcr-21.verizon-gni.net (130.81.184.172) 12.592 ms 13.901 ms 13.005 ms 19.765 ms 12.504 ms 12.541 ms 10.163 ms 12.078 ms 11.020 ms 14.372 ms 12.143 ms 9.917 ms 17.539 ms 15.386 ms 12.040 ms 16.171 ms 28.646 ms 20.638 ms 31.021 ms 36.263 ms 23.430 ms 19.040 ms 16.819 ms 10.611 ms 18.151 ms 21.263 ms 12.655 ms 20.672 ms 8.898 ms 14.673 ms (0% loss)
4 ae1-0.res-bb-rtr1.verizon-gni.net (130.81.209.206) 83.840 ms 11.715 ms 13.333 ms 12.824 ms 16.690 ms 12.908 ms 11.454 ms 11.228 ms 13.864 ms 9.852 ms * 13.848 ms 74.805 ms 9.963 ms 12.962 ms 9.203 ms 12.126 ms 10.447 ms 11.111 ms 9.002 ms 10.120 ms 9.487 ms 12.359 ms 10.290 ms 9.659 ms 10.305 ms 83.398 ms 9.107 ms 10.049 ms 10.050 ms (3% loss)
5 0.xe-4-3-0.br1.iad8.alter.net (152.63.37.37) 14.147 ms 11.895 ms 10.550 ms 10.409 ms 12.447 ms 15.124 ms 14.517 ms 10.806 ms 12.735 ms 9.677 ms 29.863 ms 9.152 ms 10.815 ms 9.184 ms 12.939 ms 12.652 ms 9.327 ms 14.112 ms 13.453 ms 10.219 ms 12.959 ms 9.109 ms 10.510 ms 9.676 ms 10.366 ms 9.369 ms 10.451 ms 9.502 ms 10.534 ms 9.885 ms (0% loss)
6 192.205.36.141 (192.205.36.141) 107.239 ms 73.419 ms 54.305 ms 16.923 ms 19.083 ms 20.798 ms * * * 19.995 ms 21.496 ms 18.794 ms 14.604 ms 17.296 ms 19.813 ms 19.942 ms 20.241 ms * * 18.814 ms 17.251 ms 17.075 ms 22.967 ms 17.161 ms 22.118 ms * 17.078 ms 18.051 ms 16.859 ms 17.606 ms (20% loss)
7 cr2.wswdc.ip.att.net (12.122.81.250) 65.313 ms 64.606 ms * 66.313 ms 65.554 ms * * 89.827 ms * * * 73.216 ms * * 72.362 ms * * * * 75.951 ms 63.327 ms * 69.371 ms 75.155 ms 64.660 ms * 67.055 ms 64.164 ms 65.130 ms 75.601 ms (46% loss)
8 cr1.cgcil.ip.att.net (12.122.18.21) 38.223 ms 35.983 ms 39.759 ms 60.296 ms 57.101 ms 35.984 ms 39.282 ms 37.753 ms 34.437 ms 43.851 ms 44.660 ms 36.554 ms 37.646 ms 40.531 ms 40.615 ms 38.974 ms 34.739 ms 37.706 ms 34.684 ms 36.430 ms 38.708 ms 37.459 ms 35.088 ms 34.364 ms 51.147 ms 36.429 ms 37.805 ms 37.354 ms 64.718 ms 92.573 ms (0% loss)
9 gar2.clboh.ip.att.net (12.122.133.197) 32.992 ms 35.112 ms 37.067 ms 32.235 ms 32.656 ms 32.377 ms 32.816 ms 31.811 ms 36.422 ms * 32.513 ms 33.608 ms 31.274 ms 32.835 ms 34.706 ms 32.417 ms 32.798 ms 32.533 ms 32.458 ms 32.607 ms 33.562 ms 33.693 ms 32.552 ms 35.307 ms 32.052 ms 32.630 ms 33.514 ms 148.905 ms 97.397 ms 100.299 ms (3% loss)
10 12.122.251.22 (12.122.251.22) 36.889 ms 35.489 ms
12.122.251.50 (12.122.251.50) 34.619 ms 34.581 ms
12.122.251.22 (12.122.251.22) 34.804 ms 35.206 ms
12.122.251.50 (12.122.251.50) 34.517 ms
12.122.251.22 (12.122.251.22) 34.509 ms
12.122.251.50 (12.122.251.50) 37.670 ms 34.363 ms
12.122.251.22 (12.122.251.22) 34.575 ms 34.787 ms
12.122.251.50 (12.122.251.50) 35.371 ms 34.972 ms
12.122.251.22 (12.122.251.22) 37.767 ms 36.116 ms
12.122.251.50 (12.122.251.50) 37.809 ms 34.591 ms
12.122.251.22 (12.122.251.22) 34.921 ms 37.446 ms
12.122.251.50 (12.122.251.50) 34.498 ms 34.622 ms
12.122.251.22 (12.122.251.22) 35.542 ms *
12.122.251.50 (12.122.251.50) 33.996 ms 34.715 ms
12.122.251.22 (12.122.251.22) 35.018 ms 34.094 ms
12.122.251.50 (12.122.251.50) 37.660 ms 38.301 ms (3% loss)
11 63.240.130.210 (63.240.130.210) 36.562 ms
63.240.130.214 (63.240.130.214) 34.128 ms
63.240.130.210 (63.240.130.210) 35.411 ms
63.240.130.214 (63.240.130.214) 36.294 ms
63.240.130.210 (63.240.130.210) 34.890 ms 36.787 ms
63.240.130.214 (63.240.130.214) 34.993 ms
63.240.130.210 (63.240.130.210) 35.423 ms
63.240.130.214 (63.240.130.214) 39.446 ms
63.240.130.210 (63.240.130.210) 37.369 ms
63.240.130.214 (63.240.130.214) 33.780 ms
63.240.130.210 (63.240.130.210) 39.300 ms
63.240.130.214 (63.240.130.214) 35.413 ms 36.561 ms
63.240.130.210 (63.240.130.210) 37.898 ms
63.240.130.214 (63.240.130.214) 34.376 ms
63.240.130.210 (63.240.130.210) 37.256 ms
63.240.130.214 (63.240.130.214) 34.913 ms
63.240.130.210 (63.240.130.210) 34.075 ms
63.240.130.214 (63.240.130.214) 35.154 ms
63.240.130.210 (63.240.130.210) 34.489 ms 35.417 ms
63.240.130.214 (63.240.130.214) 33.914 ms
63.240.130.210 (63.240.130.210) 35.329 ms
63.240.130.214 (63.240.130.214) 34.595 ms
63.240.130.210 (63.240.130.210) 36.888 ms
63.240.130.214 (63.240.130.214) 34.954 ms
63.240.130.210 (63.240.130.210) 39.119 ms
63.240.130.214 (63.240.130.214) 38.512 ms 36.382 ms (0% loss)
12 * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * (100% loss)
13 * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * (100% loss)
14 * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * (100% loss)
15 * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * (100% loss)
16 * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * (100% loss)
17 * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * (100% loss)
18 * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * (100% loss)
19 * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * (100% loss)
20 * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * (100% loss)
21 * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * (100% loss)
22 * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * (100% loss)
23 * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * (100% loss)
24 * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * (100% loss)
25 * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * (100% loss)

 

 

****************************

Any information or assitance on how to fix this issue would be most appreciated.

 

Cheers,

 

Scott

19 REPLIES 19
Highlighted
Nickel Contributor
Nickel Contributor
Posts: 25
Registered: ‎03-12-2010

Re: Excessive Slowness/Latency with Netflix, World of Warcraft, browsing in general...

Message 2 of 20
(5,872 Views)

I hate to say it, but welcome to the club! Several people here posting similar issues. Been having this issue for just over 2 weeks now with no resolution from support.

Highlighted
Copper Contributor
Copper Contributor
Posts: 5
Registered: ‎02-10-2013

Re: Excessive Slowness/Latency with Netflix, World of Warcraft, browsing in general...

Message 3 of 20
(5,852 Views)

I have been having this as well for the past couple of weeks. Usually around 7pm to about 10 pm every day. I am in pennsylvania. The whole reason I got fios is because of online gaming. I run an online gaming clan. I usually get about a 40 ping to my game servers. Around the time it goes up to 200. 5 times higher. I still have a year left on my deal. Starting to feel ripped off.

Highlighted
Contributor
Contributor
Posts: 4
Registered: ‎02-09-2013

Re: Excessive Slowness/Latency with Netflix, World of Warcraft, browsing in general...

Message 4 of 20
(5,843 Views)

http://forums.verizon.com/t5/High-Speed-Internet-DSL-and-Dial/Can-t-connect-to-specific-site-at-cert...

 

I posted in here about what you are experiencing. It's affecting a lot of NYC Verizon users. Whereas my friends on other providers are not having any issues. I just don't understand what happened in the last few weeks that's causing this issue. It's tremendously annoying - I only use fios for gaming. If I can't game, what's the point of having fios?

Highlighted
Contributor
Contributor
Posts: 2
Registered: ‎02-10-2013

Re: Excessive Slowness/Latency with Netflix, World of Warcraft, browsing in general...

Message 5 of 20
(5,817 Views)

Same here.  There is a massive Sticky on the WoW Tech Support Forum.  Repeating my post there below, and posting a link to the forum.  PLEASE keep this bumped!

 

http://us.battle.net/wow/en/forum/topic/7864916450?page=17

 

 

Realm: Boulderfist (US)
Location: New York, NY (NY County)
Running FiOS 75/35 MBPS. Performance was excellent before a couple of days ago.

Notes/Issues, which occur sporadically (worse at night):

-Substantial (30+ second lag). or complete inability to connect.
-When I actually do log in, I often get (a) character not found or (b) no instance servers available errors.
-Sometimes cannot even connect to Blizzard websites (among other sites). I had substantial difficulty posting this.
-Sometimes, I CAN can log onto my toons on Aerie Peak (US), even when I can't get onto Boulderfist.

Traceroute and Pathping to Cyclone BG (for Boulderfist) immediately below. Traceroute and Pathping to Nightfall (for Aerie Peak) follows.

***

[code]Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.

TRACEROUTE

Tracing route to 12.129.209.68 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 2 ms 2 ms 2 ms L100.NYCMNY-VFTTP-224.verizon-gni.net [74.108.1.
1]
3 10 ms 7 ms 7 ms G0-14-4-6.NYCMNY-LCR-21.verizon-gni.net [130.81.
188.250]
4 51 ms 6 ms 6 ms ae0-0.NY325-BB-RTR2.verizon-gni.net [130.81.209.
110]
5 45 ms 44 ms 41 ms 0.xe-3-2-0.BR2.NYC4.ALTER.NET [152.63.20.213]
6 85 ms 87 ms 119 ms 192.205.34.49
7 81 ms 81 ms 75 ms cr1.n54ny.ip.att.net [12.122.86.6]
8 73 ms 75 ms 75 ms cr2.cgcil.ip.att.net [12.122.1.2]
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * 123 ms * gar29.la2ca.ip.att.net [12.122.129.241]
14 * * 121 ms 12-122-254-238.attens.net [12.122.254.238]
15 * 119 ms * mdf001c7613r0003-gig-12-1.lax1.attens.net [12.12
9.193.254]
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

 

 

PATHPING

Tracing route to 12.129.209.68 over a maximum of 30 hops

0 Christopher-PC.home [192.168.1.4]
1 Wireless_Broadband_Router.home [192.168.1.1]
2 L100.NYCMNY-VFTTP-224.verizon-gni.net [74.108.1.1]
3 G0-14-4-6.NYCMNY-LCR-21.verizon-gni.net [130.81.188.250]
4 ae0-0.NY325-BB-RTR2.verizon-gni.net [130.81.209.110]
5 * * 0.xe-3-2-0.BR2.NYC4.ALTER.NET [152.63.20.213]
6 192.205.34.49
7 cr1.n54ny.ip.att.net [12.122.86.6]
8 cr2.cgcil.ip.att.net [12.122.1.2]
9 cr1.cgcil.ip.att.net [12.122.2.53]
10 * * *
Computing statistics for 225 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Christopher-PC.home [192.168.1.4]

0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% Wireless_Broadband_Router.home [19
2.168.1.1]
0/ 100 = 0% |
2 6ms 0/ 100 = 0% 0/ 100 = 0% L100.NYCMNY-VFTTP-224.verizon-gni.
net [74.108.1.1]
0/ 100 = 0% |
3 7ms 0/ 100 = 0% 0/ 100 = 0% G0-14-4-6.NYCMNY-LCR-21.verizon-gn
i.net [130.81.188.250]
0/ 100 = 0% |
4 19ms 0/ 100 = 0% 0/ 100 = 0% ae0-0.NY325-BB-RTR2.verizon-gni.ne
t [130.81.209.110]
11/ 100 = 11% |
5 54ms 11/ 100 = 11% 0/ 100 = 0% 0.xe-3-2-0.BR2.NYC4.ALTER.NET [152
.63.20.213]
1/ 100 = 1% |
6 41ms 12/ 100 = 12% 0/ 100 = 0% 192.205.34.49
88/ 100 = 88% |
7 --- 100/ 100 =100% 0/ 100 = 0% cr1.n54ny.ip.att.net [12.122.86.6]

0/ 100 = 0% |
8 --- 100/ 100 =100% 0/ 100 = 0% cr2.cgcil.ip.att.net [12.122.1.2]

0/ 100 = 0% |
9 --- 100/ 100 =100% 0/ 100 = 0% cr1.cgcil.ip.att.net [12.122.2.53]

Trace complete.

[/code]

 

 

 

Traceroute and Pathping to Nightfall (for Aerie Peak):

 

[code]Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.

TRACEROUTE 63.240.104.93

Tracing route to 63.240.104.93 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 3 ms 70 ms 54 ms L100.NYCMNY-VFTTP-224.verizon-gni.net [74.108.1.
1]
3 6 ms 7 ms 7 ms G0-14-4-6.NYCMNY-LCR-22.verizon-gni.net [130.81.
188.248]
4 69 ms 34 ms 4 ms so-3-1-0-0.NY5030-BB-RTR1.verizon-gni.net [130.8
1.151.234]
5 6 ms 5 ms 6 ms 0.xe-3-3-0.BR2.NYC4.ALTER.NET [152.63.23.133]
6 5 ms * 7 ms 192.205.36.57
7 27 ms 28 ms 7 ms cr1.n54ny.ip.att.net [12.122.86.6]
8 32 ms 28 ms 59 ms gar1.nw2nj.ip.att.net [12.122.131.81]
9 24 ms 25 ms 5 ms 12.122.251.6
10 52 ms 53 ms 52 ms mdf001c7613r0003-gig-12-1.nyc3.attens.net [63.24
0.65.22]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

PATHPING 63.240.104.93

Tracing route to 63.240.104.93 over a maximum of 30 hops

0 PC.home [192.168.1.4]
1 Wireless_Broadband_Router.home [192.168.1.1]
2 L100.NYCMNY-VFTTP-224.verizon-gni.net [74.108.1.1]
3 G0-14-4-6.NYCMNY-LCR-22.verizon-gni.net [130.81.188.248]
4 so-3-1-0-0.NY5030-BB-RTR1.verizon-gni.net [130.81.151.234]
5 0.xe-3-3-0.BR2.NYC4.ALTER.NET [152.63.23.133]
6 192.205.36.57
7 cr1.n54ny.ip.att.net [12.122.86.6]
8 gar1.nw2nj.ip.att.net [12.122.131.81]
9 12.122.251.10
10 mdf001c7613r0003-gig-12-1.nyc3.attens.net [63.240.65.22]
11 * * *
Computing statistics for 250 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 PC.home [192.168.1.4]

0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% Wireless_Broadband_Router.home [19
2.168.1.1]
0/ 100 = 0% |
2 4ms 0/ 100 = 0% 0/ 100 = 0% L100.NYCMNY-VFTTP-224.verizon-gni.
net [74.108.1.1]
0/ 100 = 0% |
3 6ms 0/ 100 = 0% 0/ 100 = 0% G0-14-4-6.NYCMNY-LCR-22.verizon-gn
i.net [130.81.188.248]
0/ 100 = 0% |
4 20ms 0/ 100 = 0% 0/ 100 = 0% so-3-1-0-0.NY5030-BB-RTR1.verizon-
gni.net [130.81.151.234]
0/ 100 = 0% |
5 70ms 15/ 100 = 15% 15/ 100 = 15% 0.xe-3-3-0.BR2.NYC4.ALTER.NET [152
.63.23.133]
0/ 100 = 0% |
6 48ms 0/ 100 = 0% 0/ 100 = 0% 192.205.36.57
100/ 100 =100% |
7 --- 100/ 100 =100% 0/ 100 = 0% cr1.n54ny.ip.att.net [12.122.86.6]

0/ 100 = 0% |
8 --- 100/ 100 =100% 0/ 100 = 0% gar1.nw2nj.ip.att.net [12.122.131.
81]
0/ 100 = 0% |
9 --- 100/ 100 =100% 0/ 100 = 0% 12.122.251.10
0/ 100 = 0% |
10 --- 100/ 100 =100% 0/ 100 = 0% mdf001c7613r0003-gig-12-1.nyc3.att
ens.net [63.240.65.22]

Trace complete.
[/code]

Highlighted
Contributor
Contributor
Posts: 1
Registered: ‎02-10-2013

Re: Excessive Slowness/Latency with Netflix, World of Warcraft, browsing in general...

Message 6 of 20
(5,785 Views)

Same issue here, have been having problems logging into wow or even accessing us.battle.net in a browser.

Highlighted
Nickel Contributor
Nickel Contributor
Posts: 28
Registered: ‎07-19-2012

Re: Excessive Slowness/Latency with Netflix, World of Warcraft, browsing in general...

Message 7 of 20
(5,723 Views)

@matt_g wrote:

I hate to say it, but welcome to the club! Several people here posting similar issues. Been having this issue for just over 2 weeks now with no resolution from support.


 


Matt and I have been posting in various threads about this for a bit now..and so have others.  My problems start around 8-9pm and last through 11pm PST.  I have horrible download speeds and my latency to Khadgar server goes from 75ms to 800 ms with HUGE spikes making the game simply unplayable.

 

I have called Verizon, posted on Twitter and I think the only thing that will help is MORE PEOPLE COMPLAINING!

Highlighted
Contributor
Contributor
Posts: 2
Registered: ‎02-11-2013

Re: Excessive Slowness/Latency with Netflix, World of Warcraft, browsing in general...

Message 8 of 20
(5,636 Views)

Trollbane-US
Germantown, MD

The last 2-3 days I have had terrible latency, upwards of 8000ms and making the game unplayable. The time of day doesn't seem to reduce the lag. I called Verizon tech support and they were not helpful (reset equipment, etc.). When asked specifically about this issue all techs I've spoken to don't even know what WoW is and just want to keep searching their knowledge base .  This issue is definitely well known since the WoW forums has a stickied thread devoted to Verizon customers with this issue. When I run speed tests, I get appropriate speeds (30 Mbps download and 15 Mbps upload). Different servers do not seem to reduce the lag (tried Bloodhoof-US). I also tried different instances with a server but I was lagging in all of them. I'm not very happy with the lack of information on Verizon's part. It's clearly their servers because if I use a proxy service to log into WoW (thereby bypassing a lot of the hops between Verizon and Blizzard), I can get in just fine with no lag. I have friends using Comcast or other ISPs that also log into my same server (Trollbane) with absolultely no issues or lag. I am EXTREMELY close to cancelling my Fios account and switching to Comcast. So far Verizon Fios has not impressed me with their service and I'm not sure why I would continue to pay them for this. Trace route info below.

 

Tracing route to 63.240.161.189 over a maximum of 30 hops

  1     4 ms    <1 ms    <1 ms  Wireless_Broadband_Router.home [192.168.1.1] 

  2     8 ms     7 ms     7 ms  L100.WASHDC-VFTTP-92.verizon-gni.net [71.191.59.1] 

  3    12 ms    12 ms    12 ms  G0-12-3-5.WASHDC-LCR-21.verizon-gni.net [130.81.184.76] 

  4    10 ms    10 ms     9 ms  ae3-0.RES-BB-RTR1.verizon-gni.net [130.81.199.130] 

  5    13 ms    12 ms    12 ms  0.xe-5-3-0.BR1.IAD8.ALTER.NET [152.63.37.49] 

  6    16 ms    19 ms    17 ms  192.205.36.141 

  7     *        *        *     Request timed out.

  8    51 ms    47 ms    47 ms  cr1.cgcil.ip.att.net [12.122.18.21] 

  9    47 ms    48 ms    47 ms  gar2.clboh.ip.att.net [12.122.133.197] 

 10    62 ms    64 ms    84 ms  12.122.251.50 

 11    52 ms    49 ms    50 ms  63.240.130.214 

 12     *        *        *     Request timed out.

 13     *        *        *     Request timed out.

 14     *        *        *     Request timed out.

 15     *        *        *     Request timed out.

 16     *        *        *     Request timed out.

 17     *        *        *     Request timed out.

 18     *        *        *     Request timed out.

 19     *        *        *     Request timed out.

 20     *        *        *     Request timed out.

 21     *        *        *     Request timed out.

 22     *        *        *     Request timed out.

 23     *        *        *     Request timed out.

 24     *        *        *     Request timed out.

 25     *        *        *     Request timed out.

 26     *        *        *     Request timed out.

 27     *        *        *     Request timed out.

 28     *        *        *     Request timed out.

 29     *        *        *     Request timed out.

 30     *        *        *     Request timed out.

Trace complete.

 

 

Highlighted
Contributor
Contributor
Posts: 1
Registered: ‎02-11-2013

Re: Excessive Slowness/Latency with Netflix, World of Warcraft, browsing in general...

Message 9 of 20
(5,625 Views)

I'm not a WOW user, but I've been experiencing similar issues in Germantown, MD.  Latency, slow download speeds, intermittent loss of connections to Web sites...  Usually my connection is very stable, but since around Wednesday of last week I've been having issues.  My kids are all over me to fix it since it cuts into their gaming and youtube time, and they believe that I own the Internet. 🙂  Looking through my firewall logs I can see that my Internet connection went down at 04:17 AM last night and then came right back up.  This morning my latency issues and connection speeds are more in line with my expectations.  I was planning to start the endless waiting on hold for a support call today.  Now I'm guardedly optimistic that maybe (just maybe) Verizon has corrected some issue that they were able to identify.  I'm goign to continue monitoring and testing periodically.  Can any of the other Germantown, MD users that were having issues confrm or deny that the localized situation has improved?

Highlighted
Contributor
Contributor
Posts: 2
Registered: ‎02-11-2013

Re: Excessive Slowness/Latency with Netflix, World of Warcraft, browsing in general...

Message 10 of 20
(5,616 Views)

I will be able to check this evening. Aside from WoW, I was also experiencing issues streaming shows from Hulu, even though my speed tests showed normal download/upload speeds. It seems that one of their routing servers that get traffic from the MD area is having issues. I wish someone at Verizon would at least say "yes there is an issue."

How-To Videos
 
The following videos were produced by users like you!
   
Videos are subject to the Verizon Fios Community Terms of Service and User Guidelines and contains content that is not created by Verizon.
Covid19


Browse Categories
Categories:
Posts

Verizon Troubleshooters
Unable to find your answer here? Try searching Verizon Troubleshooters for more options.