Verizon ISP Issues - Tracking

(Locked)

Support Forum Agent
Hey all!

If you are a Verizon ISP customer and are having connection issues (latency, disconnection, packet loss, etc.) we'd like to gather some data from you for analysis. Please provide us the following:

Realm (if a WoW player):
Your Location (city, state):
Brief Description of Issue:

Then post a Tracert and/or Pathping taken when the issue is occurring. After you paste the traces into a post, highlight everything, and hit the "pre" button (It says "Code Blocks" when you hover your mouse over it). That makes the information much more readable.

If you are not a Verizon customer, please post in an already existing thread or create a new one. Thank you!
90 Blood Elf Priest
5360
Blackrock-US
Dallas, TX
World MS spiking to 3-7k for a couple minutes to several minutes shortly after a loading screen, though sometimes everything is fine, until I log over to a different character. Seems pretty random for me.

Tracing route to 12.129.209.68 over a maximum of 30 hops

0 ***-PC.home [192.168.1.2]
1 Wireless_Broadband_Router.home [192.168.1.1]
2 L100.DLLSTX-VFTTP-73.verizon-gni.net [173.74.65.1]
3 G0-3-3-3.DLLSTX-LCR-21.verizon-gni.net [130.81.190.246]
4 so-5-0-0-0.DFW9-BB-RTR1.verizon-gni.net [130.81.199.34]
5 0.xe-3-2-0.BR1.DFW13.ALTER.NET [152.63.98.89]
6 192.205.37.125
7 cr2.dlstx.ip.att.net [12.122.212.14]
8 cr2.la2ca.ip.att.net [12.122.28.178]
9 gar29.la2ca.ip.att.net [12.122.129.241]
10 12-122-254-238.attens.net [12.122.254.238]
11 mdf001c7613r0002.lax1.attens.net [206.16.68.54]
12 * * *
Computing statistics for 275 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 ***-PC.home [192.168.1.2]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% Wireless_Broadband_Router.home [192.168.1.1]
0/ 100 = 0% |
2 23ms 0/ 100 = 0% 0/ 100 = 0% L100.DLLSTX-VFTTP-73.verizon-gni.net [173.74.65.1]
0/ 100 = 0% |
3 8ms 0/ 100 = 0% 0/ 100 = 0% G0-3-3-3.DLLSTX-LCR-21.verizon-gni.net [130.81.190.246]
0/ 100 = 0% |
4 12ms 0/ 100 = 0% 0/ 100 = 0% so-5-0-0-0.DFW9-BB-RTR1.verizon-gni.net [130.81.199.34]
0/ 100 = 0% |
5 10ms 0/ 100 = 0% 0/ 100 = 0% 0.xe-3-2-0.BR1.DFW13.ALTER.NET [152.63.98.89]
0/ 100 = 0% |
6 16ms 0/ 100 = 0% 0/ 100 = 0% 192.205.37.125
100/ 100 =100% |
7 --- 100/ 100 =100% 0/ 100 = 0% cr2.dlstx.ip.att.net [12.122.212.14]
0/ 100 = 0% |
8 --- 100/ 100 =100% 0/ 100 = 0% cr2.la2ca.ip.att.net [12.122.28.178]
0/ 100 = 0% |
9 --- 100/ 100 =100% 0/ 100 = 0% gar29.la2ca.ip.att.net [12.122.129.241]
0/ 100 = 0% |
10 --- 100/ 100 =100% 0/ 100 = 0% 12-122-254-238.attens.net [12.122.254.238]
0/ 100 = 0% |
11 --- 100/ 100 =100% 0/ 100 = 0% mdf001c7613r0002.lax1.attens.net [206.16.68.54]

Trace complete.

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 8 ms 6 ms 9 ms L100.DLLSTX-VFTTP-73.verizon-gni.net [173.74.65.1]
3 9 ms 10 ms 7 ms G0-3-3-3.DLLSTX-LCR-21.verizon-gni.net [130.81.190.246]
4 11 ms 10 ms 10 ms so-5-0-0-0.DFW9-BB-RTR1.verizon-gni.net [130.81.199.34]
5 12 ms 10 ms 9 ms 0.xe-3-2-0.BR1.DFW13.ALTER.NET [152.63.98.89]
6 11 ms 12 ms 12 ms 192.205.37.125
7 44 ms 52 ms 44 ms cr2.dlstx.ip.att.net [12.122.212.14]
8 44 ms 47 ms 47 ms cr2.la2ca.ip.att.net [12.122.28.178]
9 156 ms 90 ms 49 ms gar29.la2ca.ip.att.net [12.122.129.241]
10 42 ms 42 ms 45 ms 12-122-254-238.attens.net [12.122.254.238]
11 44 ms 44 ms 45 ms mdf001c7613r0002.lax1.attens.net [206.16.68.54]
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.
90 Tauren Druid
6705
Kil'Jaeden-US
Dallas, TX (see the trend)
Constantly freezing, d/cing
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 8 ms 7 ms 7 ms L100.DLLSTX-VFTTP-73.verizon-gni.net [173.74.65.1]
3 6 ms 7 ms 7 ms G0-3-1-3.DLLSTX-LCR-21.verizon-gni.net [130.81.109.222]
4 9 ms 10 ms 9 ms so-5-0-0-0.DFW9-BB-RTR1.verizon-gni.net [130.81.199.34]
5 11 ms 9 ms 10 ms 0.xe-3-2-0.BR1.DFW13.ALTER.NET [152.63.98.89]
6 9 ms 9 ms 10 ms 192.205.37.125
7 48 ms 44 ms 47 ms cr2.dlstx.ip.att.net [12.122.212.14]
8 48 ms 47 ms 45 ms cr2.la2ca.ip.att.net [12.122.28.178]
9 40 ms 39 ms 52 ms gar29.la2ca.ip.att.net [12.122.129.241]
10 41 ms 42 ms 42 ms 12-122-254-234.attens.net [12.122.254.234]
11 43 ms 41 ms 42 ms mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250]
12 * * * Request timed out.
13
Edited by Cretan on 2/7/2013 8:29 PM PST
90 Undead Priest
7990
Realm: Arthas-US (Ruin Battlegroup)
Location: Whitestone (Queens), NY
Issue: World lag spikes (goes up to 5000), combat freezes for a minute then resumes in short intervals. Character rubber bands a lot.

*EDIT* can't even join instances / bgs now. says transfer aborted: instance not found. also added tracert

Tracert:

Tracing route to 63.240.161.189 over a maximum of 30 hops

1 <1 ms <1 ms 1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 5 ms 9 ms 8 ms L100.NYCMNY-VFTTP-48.verizon-gni.net [71.167.106
.1]
3 14 ms 14 ms 11 ms G0-1-1-3.NYCMNY-LCR-21.verizon-gni.net [130.81.1
88.74]
4 7 ms 13 ms 42 ms so-11-0-0-0.NY325-BB-RTR1.verizon-gni.net [130.8
1.151.222]
5 11 ms 9 ms 10 ms 0.xe-9-0-0.BR2.NYC4.ALTER.NET [152.63.20.189]
6 94 ms 95 ms 100 ms 192.205.34.49
7 * 77 ms 45 ms cr1.n54ny.ip.att.net [12.122.86.6]
8 77 ms 64 ms 48 ms cr2.cgcil.ip.att.net [12.122.1.2]
9 73 ms 70 ms * gar3.cgcil.ip.att.net [12.122.132.213]
10 * 37 ms 72 ms 12.122.251.22
11 67 ms 85 ms 87 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.


Saved path pings from 2 diff occasions.

Tracing route to 63.240.161.189 over a maximum of 30 hops

