Verizon ISP Issues - Tracking

Technical Support
Prev 1 21 22 23 29 Next
I never knew so many people from TO played.

Verizon FiOS
Thousand oaks, Ca
Hyjal
2/13/2013 5am pst

Tracing route to mdf1-bi8k-1-ve-87.phx1.attens.net [63.241.138.161]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 20 ms 19 ms 20 ms L100.LSANCA-VFTTP-109.verizon-gni.net [98.112.230.1]
3 24 ms 27 ms 23 ms G0-6-1-0.LSANCA-LCR-21.verizon-gni.net [130.81.138.60]
4 26 ms 26 ms 26 ms so-6-0-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81.29.124]
5 22 ms 91 ms 22 ms 0.xe-9-0-0.BR3.LAX15.ALTER.NET [152.63.114.245]
6 25 ms 26 ms 26 ms 204.255.168.134
7 40 ms 39 ms 39 ms cr1.la2ca.ip.att.net [12.123.132.129]
8 35 ms 39 ms 39 ms cr2.phmaz.ip.att.net [12.122.31.190]
9 37 ms 33 ms 33 ms 12.123.206.225
10 36 ms 33 ms 33 ms 12-122-254-50.attens.net [12.122.254.50]
11 32 ms 33 ms 32 ms mdf002c7613r0002-gig-10-1.phx1.attens.net [63.241.130.206]
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.
Germantown, MD again. Second night in a row that I've been able to play without any lag at all. I will post my tracert later to see if it is different now that it works as compared to my first post when it was lag-central.
A quick update: We are actively working with our internet service partners on trying to determine what exactly is causing this issue. As we are still investigating the root of the problem, we currently do not have an ETA on a resolution.

Please continue to provide traceroutes and pathpings when you are experiencing issues, as this will help speed up our investigation.

Thanks for your patience everyone!


Thank you for the update!
So, I have no idea how to get the information you're asking for. But I can tell you that I get DC'd almost every minute since I switched to Verison and set up my account 3 days ago. Infact it was so bad I wasn't even able to play the first day and I'm pretty much unable to play at all this week. And for the sake of giving all the info I can, I have a wire, not wifi, if that helps at all. I am in Brookhaven, New York.
I never knew so many people from TO played.


We should start a guild O.o
02/13/2013 10:22 AMPosted by Torrq
I never knew so many people from TO played.


We should start a guild O.o

or a support group...
Name the guild Support Group..membership requirement latency of 1500+
I am not with verison I am from Canada, i am getting alot of lag and rubberbanding. my lattency goes up and down (world lattency)
is this just affected to Verison users? Or because of partnerships an so forth, has it begun to affect other isps.
I am with Eastlink Out Of Nova Scotia Canada.
Pandorium, I'm not a verizon user and have been experiencing issues with it. My latency was a good steady 50-60 ms but in the past two weeks it's been hopping from 60-300 and it's just spiky. It'll be 73ms one moment and then hit 298 the next. Feels like a yo-yo and very frustrating trying to heal heroic content. Guild is being patient and it's playable but it's just enough to be irritating. I've been doing the trace route and 3/4ths come out great but then there's that one where a couple hops are in the 100-200 ms range.

It's such a mild issue I doubt I'd get anywhere if I tried to go to my provider. They'd say it's working fine. :/

ETA -- I'm with Time warner road runner and our speed test, ping tests come back great. This is one of the tracers from today --

NVM, the lag spike monster is back and even worse than before. Grrrrrrrrr.....

Tracing route to 63.240.104.93 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms READYSHARE [192.168.1.1]
2 22 ms 9 ms 9 ms 10.194.32.1
3 11 ms 15 ms 18 ms unalloc-024-031-202-053.sc.rr.com [24.31.202.53]
4 24 ms 22 ms 24 ms pos6-0.clmascmhe-rtr2.sc.rr.com [24.93.64.126]
5 36 ms 31 ms 31 ms 107.14.19.42
6 30 ms 31 ms 30 ms 107.14.19.133
7 30 ms 30 ms 31 ms ix-0-1-3-0.tcore2.AEQ-Ashburn.as6453.net [216.6.87.53]
8 30 ms 30 ms 31 ms 192.205.34.245
9 41 ms 37 ms 36 ms cr1.wswdc.ip.att.net [12.122.88.174]
10 34 ms 36 ms 39 ms cr2.phlpa.ip.att.net [12.122.4.53]
11 122 ms 98 ms 54 ms gar1.pitpa.ip.att.net [12.122.107.85]
12 41 ms 42 ms 40 ms 12.122.251.2
13 40 ms 38 ms 38 ms mdf001c7613r0004-gig-12-1.nyc3.attens.net [63.240.65.14]
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.