0 Greg-PC.home [192.168.1.3]
1 Wireless_Broadband_Router.home [192.168.1.1]
2 L100.NYCMNY-VFTTP-48.verizon-gni.net [71.167.106.1]
3 G0-1-1-3.NYCMNY-LCR-21.verizon-gni.net [130.81.188.74]
4 so-11-0-0-0.NY325-BB-RTR1.verizon-gni.net [130.81.151.222]
5 0.xe-9-0-0.BR2.NYC4.ALTER.NET [152.63.20.189]
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 gar3.cgcil.ip.att.net [12.122.132.213]
10 * 12.122.251.50
11 63.240.130.214
12 * * *
Computing statistics for 275 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Greg-PC.home [192.168.1.3]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% Wireless_Broadband_Router.home [192.168.1.1]
0/ 100 = 0% |
2 9ms 0/ 100 = 0% 0/ 100 = 0% L100.NYCMNY-VFTTP-48.verizon-gni.net [71.167.106.1]
0/ 100 = 0% |
3 14ms 2/ 100 = 2% 2/ 100 = 2% G0-1-1-3.NYCMNY-LCR-21.verizon-gni.net [130.81.188.74]
0/ 100 = 0% |
4 20ms 0/ 100 = 0% 0/ 100 = 0% so-11-0-0-0.NY325-BB-RTR1.verizon-gni.net [130.81.151.222]
0/ 100 = 0% |
5 54ms 13/ 100 = 13% 13/ 100 = 13% 0.xe-9-0-0.BR2.NYC4.ALTER.NET [152.63.20.189]
0/ 100 = 0% |
6 61ms 0/ 100 = 0% 0/ 100 = 0% 192.205.34.49
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% cr2.cgcil.ip.att.net [12.122.1.2]
0/ 100 = 0% |
9 --- 100/ 100 =100% 0/ 100 = 0% gar3.cgcil.ip.att.net [12.122.132.213]
0/ 100 = 0% |
10 --- 100/ 100 =100% 0/ 100 = 0% 12.122.251.50
0/ 100 = 0% |
11 --- 100/ 100 =100% 0/ 100 = 0% 63.240.130.214

Trace complete.


Tracing route to 63.240.161.189 over a maximum of 30 hops

0 Greg-PC.home [192.168.1.3]
1 Wireless_Broadband_Router.home [192.168.1.1]
2 L100.NYCMNY-VFTTP-48.verizon-gni.net [71.167.106.1]
3 G0-1-1-3.NYCMNY-LCR-21.verizon-gni.net [130.81.188.74]
4 so-11-0-0-0.NY325-BB-RTR1.verizon-gni.net [130.81.151.222]
5 0.xe-9-0-0.BR2.NYC4.ALTER.NET [152.63.20.189]
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 gar3.cgcil.ip.att.net [12.122.132.213]
10 12.122.251.50
11 63.240.130.214
12 * * *
Computing statistics for 275 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Greg-PC.home [192.168.1.3]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% Wireless_Broadband_Router.home [192.168.1.1]
0/ 100 = 0% |
2 9ms 0/ 100 = 0% 0/ 100 = 0% L100.NYCMNY-VFTTP-48.verizon-gni.net [71.167.106.1]
0/ 100 = 0% |
3 12ms 0/ 100 = 0% 0/ 100 = 0% G0-1-1-3.NYCMNY-LCR-21.verizon-gni.net [130.81.188.74]
0/ 100 = 0% |
4 15ms 0/ 100 = 0% 0/ 100 = 0% so-11-0-0-0.NY325-BB-RTR1.verizon-gni.net [130.81.151.222]
1/ 100 = 1% |
5 22ms 3/ 100 = 3% 2/ 100 = 2% 0.xe-9-0-0.BR2.NYC4.ALTER.NET [152.63.20.189]
0/ 100 = 0% |
6 27ms 1/ 100 = 1% 0/ 100 = 0% 192.205.34.49
99/ 100 = 99% |
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% gar3.cgcil.ip.att.net [12.122.132.213]
0/ 100 = 0% |
10 --- 100/ 100 =100% 0/ 100 = 0% 12.122.251.50
0/ 100 = 0% |
11 --- 100/ 100 =100% 0/ 100 = 0% 63.240.130.214

Trace complete.
Edited by Riiz on 2/8/2013 5:12 PM PST
90 Night Elf Hunter
15165
Realm: Cairne-US (Emberstorm Battlegroup)
Location: Dallas, TX
Using Verizon FIOS, speed test came back at 19.54 download/4.72 upload, no other issues with internet (browsing, youtube, etc).

Issue: lag spikes (currently world latency 1543), disconnect when zoning or can't zone at all. When logging in it's like a shell, the city is there but no NPC's or players, no mailboxes, etc. Sometimes the NPC's will be there but I can't interact with them.

I'd never heard this term before but it describes exactly what I'm seeing with my character: Character rubber bands a lot.

Pathping:

Tracing route to mdf1-bi8k-1-ve-87.phx1.attens.net [63.241.138.161]
over a maximum of 30 hops:
0 Barbara-PC.home [192.168.1.2]
1 myrouter.home [192.168.1.1]
2 L100.DLLSTX-VFTTP-88.verizon-gni.net [173.74.37.1]
3 G0-5-2-4.DLLSTX-LCR-22.verizon-gni.net [130.81.138.176]
4 so-5-0-0-0.DFW9-BB-RTR2.verizon-gni.net [130.81.199.36]
5 0.xe-3-0-1.BR1.DFW13.ALTER.NET [152.63.98.241]
6 192.205.37.125
7 cr1.dlstx.ip.att.net [12.122.212.10]
8 cr1.phmaz.ip.att.net [12.122.28.182]
9 12.123.206.181
10 12-122-254-50.attens.net [12.122.254.50]
11 mdf002c7613r0001-gig-12-1.phx1.attens.net [63.241.130.210]
12 * * *
Computing statistics for 275 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Barbara-PC.home [192.168.1.2]
0/ 100 = 0% |
1 3ms 0/ 100 = 0% 0/ 100 = 0% myrouter.home [192.168.1.1]
0/ 100 = 0% |
2 16ms 0/ 100 = 0% 0/ 100 = 0% L100.DLLSTX-VFTTP-88.verizon-gni.net [173.74.37.1]
0/ 100 = 0% |
3 13ms 0/ 100 = 0% 0/ 100 = 0% G0-5-2-4.DLLSTX-LCR-22.verizon-gni.net [130.81.138.176]
0/ 100 = 0% |
4 15ms 0/ 100 = 0% 0/ 100 = 0% so-5-0-0-0.DFW9-BB-RTR2.verizon-gni.net [130.81.199.36]
0/ 100 = 0% |
5 13ms 0/ 100 = 0% 0/ 100 = 0% 0.xe-3-0-1.BR1.DFW13.ALTER.NET [152.63.98.241]
0/ 100 = 0% |
6 16ms 0/ 100 = 0% 0/ 100 = 0% 192.205.37.125
100/ 100 =100% |
7 --- 100/ 100 =100% 0/ 100 = 0% cr1.dlstx.ip.att.net [12.122.212.10]
0/ 100 = 0% |
8 --- 100/ 100 =100% 0/ 100 = 0% cr1.phmaz.ip.att.net [12.122.28.182]
0/ 100 = 0% |
9 --- 100/ 100 =100% 0/ 100 = 0% 12.123.206.181
0/ 100 = 0% |
10 --- 100/ 100 =100% 0/ 100 = 0% 12-122-254-50.attens.net [12.122.254.50]
0/ 100 = 0% |
11 --- 100/ 100 =100% 0/ 100 = 0% mdf002c7613r0001-gig-12-1.phx1.attens.net [63.241.130.210]

Trace complete.


Tracert:

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 myrouter.home [192.168.1.1]
2 8 ms 8 ms 7 ms L100.DLLSTX-VFTTP-88.verizon-gni.net [173.74.37.1]
3 14 ms 10 ms 10 ms G0-5-2-4.DLLSTX-LCR-22.verizon-gni.net [130.81.138.176]
4 9 ms 9 ms 11 ms so-5-0-0-0.DFW9-BB-RTR2.verizon-gni.net [130.81.199.36]
5 11 ms 12 ms 8 ms 0.xe-3-0-1.BR1.DFW13.ALTER.NET [152.63.98.241]
6 12 ms 12 ms 11 ms 192.205.37.125
7 47 ms 48 ms 48 ms cr1.dlstx.ip.att.net [12.122.212.10]
8 45 ms 46 ms 48 ms cr1.phmaz.ip.att.net [12.122.28.182]
9 42 ms 42 ms 44 ms 12.123.206.181
10 43 ms 43 ms 42 ms 12-122-254-50.attens.net [12.122.254.50]
11 43 ms 41 ms 43 ms mdf002c7613r0001-gig-12-1.phx1.attens.net [63.241.130.210]
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.
Edited by Sweetzz on 2/21/2013 2:24 PM PST
90 Human Priest
10440
Realm: Blade's Edge
Location: Walnut, CA
Issue: Before two weeks ago, I used to always be at about 30ms. When I'm having a good day, I'm regularly at 80-100ms now. When I'm having a bad day, it can get into the thousands. For a few days, every time I would visit Stormwind or Ironforge on this character, it was so unplayable I had to ALT F4 out (15-25k world latency, 80 home latency). Today is the first day I have not had that particular issue (just checked). In general, any spikes are sudden and random. I've found the only way to get back to normal is to completely exit the game and restart. Verizon download speeds are at 42MB and upload speeds at 35MB.


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 5 ms 5 ms 5 ms L100.LSANCA-VFTTP-113.verizon-gni.net [98.119.77.1]
3 11 ms 11 ms 10 ms G0-5-2-5.LSANCA-LCR-22.verizon-gni.net [130.81.138.242]
4 18 ms 8 ms 8 ms ae2-0.LAX01-BB-RTR2.verizon-gni.net [130.81.22.238]
5 9 ms 10 ms 39 ms 0.xe-9-1-0.BR3.LAX15.ALTER.NET [152.63.115.65]
6 9 ms 10 ms 10 ms 192.205.35.161
7 84 ms 86 ms 83 ms cr2.la2ca.ip.att.net [12.123.30.134]
8 84 ms 84 ms 83 ms cr1.slkut.ip.att.net [12.122.30.29]
9 85 ms 86 ms * cr2.dvmco.ip.att.net [12.122.30.26]
10 85 ms 83 ms 83 ms cr1.cgcil.ip.att.net [12.122.31.86]
11 85 ms 83 ms 87 ms cr2.cgcil.ip.att.net [12.122.2.54]
12 87 ms 85 ms 86 ms cr1.n54ny.ip.att.net [12.122.1.1]
13 94 ms 121 ms 81 ms gar1.nw2nj.ip.att.net [12.122.131.81]
14 84 ms 83 ms 83 ms 12.122.251.10
15 125 ms 96 ms 86 ms mdf001c7613r0003-gig-12-1.nyc3.attens.net [63.240.65.22]
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.


Tracing route to 63.240.104.93 over a maximum of 30 hops

0 owner-PC.home [192.168.1.2]
1 Wireless_Broadband_Router.home [192.168.1.1]
2 L100.LSANCA-VFTTP-113.verizon-gni.net [98.119.77.1]
3 G0-5-2-5.LSANCA-LCR-22.verizon-gni.net [130.81.138.242]
4 ae2-0.LAX01-BB-RTR2.verizon-gni.net [130.81.22.238]
5 0.xe-9-1-0.BR3.LAX15.ALTER.NET [152.63.115.65]
6 192.205.35.161
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 cr2.cgcil.ip.att.net [12.122.2.54]
12 cr1.n54ny.ip.att.net [12.122.1.1]
13 gar1.nw2nj.ip.att.net [12.122.131.81]
14 12.122.251.6
15 mdf001c7613r0003-gig-12-1.nyc3.attens.net [63.240.65.22]
16 * * *
Computing statistics for 375 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 owner-PC.home [192.168.1.2]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% Wireless_Broadband_Router.home [192.168.1.1]
0/ 100 = 0% |
2 6ms 0/ 100 = 0% 0/ 100 = 0% L100.LSANCA-VFTTP-113.verizon-gni.net [98.119.77.1]
0/ 100 = 0% |
3 8ms 0/ 100 = 0% 0/ 100 = 0% G0-5-2-5.LSANCA-LCR-22.verizon-gni.net [130.81.138.242]
0/ 100 = 0% |
4 10ms 0/ 100 = 0% 0/ 100 = 0% ae2-0.LAX01-BB-RTR2.verizon-gni.net [130.81.22.238]
2/ 100 = 2% |
5 13ms 2/ 100 = 2% 0/ 100 = 0% 0.xe-9-1-0.BR3.LAX15.ALTER.NET [152.63.115.65]
0/ 100 = 0% |
6 8ms 2/ 100 = 2% 0/ 100 = 0% 192.205.35.161
98/ 100 = 98% |
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% cr2.cgcil.ip.att.net [12.122.2.54]
0/ 100 = 0% |
12 --- 100/ 100 =100% 0/ 100 = 0% cr1.n54ny.ip.att.net [12.122.1.1]
0/ 100 = 0% |
13 --- 100/ 100 =100% 0/ 100 = 0% gar1.nw2nj.ip.att.net [12.122.131.81]
0/ 100 = 0% |
14 --- 100/ 100 =100% 0/ 100 = 0% 12.122.251.6
0/ 100 = 0% |
15 --- 100/ 100 =100% 0/ 100 = 0% mdf001c7613r0003-gig-12-1.nyc3.attens.net [63.240.65.22]

Trace complete.
1 Human Warrior
0
Realm - Kel'Thuzad US
Location - Lynchburg VA
Verizon Fios. Never had a problem until last night and today.

Here is a traceroute that was done when I was experiencing 800ms world lag and about 250 home. I'm used to between 30-50 for both of them.


Tracing route to 63.240.104.93 over a maximum of 30 hops

1 1 ms 2 ms 1 ms 192.168.1.1
2 7 ms 12 ms 10 ms L100.RCMDVA-VFTTP-18.verizon-gni.net [98.117.71.1]
3 17 ms 11 ms 12 ms G0-3-1-5.RCMDVA-LCR-21.verizon-gni.net [130.81.184.84]
4 31 ms 27 ms 29 ms so-0-1-0-0.RES-BB-RTR1.verizon-gni.net [130.81.199.56]
5 31 ms 30 ms 45 ms 0.xe-5-3-0.BR1.IAD8.ALTER.NET [152.63.37.49]
6 29 ms 29 ms 39 ms 192.205.36.141
7 33 ms 37 ms 38 ms cr1.wswdc.ip.att.net [12.122.81.246]
8 34 ms 36 ms 34 ms cr2.phlpa.ip.att.net [12.122.4.53]
9 103 ms 74 ms 39 ms gar1.pitpa.ip.att.net [12.122.107.85]
10 48 ms 38 ms 37 ms 12.122.251.2
11 50 ms 41 ms 46 ms mdf001c7613r0003-gig-10-1.nyc3.attens.net [63.240.65.10]
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.


Can't do a pathping right now because it just magically stopped lagging, but it will be back shortly...it always comes back...

EDIT: And we're back. Have a pathping!

Tracing route to 63.240.104.93 over a maximum of 30 hops

0 JDJG-HP.home [192.168.1.8]
1 Wireless_Broadband_Router.home [192.168.1.1]
2 L100.RCMDVA-VFTTP-18.verizon-gni.net [98.117.71.1]
3 G0-3-1-5.RCMDVA-LCR-21.verizon-gni.net [130.81.184.84]
4 so-0-1-0-0.RES-BB-RTR1.verizon-gni.net [130.81.199.56]
5 0.xe-5-3-0.BR1.IAD8.ALTER.NET [152.63.37.49]
6 192.205.36.141
7 cr1.wswdc.ip.att.net [12.122.81.246]
8 cr2.phlpa.ip.att.net [12.122.4.53]
9 gar1.pitpa.ip.att.net [12.122.107.85]
10 12.122.251.2
11 mdf001c7613r0003-gig-10-1.nyc3.attens.net [63.240.65.10]
12 * * *
Computing statistics for 275 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 JDJG-HP.home [192.168.1.8]
0/ 100 = 0% |
1 3ms 0/ 100 = 0% 0/ 100 = 0% Wireless_Broadband_Router.home [192.168.1.1]
0/ 100 = 0% |
2 13ms 0/ 100 = 0% 0/ 100 = 0% L100.RCMDVA-VFTTP-18.verizon-gni.net [98.117.71.1]
0/ 100 = 0% |
3 10ms 0/ 100 = 0% 0/ 100 = 0% G0-3-1-5.RCMDVA-LCR-21.verizon-gni.net [130.81.184.84]
0/ 100 = 0% |
4 48ms 0/ 100 = 0% 0/ 100 = 0% so-0-1-0-0.RES-BB-RTR1.verizon-gni.net [130.81.199.56]
0/ 100 = 0% |
5 33ms 0/ 100 = 0% 0/ 100 = 0% 0.xe-5-3-0.BR1.IAD8.ALTER.NET [152.63.37.49]
0/ 100 = 0% |
6 32ms 0/ 100 = 0% 0/ 100 = 0% 192.205.36.141
100/ 100 =100% |
7 --- 100/ 100 =100% 0/ 100 = 0% cr1.wswdc.ip.att.net [12.122.81.246]
0/ 100 = 0% |
8 --- 100/ 100 =100% 0/ 100 = 0% cr2.phlpa.ip.att.net [12.122.4.53]
0/ 100 = 0% |
9 --- 100/ 100 =100% 0/ 100 = 0% gar1.pitpa.ip.att.net [12.122.107.85]
0/ 100 = 0% |
10 --- 100/ 100 =100% 0/ 100 = 0% 12.122.251.2
0/ 100 = 0% |
11 --- 100/ 100 =100% 0/ 100 = 0% mdf001c7613r0003-gig-10-1.nyc3.attens.net [63.240.65.10]