New trace route with lag issues --

Tracing route to 63.240.104.93 over a maximum of 30 hops

1 5 ms 4 ms 2 ms READYSHARE [192.168.1.1]
2 16 ms 13 ms 11 ms 10.194.32.1
3 57 ms 63 ms 18 ms unalloc-024-031-202-053.sc.rr.com [24.31.202.53]
4 36 ms 36 ms 28 ms pos6-0.clmascmhe-rtr2.sc.rr.com [24.93.64.126]
5 59 ms 67 ms 42 ms 107.14.19.42
6 116 ms 158 ms 143 ms 107.14.19.133
7 111 ms 95 ms 107 ms ix-0-1-3-0.tcore2.AEQ-Ashburn.as6453.net [216.6.87.53]
8 89 ms 117 ms 103 ms 192.205.34.245
9 168 ms 223 ms 126 ms cr1.wswdc.ip.att.net [12.122.88.174]
10 214 ms 168 ms 160 ms cr2.phlpa.ip.att.net [12.122.4.53]
11 108 ms 61 ms 100 ms gar1.pitpa.ip.att.net [12.122.107.85]
12 173 ms 150 ms 66 ms 12.122.251.2
13 43 ms 61 ms 49 ms mdf001c7613r0004-gig-12-1.nyc3.attens.net [63.240.65.14]
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18
Brief Description of Issue:
Wife and I have been having VERY BAD LAG for the past couple weeks (noticeable while raiding, but occurs outside of raiding as well. In raids, we freeze for anywhere from 2 to 60 seconds. Sometimes getting d/c'd.) There has not been a good raiding experience for either of us for the past one to two weeks.

ISP is Verizon FIOS. 75 download/35 upload speeds. New router, everything checks out...STILL LAGGY AS HECK IN RAIDS. Please please please please fix. :)

Server (Realm): Kargath - US
Location: Gainesville,VA


Thanks,
Claud


Attempt 1:
tracert 12.129.209.68

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 7 ms 6 ms 7 ms L100.WASHDC-VFTTP-94.verizon-gni.net [96.241.211
.1]
3 9 ms 12 ms 15 ms G0-13-3-4.WASHDC-LCR-22.verizon-gni.net [130.81.
110.144]
4 9 ms 9 ms 10 ms ae0-0.RES-BB-RTR1.verizon-gni.net [130.81.209.11
4]
5 9 ms 14 ms 10 ms 0.xe-8-0-0.BR1.IAD8.ALTER.NET [152.63.37.73]
6 12 ms 15 ms 12 ms 192.205.36.141
7 85 ms 86 ms 84 ms cr2.wswdc.ip.att.net [12.122.81.250]
8 88 ms 87 ms 87 ms cr1.cgcil.ip.att.net [12.122.18.21]
9 87 ms 92 ms 85 ms cr2.dvmco.ip.att.net [12.122.31.85]
10 87 ms 87 ms 87 ms cr1.slkut.ip.att.net [12.122.30.25]
11 83 ms 89 ms 84 ms cr2.la2ca.ip.att.net [12.122.30.30]
12 81 ms 81 ms 82 ms gar29.la2ca.ip.att.net [12.122.129.241]
13 84 ms 82 ms 82 ms 12-122-254-238.attens.net [12.122.254.238]
14 81 ms 82 ms 84 ms mdf001c7613r0002.lax1.attens.net [206.16.68.54]

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.



Attempt 2:
tracert 12.129.209.68

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 6 ms 8 ms 9 ms L100.WASHDC-VFTTP-94.verizon-gni.net [96.241.211
.1]
3 11 ms 9 ms 12 ms G0-13-3-4.WASHDC-LCR-22.verizon-gni.net [130.81.
110.144]
4 * 11 ms 11 ms ae0-0.RES-BB-RTR1.verizon-gni.net [130.81.209.11
4]
5 10 ms 9 ms 9 ms 0.xe-8-0-0.BR1.IAD8.ALTER.NET [152.63.37.73]
6 10 ms 13 ms 10 ms 192.205.36.141
7 85 ms 83 ms 87 ms cr2.wswdc.ip.att.net [12.122.81.250]
8 86 ms 83 ms 89 ms cr1.cgcil.ip.att.net [12.122.18.21]
9 84 ms 83 ms 90 ms cr2.dvmco.ip.att.net [12.122.31.85]
10 88 ms 88 ms 90 ms cr1.slkut.ip.att.net [12.122.30.25]
11 90 ms 86 ms 90 ms cr2.la2ca.ip.att.net [12.122.30.30]
12 81 ms 83 ms 83 ms gar29.la2ca.ip.att.net [12.122.129.241]
13 83 ms 86 ms 81 ms 12-122-254-234.attens.net [12.122.254.234]
14 84 ms 82 ms 82 ms mdf001c7613r0002.lax1.attens.net [206.16.68.54]

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.
Frankly, this doesn't look like a Verizon issue at all from the tracerts...it looks like an AT&T issue. Does anyone else disagree? If so, could you explain your logic?
For those who are not Verizon customers, the issues affecting you might be the same ones affecting us. I agree with Magicmaster that this might well be an ATT problem. All the large companies pay each other to use bandwidth on each others lines. ATT owns a LOT of the "information highway real estate" across the US.