Trace complete.
Edited by Constatine on 2/8/2013 10:10 AM PST
45 Pandaren Monk
4225
Serious lag during evening hours. It changes from ~20ms to ~2-4seconds. Completely un-playable. Here is a Tracert taken during heavy lag play.

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 9 ms 8 ms 9 ms L100.LSANCA-VFTTP-109.verizon-gni.net [98.112.230.1]
3 15 ms 16 ms 15 ms G0-6-1-0.LSANCA-LCR-22.verizon-gni.net [130.81.138.234]
4 13 ms 33 ms 15 ms so-4-1-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.151.248]
5 15 ms 12 ms 29 ms 0.xe-9-1-0.BR3.LAX15.ALTER.NET [152.63.115.65]
6 * 65 ms 34 ms 192.205.35.161
7 * * 27 ms cr1.la2ca.ip.att.net [12.123.30.6]
8 * 65 ms 26 ms cr2.phmaz.ip.att.net [12.122.31.190]
9 22 ms 26 ms 50 ms 12.123.206.249
10 * * * Request timed out.
11 * 22 ms 39 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.
90 Blood Elf Monk
TF
8440
Same probelm in Denton, TX.
90 Draenei Shaman
6550
Khadgar
Long Beach, California
Verizon Fios

Hey all!

First of all, thank you Blizzard for getting involved...it really says a LOT!

I have been experiencing issues for the last two weeks. I just had a tech out here today that I have an email now for to send ping and tracert info to so that hopefully we can resolve this matter. My problems occur between 7pm and 11pm PST. My pings shoot from 75 to 400-800ms and my download speeds are cut from 75mb to 6-10 Mb. I have been contacting people via the Verizon forums and see that this issue is widespread. The tech today told me that a large number of people are having problems in my area.

I will edit my post tonight with tracert and ping info.
90 Human Warrior
8245
Ðiver
Nesingwary
Murrieta, CA
Verizon FIOS

Add me to the list...sporadic and extreme latency fluctuations crippling my gameplay.

Tracing route to 206.16.119.45 over a maximum of 30 hops.

1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 6 ms 6 ms 6 ms L100.LSANCA-VFTTP-86.verizon-gni.net [96.229.107.1]
3 14 ms 16 ms 16 ms G0-3-4-5.LSANCA-LCR-21.verizon-gni.net [130.81.182.142]
4 13 ms 11 ms 12 ms so-6-0-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81.29.124]
5 11 ms 11 ms 11 ms 0.xe-3-0-0.BR3.LAX15.ALTER.NET [152.63.114.241]
6 * 11 ms 11 ms 192.205.35.161
7 22 ms 28 ms 24 ms cr1.la2ca.ip.att.net [12.123.132.129]
8 28 ms 26 ms 21 ms cr2.phmaz.ip.att.net [12.122.31.190]
9 21 ms 22 ms 34 ms 12.123.206.225
10 22 ms 26 ms 22 ms 12-122-254-50.attens.net [12.122.254.50]
11 * 26 ms 24 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.

----------------------------------------------------------------------------------------------------------------------

Tracing route to 206.16.119.45 over a maximum of 30 hops

0 Robin-PC.home [192.168.1.10]
1 Wireless_Broadband_Router.home [192.168.1.1]
2 L100.LSANCA-VFTTP-86.verizon-gni.net [96.229.107.1]
3 G0-3-4-5.LSANCA-LCR-21.verizon-gni.net [130.81.182.142]
4 so-6-0-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81.29.124]
5 0.xe-3-0-0.BR3.LAX15.ALTER.NET [152.63.114.241]
6 192.205.35.161
7 cr1.la2ca.ip.att.net [12.123.132.129]
8 cr2.phmaz.ip.att.net [12.122.31.190]
9 12.123.206.225
10 12-122-254-50.attens.net [12.122.254.50]
11 mdf002c7613r0002-gig-10-1.phx1.attens.net [63.241.130.206]
12 * * *
Computing statistics for 275 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Robin-PC.home [192.168.1.10]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% Wireless_Broadband_Router.home [192.168.1.1]
0/ 100 = 0% |
2 15ms 0/ 100 = 0% 0/ 100 = 0% L100.LSANCA-VFTTP-86.verizon-gni.net [96.229.107.1]
0/ 100 = 0% |
3 14ms 2/ 100 = 2% 2/ 100 = 2% G0-3-4-5.LSANCA-LCR-21.verizon-gni.net [130.81.182.142]
0/ 100 = 0% |
4 14ms 0/ 100 = 0% 0/ 100 = 0% so-6-0-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81.29.124]
10/ 100 = 10% |
5 16ms 10/ 100 = 10% 0/ 100 = 0% 0.xe-3-0-0.BR3.LAX15.ALTER.NET [152.63.114.241]
1/ 100 = 1% |
6 16ms 11/ 100 = 11% 0/ 100 = 0% 192.205.35.161
89/ 100 = 89% |
7 --- 100/ 100 =100% 0/ 100 = 0% cr1.la2ca.ip.att.net [12.123.132.129]
0/ 100 = 0% |
8 --- 100/ 100 =100% 0/ 100 = 0% cr2.phmaz.ip.att.net [12.122.31.190]
0/ 100 = 0% |
9 --- 100/ 100 =100% 0/ 100 = 0% 12.123.206.225
0/ 100 = 0% |
10 --- 100/ 100 =100% 0/ 100 = 0% 12-122-254-50.attens.net [12.122.254.50]
0/ 100 = 0% |
11 --- 100/ 100 =100% 0/ 100 = 0% mdf002c7613r0002-gig-10-1.phx1.attens.net [63.241.130.206]

Trace complete.
90 Draenei Mage
15755
I've been having serious latency/lag issues for the past two weeks. Am on the Silvermoon server and in New York City. The game is unplayable in the evenings especially. I have been a Verizon Fios customer for several years and have played on the same server without any problems.


Tracing route to 12.129.209.68 over a maximum of 30 hops

1 67 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 8 ms 7 ms 6 ms L100.NYCMNY-VFTTP-161.verizon-gni.net [98.113.150.1]
3 13 ms 9 ms 9 ms G0-1-3-5.NYCMNY-LCR-22.verizon-gni.net [130.81.139.52]
4 8 ms 7 ms 8 ms so-6-1-0-0.NY5030-BB-RTR2.verizon-gni.net [130.81.151.224]
5 9 ms 9 ms 9 ms 0.xe-1-1-1.BR2.NYC4.ALTER.NET [152.63.23.169]
6 9 ms 9 ms 9 ms 192.205.36.57
7 80 ms 81 ms 77 ms cr1.n54ny.ip.att.net [12.122.86.6]
8 116 ms 92 ms 92 ms cr2.cgcil.ip.att.net [12.122.1.2]
9 89 ms 87 ms 86 ms cr1.cgcil.ip.att.net [12.122.2.53]
10 * * * Request timed out.
11 91 ms 89 ms 87 ms cr1.slkut.ip.att.net [12.122.30.25]
12 96 ms 99 ms 99 ms cr2.la2ca.ip.att.net [12.122.30.30]
13 83 ms 84 ms 86 ms gar29.la2ca.ip.att.net [12.122.129.241]
14 88 ms 174 ms 86 ms 12-122-254-238.attens.net [12.122.254.238]


Still having the same issues except that it's occurring at all times of the day now. Did a pathping during the latest latency spike:

Tracing route to 12.129.209.68 over a maximum of 30 hops

0 Luba-PC.home [192.168.1.5]
1 Wireless_Broadband_Router.home [192.168.1.1]
2 L100.NYCMNY-VFTTP-161.verizon-gni.net [98.113.150.1]
3 G0-1-3-5.NYCMNY-LCR-22.verizon-gni.net [130.81.139.52]
4 so-6-1-0-0.NY5030-BB-RTR2.verizon-gni.net [130.81.151.224]
5 0.xe-1-1-1.BR2.NYC4.ALTER.NET [152.63.23.169]
6 192.205.36.57
7 * * *
Computing statistics for 150 seconds...
Edited by Allswell on 2/9/2013 2:12 PM PST
43 Gnome Mage
8330
Wyrmrest Accord and also happening on Diablo 3
Stony Point, New York

I've been having issues since 1/29/13. The latency soars to several thousand ms, and stays there for up to a half hour, usually during the hours of 4pm-10pm EST. (But it has happened outside of this time frame.) The game hangs, and I can only exit out by using alt-f4, or closing the program from Windows. These issues do not seem to be affecting other non-Blizzard games, or web browsing, but when they first surfaced I had trouble accessing any Blizzard websites.

I've documented this issue extensively with both GM Vladosiky, and Verizon. Ticket US35136548 I've posted several tracert's in that ticket, and here's two of them, along with a pathping.

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 7 ms 7 ms 6 ms L100.NYCMNY-VFTTP-88.verizon-gni.net [96.246.53.1]
3 12 ms 12 ms 11 ms G0-11-4-5.NYCMNY-LCR-21.verizon-gni.net [130.81.137.68]
4 24 ms 21 ms 12 ms ae0-0.NY325-BB-RTR2.verizon-gni.net [130.81.209.110]
5 * * * Request timed out.
6 48 ms 47 ms 46 ms 192.205.34.49
7 118 ms * 118 ms cr2.n54ny.ip.att.net [12.122.86.10]
8 120 ms 119 ms 117 ms cr2.wswdc.ip.att.net [12.122.3.38]
9 121 ms 120 ms 120 ms cr1.attga.ip.att.net [12.122.1.173]
10 96 ms 96 ms 94 ms cr2.dlstx.ip.att.net [12.122.28.174]
11 * 125 ms * cr1.dlstx.ip.att.net [12.122.1.209]
12 131 ms * 129 ms cr1.phmaz.ip.att.net [12.122.28.182]
13 90 ms 90 ms 89 ms 12.123.206.157
14 135 ms 290 ms 191 ms 12-122-254-50.attens.net [12.122.254.50]
15 125 ms 128 ms 127 ms mdf002c7613r0002-gig-10-1.phx1.attens.net [63.241.130.206]
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.


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 7 ms 7 ms 7 ms L100.NYCMNY-VFTTP-88.verizon-gni.net [96.246.53.1]
3 9 ms 11 ms 12 ms G0-11-4-5.NYCMNY-LCR-21.verizon-gni.net [130.81.137.68]
4 82 ms 11 ms 17 ms ae0-0.NY325-BB-RTR2.verizon-gni.net [130.81.209.110]
5 * * * Request timed out.
6 11 ms 10 ms 9 ms 192.205.34.49
7 106 ms 102 ms 102 ms cr2.n54ny.ip.att.net [12.122.86.10]
8 99 ms 101 ms 99 ms cr2.wswdc.ip.att.net [12.122.3.38]
9 100 ms 99 ms 101 ms cr1.attga.ip.att.net [12.122.1.173]
10 105 ms 106 ms 109 ms cr2.dlstx.ip.att.net [12.122.28.174]
11 97 ms 94 ms 97 ms cr1.dlstx.ip.att.net [12.122.1.209]
12 96 ms 95 ms 97 ms cr1.phmaz.ip.att.net [12.122.28.182]
13 102 ms 104 ms 104 ms 12.123.206.157
14 126 ms 210 ms 202 ms 12-122-254-50.attens.net [12.122.254.50]
15 79 ms 79 ms 85 ms mdf002c7613r0002-gig-10-1.phx1.attens.net [63.241.130.206]
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.


Tracing route to mdf1-bi8k-1-ve-87.phx1.attens.net [63.241.138.161]
over a maximum of 30 hops:
0 Weevil-PC.home [192.168.1.3]
1 Wireless_Broadband_Router.home [192.168.1.1]
2 L100.NYCMNY-VFTTP-88.verizon-gni.net [96.246.53.1]
3 G0-11-4-5.NYCMNY-LCR-21.verizon-gni.net [130.81.137.68]
4 ae0-0.NY325-BB-RTR2.verizon-gni.net [130.81.209.110]
5 * 0.xe-11-0-0.BR2.NYC4.ALTER.NET [152.63.20.221]
6 192.205.34.49
7 cr2.n54ny.ip.att.net [12.122.86.10]
8 cr2.wswdc.ip.att.net [12.122.3.38]
9 cr1.attga.ip.att.net [12.122.1.173]
10 cr2.dlstx.ip.att.net [12.122.28.174]
11 cr1.dlstx.ip.att.net [12.122.1.209]
12 cr1.phmaz.ip.att.net [12.122.28.182]
13 12.123.206.157
14 12-122-254-50.attens.net [12.122.254.50]
15 mdf002c7613r0002-gig-10-1.phx1.attens.net [63.241.130.206]
16 * * *
Computing statistics for 375 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Weevil-PC.home [192.168.1.3]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% Wireless_Broadband_Router.home [192.168.1.1]
0/ 100 = 0% |
2 7ms 0/ 100 = 0% 0/ 100 = 0% L100.NYCMNY-VFTTP-88.verizon-gni.net [96.246.53.1]
0/ 100 = 0% |
3 11ms 0/ 100 = 0% 0/ 100 = 0% G0-11-4-5.NYCMNY-LCR-21.verizon-gni.net [130.81.137.68]
0/ 100 = 0% |
4 15ms 0/ 100 = 0% 0/ 100 = 0% ae0-0.NY325-BB-RTR2.verizon-gni.net [130.81.209.110]
0/ 100 = 0% |
5 57ms 0/ 100 = 0% 0/ 100 = 0% 0.xe-11-0-0.BR2.NYC4.ALTER.NET [152.63.20.221]
0/ 100 = 0% |
6 44ms 0/ 100 = 0% 0/ 100 = 0% 192.205.34.49
100/ 100 =100% |
7 --- 100/ 100 =100% 0/ 100 = 0% cr2.n54ny.ip.att.net [12.122.86.10]
0/ 100 = 0% |
8 --- 100/ 100 =100% 0/ 100 = 0% cr2.wswdc.ip.att.net [12.122.3.38]
0/ 100 = 0% |
9 --- 100/ 100 =100% 0/ 100 = 0% cr1.attga.ip.att.net [12.122.1.173]
0/ 100 = 0% |
10 --- 100/ 100 =100% 0/ 100 = 0% cr2.dlstx.ip.att.net [12.122.28.174]
0/ 100 = 0% |
11 --- 100/ 100 =100% 0/ 100 = 0% cr1.dlstx.ip.att.net [12.122.1.209]
0/ 100 = 0% |
12 --- 100/ 100 =100% 0/ 100 = 0% cr1.phmaz.ip.att.net [12.122.28.182]
0/ 100 = 0% |
13 --- 100/ 100 =100% 0/ 100 = 0% 12.123.206.157
0/ 100 = 0% |
14 --- 100/ 100 =100% 0/ 100 = 0% 12-122-254-50.attens.net [12.122.254.50]
0/ 100 = 0% |
15 --- 100/ 100 =100% 0/ 100 = 0% mdf002c7613r0002-gig-10-1.phx1.attens.net [63.241.130.206]

Trace complete.
Edited by Egnormous on 2/9/2013 6:17 AM PST
Realm: Area-52 US
Location: Riverside, CA
Description:
Random spikes, most severe during peak hours. 3-6k ms. While I see everyone running in place, raid members saw my dead body jumping around during a raid encounter.

Trace Route:

Tracing route to 63.240.104.93 over a maximum of 17 hops

1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 6 ms 4 ms 4 ms L100.LSANCA-VFTTP-99.verizon-gni.net [98.112.16.1]
3 25 ms 4 ms 9 ms G0-10-3-3.LSANCA-LCR-22.verizon-gni.net [130.81.133.104]
4 8 ms 6 ms 7 ms ae0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.22.246]
5 6 ms 6 ms 7 ms 0.xe-4-0-0.BR3.LAX15.ALTER.NET [152.63.115.61]
6 18 ms 67 ms 6 ms 204.255.168.134
7 108 ms 86 ms 84 ms cr2.la2ca.ip.att.net [12.123.30.134]
8 83 ms 83 ms 84 ms cr1.slkut.ip.att.net [12.122.30.29]
9 85 ms 87 ms 86 ms cr2.dvmco.ip.att.net [12.122.30.26]
10 82 ms 84 ms 81 ms cr1.cgcil.ip.att.net [12.122.31.86]
11 85 ms 86 ms 84 ms cr1.cl2oh.ip.att.net [12.122.2.206]
12 87 ms 81 ms 84 ms cr2.cl2oh.ip.att.net [12.122.2.126]
13 83 ms 81 ms 84 ms cr2.phlpa.ip.att.net [12.122.2.210]
14 83 ms 81 ms 82 ms gar1.pitpa.ip.att.net [12.122.107.85]
15 90 ms 87 ms 89 ms 12-122-254-242.attens.net [12.122.254.242]
16 82 ms 81 ms 79 ms mdf001c7613r0004-gig-12-1.nyc3.attens.net [63.240.65.14]
17 * * * Request timed out.

Trace complete.


Pathping:

Tracing route to 63.240.104.93 over a maximum of 30 hops