Here is more from me:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\i73930k2>tracert 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 1 ms 1 ms 1 ms L100.LSANCA-VFTTP-127.verizon-gni.net [173.51.202.1]
3 7 ms 7 ms 5 ms G0-9-1-5.LSANCA-LCR-21.verizon-gni.net [130.81.138.96]
4 3 ms 3 ms 2 ms so-4-1-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81.151.246]
5 30 ms 5 ms 4 ms 0.xe-3-0-0.BR3.LAX15.ALTER.NET [152.63.114.241]
6 3 ms 3 ms 6 ms 204.255.168.134
7 80 ms 80 ms 83 ms cr2.la2ca.ip.att.net [12.123.30.134]
8 81 ms 79 ms 79 ms cr1.slkut.ip.att.net [12.122.30.29]
9 80 ms 80 ms 82 ms cr2.dvmco.ip.att.net [12.122.30.26]
10 82 ms 83 ms 83 ms cr1.cgcil.ip.att.net [12.122.31.86]
11 81 ms 83 ms 82 ms cr1.cl2oh.ip.att.net [12.122.2.206]
12 81 ms 83 ms 83 ms cr2.cl2oh.ip.att.net [12.122.2.126]
13 83 ms 82 ms 82 ms cr2.phlpa.ip.att.net [12.122.2.210]
14 78 ms 78 ms 78 ms gar1.pitpa.ip.att.net [12.122.107.85]
15 93 ms 84 ms 83 ms 12.122.251.2
16 90 ms 89 ms 89 ms mdf001c7613r0004-gig-12-1.nyc3.attens.net [63.240.65.14]
17 * * * Request timed out.
18 ^C
C:\Users\i73930k2>pathping 63.240.104.93

Tracing route to 63.240.104.93 over a maximum of 30 hops

0 i73930k2-PC.home [192.168.1.7]
1 Wireless_Broadband_Router.home [192.168.1.1]
2 L100.LSANCA-VFTTP-127.verizon-gni.net [173.51.202.1]
3 G0-9-1-5.LSANCA-LCR-21.verizon-gni.net [130.81.138.96]
4 so-4-1-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81.151.246]
5 0.xe-3-0-0.BR3.LAX15.ALTER.NET [152.63.114.241]
6 204.255.168.134
7 cr2.la2ca.ip.att.net [12.123.30.134]
8 cr1.slkut.ip.att.net [12.122.30.29]
9 cr2.dvmco.ip.att.net [12.122.30.26]
10 cr1.cgcil.ip.att.net [12.122.31.86]
11 cr1.cl2oh.ip.att.net [12.122.2.206]
12 cr2.cl2oh.ip.att.net [12.122.2.126]
13 cr2.phlpa.ip.att.net [12.122.2.210]
14 gar1.pitpa.ip.att.net [12.122.107.85]
15 12-122-254-242.attens.net [12.122.254.242]
16 mdf001c7613r0004-gig-12-1.nyc3.attens.net [63.240.65.14]
17 * * *
Computing statistics for 400 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 i73930k2-PC.home [192.168.1.7]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% Wireless_Broadband_Router.home [192.168.1.1]
0/ 100 = 0% |
2 5ms 0/ 100 = 0% 0/ 100 = 0% L100.LSANCA-VFTTP-127.verizon-gni.net [173.51.202.1]
0/ 100 = 0% |
3 5ms 0/ 100 = 0% 0/ 100 = 0% G0-9-1-5.LSANCA-LCR-21.verizon-gni.net [130.81.138.96]
0/ 100 = 0% |
4 9ms 0/ 100 = 0% 0/ 100 = 0% so-4-1-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81.151.246]
3/ 100 = 3% |
5 7ms 3/ 100 = 3% 0/ 100 = 0% 0.xe-3-0-0.BR3.LAX15.ALTER.NET [152.63.114.241]
0/ 100 = 0% |
6 9ms 3/ 100 = 3% 0/ 100 = 0% 204.255.168.134
97/ 100 = 97% |
7 --- 100/ 100 =100% 0/ 100 = 0% cr2.la2ca.ip.att.net [12.123.30.134]
0/ 100 = 0% |
8 --- 100/ 100 =100% 0/ 100 = 0% cr1.slkut.ip.att.net [12.122.30.29]
0/ 100 = 0% |
9 --- 100/ 100 =100% 0/ 100 = 0% cr2.dvmco.ip.att.net [12.122.30.26]
0/ 100 = 0% |
10 --- 100/ 100 =100% 0/ 100 = 0% cr1.cgcil.ip.att.net [12.122.31.86]
0/ 100 = 0% |
11 --- 100/ 100 =100% 0/ 100 = 0% cr1.cl2oh.ip.att.net [12.122.2.206]
0/ 100 = 0% |
12 --- 100/ 100 =100% 0/ 100 = 0% cr2.cl2oh.ip.att.net [12.122.2.126]
0/ 100 = 0% |
13 --- 100/ 100 =100% 0/ 100 = 0% cr2.phlpa.ip.att.net [12.122.2.210]
0/ 100 = 0% |
14 --- 100/ 100 =100% 0/ 100 = 0% gar1.pitpa.ip.att.net [12.122.107.85]
0/ 100 = 0% |
15 --- 100/ 100 =100% 0/ 100 = 0% 12-122-254-242.attens.net [12.122.254.242]
0/ 100 = 0% |
16 --- 100/ 100 =100% 0/ 100 = 0% mdf001c7613r0004-gig-12-1.nyc3.attens.net [63.240.65.14]