0 Elliott-PC.home [192.168.1.3]
1 Wireless_Broadband_Router.home [192.168.1.1]
2 L100.LSANCA-VFTTP-99.verizon-gni.net [98.112.16.1]
3 G0-10-3-3.LSANCA-LCR-22.verizon-gni.net [130.81.133.104]
4 ae0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.22.246]
5 0.xe-4-0-0.BR3.LAX15.ALTER.NET [152.63.115.61]
6 204.255.168.134
7 cr2.la2ca.ip.att.net [12.123.30.150]
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 Elliott-PC.home [192.168.1.3]
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-99.verizon-gni.net [98.112.16.1]
0/ 100 = 0% |
3 8ms 0/ 100 = 0% 0/ 100 = 0% G0-10-3-3.LSANCA-LCR-22.verizon-gni.net [130.81.133.104]
0/ 100 = 0% |
4 12ms 0/ 100 = 0% 0/ 100 = 0% ae0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.22.246]
0/ 100 = 0% |
5 10ms 0/ 100 = 0% 0/ 100 = 0% 0.xe-4-0-0.BR3.LAX15.ALTER.NET [152.63.115.61]
0/ 100 = 0% |
6 12ms 0/ 100 = 0% 0/ 100 = 0% 204.255.168.134
100/ 100 =100% |
7 --- 100/ 100 =100% 0/ 100 = 0% cr2.la2ca.ip.att.net [12.123.30.150]
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.
90 Blood Elf Priest
0
Realm: Area 52
Your Location: Thousand Oaks, CA
Brief Description of Issue: Latency spikes (up to 22k world or 13k home, usually just world but sometimes just home) and lag spikes without latency increase (screen freezes for 5-30s then catches up in fast motion) make it impossible to play. Phenomenon limited to a random duration between 7:30PM and 11PM PST.

Tracert/Pathping (taken last night around 9:30PM, observed home was sitting at an unplayble 2200ms) to Area 52:
Tracing route to 199.107.24.244 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 5 ms 9 ms 10 ms L100.LSANCA-VFTTP-90.verizon-gni.net [173.55.183.1]
3 21 ms 14 ms 11 ms G0-6-4-0.LSANCA-LCR-21.verizon-gni.net [130.81.109.228]
4 13 ms * 29 ms so-3-1-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81.151.236]
5 11 ms 7 ms 10 ms 0.xe-3-0-0.BR3.LAX15.ALTER.NET [152.63.114.241]
6 * 14 ms 9 ms 204.255.168.134
7 87 ms 90 ms 122 ms cr2.la2ca.ip.att.net [12.123.30.134]
8 89 ms 89 ms 86 ms cr1.slkut.ip.att.net [12.122.30.29]
9 88 ms 87 ms 87 ms cr2.dvmco.ip.att.net [12.122.30.26]
10 85 ms 88 ms 88 ms cr1.cgcil.ip.att.net [12.122.31.86]
11 98 ms * 89 ms cr2.cgcil.ip.att.net [12.122.2.54]
12 85 ms 87 ms 87 ms cr1.n54ny.ip.att.net [12.122.1.1]
13 88 ms 93 ms 82 ms gar1.nw2nj.ip.att.net [12.122.131.81]
14 88 ms 89 ms 87 ms 12.122.251.6
15 * 86 ms 87 ms mdf001c7613r0003-gig-12-1.nyc3.attens.net [63.240.65.22]
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.

Tracing route to 199.107.24.244 over a maximum of 30 hops

0 ThousandSunny.home [192.168.1.2]
1 Wireless_Broadband_Router.home [192.168.1.1]
2 L100.LSANCA-VFTTP-90.verizon-gni.net [173.55.183.1]
3 G0-6-4-0.LSANCA-LCR-21.verizon-gni.net [130.81.109.228]
4 so-3-1-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81.151.236]
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 cr2.cgcil.ip.att.net [12.122.2.54]
12 cr1.n54ny.ip.att.net [12.122.1.1]
13 * * gar1.nw2nj.ip.att.net [12.122.131.81]
14 12.122.251.10
15 mdf001c7613r0003-gig-12-1.nyc3.attens.net [63.240.65.22]
16 * * *
Computing statistics for 375 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 ThousandSunny.home [192.168.1.2]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% Wireless_Broadband_Router.home [192.168.1.1]
0/ 100 = 0% |
2 20ms 0/ 100 = 0% 0/ 100 = 0% L100.LSANCA-VFTTP-90.verizon-gni.net [173.55.183.1]
0/ 100 = 0% |
3 22ms 0/ 100 = 0% 0/ 100 = 0% G0-6-4-0.LSANCA-LCR-21.verizon-gni.net [130.81.109.228]
0/ 100 = 0% |
4 27ms 0/ 100 = 0% 0/ 100 = 0% so-3-1-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81.151.236]
8/ 100 = 8% |
5 33ms 8/ 100 = 8% 0/ 100 = 0% 0.xe-3-0-0.BR3.LAX15.ALTER.NET [152.63.114.241]
1/ 100 = 1% |
6 27ms 9/ 100 = 9% 0/ 100 = 0% 204.255.168.134
91/ 100 = 91% |
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% cr2.cgcil.ip.att.net [12.122.2.54]
0/ 100 = 0% |
12 --- 100/ 100 =100% 0/ 100 = 0% cr1.n54ny.ip.att.net [12.122.1.1]
0/ 100 = 0% |
13 --- 100/ 100 =100% 0/ 100 = 0% gar1.nw2nj.ip.att.net [12.122.131.81]
0/ 100 = 0% |
14 --- 100/ 100 =100% 0/ 100 = 0% 12.122.251.10
0/ 100 = 0% |
15 --- 100/ 100 =100% 0/ 100 = 0% mdf001c7613r0003-gig-12-1.nyc3.attens.net [63.240.65.22]

Trace complete.


Tracert/Pathping to login server:
Tracing route to us.logon.battle.net [12.129.206.130]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 7 ms 9 ms 8 ms L100.LSANCA-VFTTP-90.verizon-gni.net [173.55.183.1]
3 18 ms 19 ms 16 ms G0-6-4-0.LSANCA-LCR-21.verizon-gni.net [130.81.109.228]
4 10 ms 13 ms 15 ms so-3-1-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81.151.236]
5 10 ms 9 ms 9 ms 0.xe-9-0-0.BR3.LAX15.ALTER.NET [152.63.114.245]
6 16 ms 18 ms 12 ms 204.255.168.134
7 14 ms 20 ms 23 ms cr2.la2ca.ip.att.net [12.123.30.134]
8 10 ms 9 ms 10 ms gar20.la2ca.ip.att.net [12.122.128.181]
9 16 ms 11 ms 8 ms 12-122-254-234.attens.net [12.122.254.234]
10 17 ms 17 ms 10 ms mdf001c7613r0002.lax1.attens.net [206.16.68.54]
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.

Tracing route to us.logon.battle.net [12.129.206.130]
over a maximum of 30 hops:
0 ThousandSunny.home [192.168.1.2]
1 Wireless_Broadband_Router.home [192.168.1.1]
2 L100.LSANCA-VFTTP-90.verizon-gni.net [173.55.183.1]
3 G0-6-4-0.LSANCA-LCR-21.verizon-gni.net [130.81.109.228]
4 so-3-1-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81.151.236]
5 0.xe-9-0-0.BR3.LAX15.ALTER.NET [152.63.114.245]
6 204.255.168.134
7 cr1.la2ca.ip.att.net [12.123.132.129]
8 gar29.la2ca.ip.att.net [12.122.129.241]
9 12.122.251.190
10 mdf001c7613r0002.lax1.attens.net [206.16.68.54]
11 * * *
Computing statistics for 250 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 ThousandSunny.home [192.168.1.2]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% Wireless_Broadband_Router.home [192.168.1.1]
0/ 100 = 0% |
2 10ms 0/ 100 = 0% 0/ 100 = 0% L100.LSANCA-VFTTP-90.verizon-gni.net [173.55.183.1]
0/ 100 = 0% |
3 12ms 1/ 100 = 1% 1/ 100 = 1% G0-6-4-0.LSANCA-LCR-21.verizon-gni.net [130.81.109.228]
0/ 100 = 0% |
4 15ms 0/ 100 = 0% 0/ 100 = 0% so-3-1-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81.151.236]
6/ 100 = 6% |
5 17ms 6/ 100 = 6% 0/ 100 = 0% 0.xe-9-0-0.BR3.LAX15.ALTER.NET [152.63.114.245]
2/ 100 = 2% |
6 16ms 8/ 100 = 8% 0/ 100 = 0% 204.255.168.134
92/ 100 = 92% |
7 --- 100/ 100 =100% 0/ 100 = 0% cr1.la2ca.ip.att.net [12.123.132.129]
0/ 100 = 0% |
8 --- 100/ 100 =100% 0/ 100 = 0% gar29.la2ca.ip.att.net [12.122.129.241]
0/ 100 = 0% |
9 --- 100/ 100 =100% 0/ 100 = 0% 12.122.251.190
0/ 100 = 0% |
10 --- 100/ 100 =100% 0/ 100 = 0% mdf001c7613r0002.lax1.attens.net [206.16.68.54]

Trace complete.


As a point of comparison, this is what my tracert/pathping to A52 looks like right now (and I'm sitting perfectly happy at 86ms world/83ms home):

Tracing route to 199.107.24.244 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 14 ms 9 ms 9 ms L100.LSANCA-VFTTP-90.verizon-gni.net [173.55.183
.1]
3 15 ms 11 ms 14 ms G0-6-4-0.LSANCA-LCR-21.verizon-gni.net [130.81.1
09.228]
4 9 ms 10 ms 8 ms so-3-1-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81
.151.236]
5 12 ms 9 ms 9 ms 0.xe-3-0-0.BR3.LAX15.ALTER.NET [152.63.114.241]

6 11 ms 10 ms 9 ms 204.255.168.134
7 87 ms 86 ms 88 ms cr2.la2ca.ip.att.net [12.123.30.134]
8 94 ms 87 ms 86 ms cr1.slkut.ip.att.net [12.122.30.29]
9 92 ms 87 ms 88 ms cr2.dvmco.ip.att.net [12.122.30.26]
10 91 ms 88 ms 90 ms cr1.cgcil.ip.att.net [12.122.31.86]
11 90 ms 88 ms 91 ms cr1.cl2oh.ip.att.net [12.122.2.206]
12 95 ms 87 ms 87 ms cr2.cl2oh.ip.att.net [12.122.2.126]
13 95 ms 97 ms 86 ms cr2.phlpa.ip.att.net [12.122.2.210]
14 85 ms 88 ms 88 ms gar1.pitpa.ip.att.net [12.122.107.85]
15 87 ms 90 ms 98 ms 12-122-254-242.attens.net [12.122.254.242]
16 81 ms 87 ms 88 ms mdf001c7613r0004-gig-12-1.nyc3.attens.net [63.24
0.65.14]
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.

Tracing route to 199.107.24.244 over a maximum of 30 hops

0 ThousandSunny.home [192.168.1.2]
1 Wireless_Broadband_Router.home [192.168.1.1]
2 L100.LSANCA-VFTTP-90.verizon-gni.net [173.55.183.1]
3 G0-6-4-0.LSANCA-LCR-21.verizon-gni.net [130.81.109.228]
4 so-3-1-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81.151.236]
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.150]
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.251.2
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 ThousandSunny.home [192.168.1.2]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% Wireless_Broadband_Router.home [19
2.168.1.1]
0/ 100 = 0% |
2 10ms 0/ 100 = 0% 0/ 100 = 0% L100.LSANCA-VFTTP-90.verizon-gni.n
et [173.55.183.1]
0/ 100 = 0% |
3 13ms 0/ 100 = 0% 0/ 100 = 0% G0-6-4-0.LSANCA-LCR-21.verizon-gni
.net [130.81.109.228]
0/ 100 = 0% |
4 16ms 0/ 100 = 0% 0/ 100 = 0% so-3-1-0-0.LAX01-BB-RTR1.verizon-g
ni.net [130.81.151.236]
0/ 100 = 0% |
5 15ms 0/ 100 = 0% 0/ 100 = 0% 0.xe-3-0-0.BR3.LAX15.ALTER.NET [15
2.63.114.241]
0/ 100 = 0% |
6 14ms 0/ 100 = 0% 0/ 100 = 0% 204.255.168.134
100/ 100 =100% |
7 --- 100/ 100 =100% 0/ 100 = 0% cr2.la2ca.ip.att.net [12.123.30.15
0]
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.251.2
0/ 100 = 0% |
16 --- 100/ 100 =100% 0/ 100 = 0% mdf001c7613r0004-gig-12-1.nyc3.att
ens.net [63.240.65.14]

Trace complete.
90 Tauren Druid
10580
Realm: Spirestone
Location: Rockland County, NY

Same issue as many reporting here. I have had intermittent issues for the past week or so, usually at night (8:30PM EST-11:30PM EST), but just began having issues a few minutes ago. The problem manifests as steadily increasing latency over a minute or so (350ms+) and then suddenly it is as if the connection has been severed, though I am still in game. I have left the game sitting there upwards of ten minutes without actually getting disconnected. It's akin to a character in a movie or TV show freezing time, then wandering around. Chat response is delayed but not completely cut off.

Pathping:

Tracing route to 12.129.222.155 over a maximum of 30 hops

0 <origin>
1 <firewall>
2 l101.nycmny-vfttp-88.verizon-gni.net [72.89.152.1]
3 g0-3-5-0.nycmny-lcr-21.verizon-gni.net [130.81.180.46]
4 so-5-0-0-0.ny325-bb-rtr2.verizon-gni.net [130.81.22.16]
5 0.xe-3-2-0.BR2.NYC4.ALTER.NET [152.63.20.213]
6 192.205.36.57
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 * * cr2.dvmco.ip.att.net [12.122.31.85]
11 * cr1.slkut.ip.att.net [12.122.30.25]
12 * cr2.la2ca.ip.att.net [12.122.30.30]
13 * * *
Computing statistics for 300 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 <origin>
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% <firewall>
0/ 100 = 0% |
2 2ms 0/ 100 = 0% 0/ 100 = 0% l101.nycmny-vfttp-88.verizon-gni.net [72.89.152.1]
0/ 100 = 0% |
3 5ms 0/ 100 = 0% 0/ 100 = 0% g0-3-5-0.nycmny-lcr-21.verizon-gni.net [130.81.180.46]
0/ 100 = 0% |
4 9ms 0/ 100 = 0% 0/ 100 = 0% so-5-0-0-0.ny325-bb-rtr2.verizon-gni.net [130.81.22.16]
0/ 100 = 0% |
5 28ms 1/ 100 = 1% 1/ 100 = 1% 0.xe-3-2-0.BR2.NYC4.ALTER.NET [152.63.20.213]
0/ 100 = 0% |
6 16ms 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% 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]
0/ 100 = 0% |
10 --- 100/ 100 =100% 0/ 100 = 0% cr2.dvmco.ip.att.net [12.122.31.85]
0/ 100 = 0% |
11 --- 100/ 100 =100% 0/ 100 = 0% cr1.slkut.ip.att.net [12.122.30.25]
0/ 100 = 0% |
12 --- 100/ 100 =100% 0/ 100 = 0% cr2.la2ca.ip.att.net [12.122.30.30]

Trace complete.


Here is an updated pathping as well. This time I actually got ejected from the game, along with an Error #2 when trying to log back in to test. I ran this twice to verify results:

Tracing route to 12.129.222.155 over a maximum of 30 hops

0 <origin>
1 <firewall>
2 l101.nycmny-vfttp-88.verizon-gni.net [72.89.152.1]
3 g0-3-5-0.nycmny-lcr-21.verizon-gni.net [130.81.180.46]
4 so-5-0-0-0.ny325-bb-rtr2.verizon-gni.net [130.81.22.16]
5 0.xe-3-2-0.BR2.NYC4.ALTER.NET [152.63.20.213]
6 192.205.36.57
7 * * *
Computing statistics for 150 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 <origin>
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% <firewall>
0/ 100 = 0% |
2 4ms 0/ 100 = 0% 0/ 100 = 0% l101.nycmny-vfttp-88.verizon-gni.net [72.89.152.1]
0/ 100 = 0% |
3 6ms 0/ 100 = 0% 0/ 100 = 0% g0-3-5-0.nycmny-lcr-21.verizon-gni.net [130.81.180.46]
0/ 100 = 0% |
4 9ms 0/ 100 = 0% 0/ 100 = 0% so-5-0-0-0.ny325-bb-rtr2.verizon-gni.net [130.81.22.16]
0/ 100 = 0% |
5 24ms 0/ 100 = 0% 0/ 100 = 0% 0.xe-3-2-0.BR2.NYC4.ALTER.NET [152.63.20.213]
0/ 100 = 0% |
6 9ms 0/ 100 = 0% 0/ 100 = 0% 192.205.36.57

Trace complete.
Edited by Paidhima on 2/8/2013 2:11 PM PST
90 Pandaren Monk
8175
Performed tracert as problems began occurring, 507 PM US Eastern (Live in NY), connecting to Bonechewer (Western server)
Problems have gone on for a few days, really peaked today.
EDIT
Also now can no longer connect, just hangs. Deleted cache, wtf, and interface to no avail.
Was getting booted on and off battle.net (in game) last night.
Thanks!

Tracing route to 12.129.209.68 over a maximum of 30 hops