Trace complete.

C:\Users\i73930k2>
As a note to people crying about Verizon, the biggest bottleneck actually exists in att's side..

example from last poster

6 10 ms 9 ms 19 ms 192.205.34.49

7 95 ms 109 ms 96 ms cr2.n54ny.ip.att.net [12.122.86.10]

all's fast up to 192.205.34.49 (also an ATT circuit) then suddenly 100ms latency.


ATT and Verizon are suffering lag just i see more Verizon in this thread but really they need to work on all the internet providers that are getting the lag this is just insane.
I have been sending a Verizon Tech numerous tracerts for the last week when my problem occurs. He called me today (imagine that) and told me that it appears from MY tracerts that the problems looks like a congestion issue that begins with ALTER.NET and ATT...that's straight from the horses mouth.

HOWEVER when I run speedtest at Verizon's own site and choose my state, CA during those times, my download speeds drop from 75Mb/s to 5Mb/sec or less. So, this may be several different problems.
I have been sending a Verizon Tech numerous tracerts for the last week when my problem occurs. He called me today (imagine that) and told me that it appears from MY tracerts that the problems looks like a congestion issue that begins with ALTER.NET and ATT...that's straight from the horses mouth.

HOWEVER when I run speedtest at Verizon's own site and choose my state, CA during those times, my download speeds drop from 75Mb/s to 5Mb/sec or less. So, this may be several different problems.


I'm actually starting to believe there are issues on both Verizon's and ATTs end. As I have been having the same issues with the download speeds hovering around 5Mb/s. There have also been numerous posts over the Verizon foums about similar issues(a few users have pointed out it's Verizon's backbone routing causing the issues but no official word). I'm no expert but the more I look at it the more it looks like it's a compound problem with both Verizon's and AT&T's backend.
Long Island, New York
Verizon Fios
64 bit client with authenticator

STILL am getting disconnected or lag so bad i can't cast, no npcs, and can't even log out properly. This is going on 3 weeks for me since i put a ticket in with an in-game GM. There's 436 posts already.
So...waiting 2 days on an update, any update, is ridiculous. I'm starting to think you guys aren't working the issue anymore. Problems persist in MD.
If you have a twitter account, please follow and tweet @VerizonSupport. They will open tweet a response and follow you, so you can send a DM with this issue.

UPDATE:...well ....here is Verizons response regarding "that the issues start at ATT.NET" :

"Unfortunately, since it doesn't fall under the umbrella of a Verizon issue, it will need to be relayed to them through another party.^AFC "
If you have a twitter account, please follow and tweet @VerizonSupport. They will open tweet a response and follow you, so you can send a DM with this issue.

UPDATE:...well ....here is Verizons response regarding "that the issues start at ATT.NET" :

"Unfortunately, since it doesn't fall under the umbrella of a Verizon issue, it will need to be relayed to them through another party.^AFC "


LOL I suppose the only "party" that will get any response is Blizzard. Can you imagine us calling up ATT and telling them we subscribe to Verizon and we have traced our latency problems to their network? THEY WOULD LAUGH US INTO NEXT WEEK.

Join the Conversation

Return to Forum