1 1 ms <1 ms <1 ms Wireless_Broadband_Route
2 8 ms 6 ms 7 ms 74.108.107.1
3 13 ms 12 ms 9 ms G0-14-2-6.NYCMNY-LCR-21.
96.170]
4 10 ms 11 ms 9 ms 130.81.151.228
5 32 ms 31 ms 31 ms 0.xe-3-2-0.BR2.NYC4.ALTE
6 44 ms 47 ms 49 ms 192.205.34.49
7 80 ms 77 ms 79 ms cr1.n54ny.ip.att.net [12
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 130 ms 128 ms 124 ms cr1.slkut.ip.att.net [12
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.
Edited by Maxbaer on 2/8/2013 2:15 PM PST
90 Tauren Death Knight
4815
server-Borean Tundra-US
Greenwich Connecticut

switched to fios recently, no problem til about 3 days ago or so, disconnecting frequently, need to fight with my PC to even connect to battle.net website, gameplay is super slow if it decides to work.... have a 8gbRAM pc with 3.14ghz i7.... my PC is far from slow so something must be wrong here... lacency spikes up to 2k and sometimes higher, certain parts of the day it seems to work ok but that could be just luck of the draw because i know time of day shouldnt change connections to my knowledge... but this always seems to happen in the middle of a raid or battleground, which is when im the most into it.. here is tracert info, was told to try to get both on here.. ran them both several times, this was the most info i could get out of the runs..

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 4 ms 4 ms 4 ms L100.NYCMNY-VFTTP-154.verizon-gni.net [96.232.127.1]
3 9 ms 9 ms 7 ms G0-11-3-4.NYCMNY-LCR-22.verizon-gni.net [130.81.139.38]
4 5 ms 5 ms 5 ms so-3-1-0-0.NY5030-BB-RTR1.verizon-gni.net [130.81.151.234]
5 * * * Request timed out.
6 54 ms 51 ms 52 ms 192.205.36.57
7 * * * Request timed out.
8 127 ms 127 ms * cr2.wswdc.ip.att.net [12.122.3.38]
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * 128 ms * cr1.phmaz.ip.att.net [12.122.28.182]
13 * 140 ms * cr1.phmaz.ip.att.net [12.123.206.185]
14 75 ms 160 ms 81 ms 12-122-254-50.attens.net [12.122.254.50]
15 * 129 ms * mdf002c7613r0002-gig-10-1.phx1.attens.net [63.241.130.206]
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 * *

and here is pathping stuff if we need to show this..

0/ 100 = 0% |
1 1ms 0/ 100 = 0% 0/ 100 = 0% Wireless_Broadband_Router.home [192.168.1.1]
0/ 100 = 0% |
2 9ms 1/ 100 = 1% 1/ 100 = 1% L100.NYCMNY-VFTTP-154.verizon-gni.net [96.232.127.1]
0/ 100 = 0% |
3 8ms 0/ 100 = 0% 0/ 100 = 0% G0-11-3-4.NYCMNY-LCR-22.verizon-gni.net [130.81.139.38]
0/ 100 = 0% |
4 16ms 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 57ms 13/ 100 = 13% 13/ 100 = 13% 0.xe-3-3-0.BR2.NYC4.ALTER.NET [152.63.23.133]
0/ 100 = 0% |
6 65ms 0/ 100 = 0% 0/ 100 = 0% 192.205.36.57

Trace complete.



i dont really know what all these codes mean hope these issues can be resolved asap
Edited by Salazarr on 2/10/2013 10:28 PM PST
90 Gnome Rogue
aus
15205
Proudmoore
Brooklyn, NY
Lag spikes occuring roughly the same time each night (9-10pm Eastern) and lasting for an hour or so. Normally play with about 80-90, but latency spikes up to about 5600 at times. Eventually will just lead to a disconnect and a long wait before I can get log back in.

Pathping and traces are from the other night. Once it happens tonight I'll repost.

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 4 ms 4 ms 3 ms L101.NYCMNY-VFTTP-44.verizon-gni.net [98.116.149.1]
3 8 ms 6 ms 8 ms G0-14-0-6.NYCMNY-LCR-22.verizon-gni.net [130.81.189.232]
4 41 ms 124 ms 53 ms ae0-0.NY5030-BB-RTR2.verizon-gni.net [130.81.209.126]
5 8 ms 7 ms 7 ms 0.xe-1-1-1.BR2.NYC4.ALTER.NET [152.63.23.169]
6 41 ms 40 ms 42 ms 192.205.36.57
7 110 ms 111 ms 111 ms cr1.n54ny.ip.att.net [12.122.86.6]
8 96 ms 91 ms 95 ms cr2.cgcil.ip.att.net [12.122.1.2]
9 104 ms 108 ms 106 ms cr1.cgcil.ip.att.net [12.122.2.53]
10 109 ms 110 ms 113 ms cr2.dvmco.ip.att.net [12.122.31.85]
11 109 ms 109 ms 111 ms cr1.slkut.ip.att.net [12.122.30.25]
12 108 ms 109 ms 106 ms cr2.la2ca.ip.att.net [12.122.30.30]
13 90 ms 129 ms 125 ms gar29.la2ca.ip.att.net [12.122.129.241]
14 195 ms 89 ms 89 ms 12-122-254-238.attens.net [12.122.254.238]
15 90 ms 91 ms 89 ms mdf001c7613r0002.lax1.attens.net [206.16.68.54]
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.


Tracing route to 12.129.209.68 over a maximum of 30 hops

0 odziozo-PC.home [192.168.1.3]
1 Wireless_Broadband_Router.home [192.168.1.1]
2 L101.NYCMNY-VFTTP-44.verizon-gni.net [98.116.149.1]
3 G0-14-0-6.NYCMNY-LCR-22.verizon-gni.net [130.81.189.232]
4 ae0-0.NY5030-BB-RTR2.verizon-gni.net [130.81.209.126]
5 0.xe-1-1-1.BR2.NYC4.ALTER.NET [152.63.23.169]
6 192.205.36.57
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 cr2.dvmco.ip.att.net [12.122.31.85]
11 cr1.slkut.ip.att.net [12.122.30.25]
12 cr2.la2ca.ip.att.net [12.122.30.30]
13 gar29.la2ca.ip.att.net [12.122.129.241]
14 * 12-122-254-238.attens.net [12.122.254.238]
15 mdf001c7613r0002.lax1.attens.net [206.16.68.54]
16 * * *
Computing statistics for 375 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 odziozo-PC.home [192.168.1.3]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% Wireless_Broadband_Router.home [192.168.1.1]
0/ 100 = 0% |
2 6ms 0/ 100 = 0% 0/ 100 = 0% L101.NYCMNY-VFTTP-44.verizon-gni.net [98.116.149.1]
0/ 100 = 0% |
3 8ms 0/ 100 = 0% 0/ 100 = 0% G0-14-0-6.NYCMNY-LCR-22.verizon-gni.net [130.81.189.232]
0/ 100 = 0% |
4 20ms 0/ 100 = 0% 0/ 100 = 0% ae0-0.NY5030-BB-RTR2.verizon-gni.net [130.81.209.126]
0/ 100 = 0% |
5 31ms 0/ 100 = 0% 0/ 100 = 0% 0.xe-1-1-1.BR2.NYC4.ALTER.NET [152.63.23.169]
0/ 100 = 0% |
6 15ms 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% 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]
0/ 100 = 0% |
10 --- 100/ 100 =100% 0/ 100 = 0% cr2.dvmco.ip.att.net [12.122.31.85]
0/ 100 = 0% |
11 --- 100/ 100 =100% 0/ 100 = 0% cr1.slkut.ip.att.net [12.122.30.25]
0/ 100 = 0% |
12 --- 100/ 100 =100% 0/ 100 = 0% cr2.la2ca.ip.att.net [12.122.30.30]
0/ 100 = 0% |
13 --- 100/ 100 =100% 0/ 100 = 0% gar29.la2ca.ip.att.net [12.122.129.241]
0/ 100 = 0% |
14 --- 100/ 100 =100% 0/ 100 = 0% 12-122-254-238.attens.net [12.122.254.238]
0/ 100 = 0% |
15 --- 100/ 100 =100% 0/ 100 = 0% mdf001c7613r0002.lax1.attens.net [206.16.68.54]

Trace complete.
This topic is locked.

Please report any Code of Conduct violations, including:

Threats of violence. We take these seriously and will alert the proper authorities.

Posts containing personal information about other players. This includes physical addresses, e-mail addresses, phone numbers, and inappropriate photos and/or videos.

Harassing or discriminatory language. This will not be tolerated.

Forums Code of Conduct

Report Post # written by

Reason
Explain (256 characters max)
Submit Cancel

Reported!

[Close]