Verizon ISP Issues - Tracking

Technical Support
Prev 1 2 3 4 29 Next
Realm (if a WoW player): Sargeras
Your Location (city, state): Staten Island, NYC
Brief Description of Issue: I can't even connect to the game, all it does it throw me at the "Connecting" prompt.


Tracing route to 63.240.161.189 over a maximum of 30 hops

1 3 ms 3 ms 1 ms 192.168.1.1
2 9 ms 7 ms 8 ms L100.NYCMNY-VFTTP-140.verizon-gni.net [98.113.69.1]
3 7 ms 11 ms 11 ms G0-14-3-6.NYCMNY-LCR-22.verizon-gni.net [130.81.188.164]
4 12 ms 10 ms 15 ms so-3-1-0-0.NY5030-BB-RTR1.verizon-gni.net [130.81.151.234]
5 18 ms 12 ms 11 ms 0.xe-11-1-0.BR2.NYC4.ALTER.NET [152.63.23.137]
6 92 ms 90 ms 93 ms 192.205.34.49
7 * * * Request timed out.
8 51 ms 52 ms 50 ms cr2.cgcil.ip.att.net [12.122.1.2]
9 57 ms 60 ms 59 ms gar3.cgcil.ip.att.net [12.122.132.213]
10 229 ms 47 ms 84 ms 12.122.251.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.


Come cry with me in Staten Island LOL I'm so bored, especially with this blizzard going on.
Bleeding Hollow
Queens, NYC
For the past week, been experiencing major lag. Usually around the night time between 8-10. Today it started around 5pm EST and then about 30 minutes ago, it completely timed out. I was half way through a dungeon and everyone was running in place. I kept it open for 10 minutes but nothing was happening. The connection was up and down from 50-1500ms home and world. I played earlier today at around 3 and it was fine (around 50-80ms home and world, which is still slower than usual). When i tried to log back on after I got disconnected, I couldn't even log back in. My launcher screen was stuck on "initializing" for over 10 minutes.

I didn't have this issue until the beginning of this week. I started disconnecting and reconnecting onto battle.net. Even when I'm trying to maneuver around this website, I've been experiencing lag. But everything else works fine (steaming videos & movies, surfing the web). The internet has been flying. I've been doing speedtests getting 58mbps download and 15mbps upload. I purposely upgraded my FIOS internet plan 2 days ago thinking maybe my internet was slow from sharing it through my household. But even after the upgrade it is still giving me problems on WOW. I don't understand why this has not been fixed. Clearly people have been reporting this issue to Verizon and Blizzard. We are paying for this service and we can't even play it especially during peak hours.

this was from today after i got disconnected:
Tracing route to 64.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 12 ms 7 ms 6 ms L100.NYCMNY-VFTTP-48.verizon-gni.net [71.167.106.1]
3 9 ms 11 ms 7 ms G0-1-1-4.NYCMNY-LCR-21.verizon-gni.net [130.81.146.230]
4 26 ms 18 ms 9 ms so-11-0-0-0.NY325-BB-RTR1.verizon-gni.net [130.81.151.222]
5 46 ms 53 ms 33 ms 0.xe-9-0-0.BR2.NYC4.ALTER.NET [152.63.20.189]
6 39 ms 39 ms 41 ms 204.255.168.90
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
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.


this is from a couple days ago:

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 4 ms 6 ms 6 ms L100.NYCMNY-VFTTP-48.verizon-gni.net [71.167.106.1]
3 14 ms 8 ms 11 ms G0-1-1-3.NYCMNY-LCR-21.verizon-gni.net [130.81.188.74]
4 10 ms 9 ms 17 ms ae0-0.NY325-BB-RTR2.verizon-gni.net [130.81.209.110]
5 27 ms 29 ms 30 ms 0.xe-3-2-0.BR2.NYC4.ALTER.NET [152.63.20.213]
6 8 ms 10 ms 9 ms 192.205.36.57
7 * 58 ms 56 ms cr1.n54ny.ip.att.net [12.122.86.6]
8 39 ms 35 ms 38 ms cr2.cgcil.ip.att.net [12.122.1.2]
9 33 ms 38 ms 35 ms gar3.cgcil.ip.att.net [12.122.132.213]
10 35 ms 36 ms 36 ms 12.122.251.50
11 69 ms * 38 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.
Realm: Ner'Zhul / Proudmoore
Manhattan, NY, NY

Around the same time every evening my MS starts to spike and the game becomes unplayable.....

Location: New York City, NY.
ISP: Verizon FIOS

Tracing route to 12.129.209.68 over a maximum of 30 hops

1 15 ms 115 ms 80 ms Wireless_Broadband_Router.home [192.168.1.1]
2 59 ms 31 ms 48 ms L100.NYCMNY-VFTTP-209.verizon-gni.net [108.6.171
.1]
3 117 ms 59 ms 30 ms G0-3-3-7.NYCMNY-LCR-21.verizon-gni.net [130.81.1
77.82]
4 106 ms 16 ms * ae0-0.NY325-BB-RTR2.verizon-gni.net [130.81.209.
110]
5 * 51 ms 22 ms 0.xe-3-2-0.BR2.NYC4.ALTER.NET [152.63.20.213]
6 14 ms * 187 ms 192.205.34.49
7 182 ms 252 ms * cr1.n54ny.ip.att.net [12.122.86.6]
8 132 ms * 258 ms cr2.cgcil.ip.att.net [12.122.1.2]
9 100 ms 97 ms 97 ms cr1.cgcil.ip.att.net [12.122.2.53]
10 164 ms 339 ms 99 ms cr2.dvmco.ip.att.net [12.122.31.85]
11 108 ms 98 ms 98 ms cr1.slkut.ip.att.net [12.122.30.25]
12 98 ms 95 ms 102 ms cr2.la2ca.ip.att.net [12.122.30.30]
13 106 ms * 345 ms gar29.la2ca.ip.att.net [12.122.129.241]
14 99 ms 86 ms 87 ms 12.122.251.190
15 98 ms 102 ms 103 ms mdf001c7613r0004-gig-10-1.lax1.attens.net [12.12
9.193.250]
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.
Realm: Cenarion Circle
Location: Bronx, NYC
Problem: Abnormally high latency, connection issues, disconnection issues, lag
Verizon's response: It's not us, it must be Blizzard

1 wireless_broadband_router (192.168.1.1) 0.753 ms 0.431 ms 0.420 ms
2 l100.nycmny-vfttp-139.verizon-gni.net (72.68.137.1) 5.538 ms 5.323 ms 5.685 ms
3 g1-5-5-4.nycmny-lcr-21.verizon-gni.net (130.81.212.2) 9.606 ms 7.501 ms 8.201 ms
4 ae0-0.ny325-bb-rtr1.verizon-gni.net (130.81.209.102) 30.233 ms 6.797 ms 7.018 ms
5 0.xe-9-0-0.br2.nyc4.alter.net (152.63.20.189) 89.748 ms * *
6 192.205.34.49 (192.205.34.49) 78.803 ms 73.813 ms 74.024 ms
7 * * cr2.n54ny.ip.att.net (12.122.86.10) 132.892 ms
8 * * *
9 * cr1.attga.ip.att.net (12.122.1.173) 116.459 ms 119.553 ms
10 * * *
11 * * *
12 cr1.phmaz.ip.att.net (12.122.28.182) 110.017 ms 112.334 ms 112.413 ms
13 cr1.phmaz.ip.att.net (12.123.206.185) 103.552 ms 101.414 ms 103.537 ms
14 * * *
15 mdf002c7613r0001-gig-12-1.phx1.attens.net (63.241.130.210) 108.914 ms * 108.091 ms
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
31 * * *
32 * * *
33 * * *
34 * * *
35 * * *
36 * * *
37 * * *
38 * * *
39 * * *
40 * * *
41 * * *
42 * * *
43 * * *
44 * * *
45 * * *
46 * * *
47 * * *
48 * * *
49 * * *
50 * * *
51 * * *
52 * * *
53 * * *
54 * * *
55 * * *
56 * * *
57 * * *
58 * * *
59 * * *
60 * * *
61 * * *
62 * * *
63 * * *
64 * * *
Draka-US
Ozone Park, NY

Can't even log in. Takes ages to get to my character screen, and i get DCed after sitting at a loading screen.
Realm (if a WoW player): Bronzebeard
Your Location (city, state): Pittsburgh, PA
Brief Description of Issue: Experienced extreme latency and disconnections last night (though the information listed in the wow client still showed <100ms local and <140ms world). Issues connecting and getting disconnected today.

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 5 ms 5 ms 5 ms L100.PITBPA-VFTTP-20.verizon-gni.net [96.236.150.1]
3 6 ms 5 ms 5 ms G5-1-120.PITBPA-LCR-01.verizon-gni.net [130.81.129.28]
4 12 ms 12 ms 12 ms so-15-0-1-0.RES-BB-RTR1.verizon-gni.net [130.81.28.200]
5 17 ms 16 ms 17 ms 0.xe-4-3-0.BR1.IAD8.ALTER.NET [152.63.37.37]
6 17 ms 17 ms 17 ms 192.205.36.141
7 93 ms 93 ms 96 ms cr2.wswdc.ip.att.net [12.122.81.250]
8 105 ms 102 ms 104 ms cr1.cgcil.ip.att.net [12.122.18.21]
9 104 ms 103 ms 105 ms cr2.dvmco.ip.att.net [12.122.31.85]
10 93 ms 93 ms 96 ms cr1.slkut.ip.att.net [12.122.30.25]
11 106 ms 104 ms 108 ms cr2.la2ca.ip.att.net [12.122.30.30]
12 106 ms 106 ms 105 ms gar29.la2ca.ip.att.net [12.122.129.241]
13 94 ms 92 ms 103 ms 12.122.251.190
14 107 ms 105 ms 105 ms mdf001c7613r0003-gig-12-1.lax1.attens.net [12.129.193.254]
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.
Eitrigg
Baltimore, MD
Extreme latency on Eitrigg in Eastern Kingdoms

Tracing route to 12.129.209.68 over a maximum of 30 hops

1 4 ms 1 ms 3 ms Wireless_Broadband_Router.home [192.168.1.1]
2 14 ms 11 ms 8 ms L100.BLTMMD-VFTTP-53.verizon-gni.net [96.244.132.1]
3 10 ms 10 ms 11 ms G0-10-4-4.BLTMMD-LCR-21.verizon-gni.net [130.81.216.192]
4 11 ms 12 ms 13 ms so-1-1-0-0.RES-BB-RTR1.verizon-gni.net [130.81.199.2]
5 12 ms 11 ms 93 ms 0.xe-4-3-0.BR1.IAD8.ALTER.NET [152.63.37.37]
6 23 ms 12 ms 13 ms 192.205.36.141
7 96 ms 92 ms 95 ms cr2.wswdc.ip.att.net [12.122.81.250]
8 95 ms 92 ms 96 ms cr1.cgcil.ip.att.net [12.122.18.21]
9 91 ms 88 ms 92 ms cr2.dvmco.ip.att.net [12.122.31.85]
10 90 ms 90 ms 92 ms cr1.slkut.ip.att.net [12.122.30.25]
11 93 ms 93 ms 93 ms cr2.la2ca.ip.att.net [12.122.30.30]
12 89 ms 94 ms 89 ms gar29.la2ca.ip.att.net [12.122.129.241]
13 89 ms 174 ms 89 ms 12-122-254-238.attens.net [12.122.254.238]
14 91 ms 91 ms 124 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.

and pathping is as follows:

Tracing route to 12.129.209.68 over a maximum of 30 hops

0 Vanyel-PC.home [192.168.1.6]
1 Wireless_Broadband_Router.home [192.168.1.1]
2 L100.BLTMMD-VFTTP-53.verizon-gni.net [96.244.132.1]
3 G0-10-4-4.BLTMMD-LCR-21.verizon-gni.net [130.81.216.192]
4 so-1-1-0-0.RES-BB-RTR1.verizon-gni.net [130.81.199.2]
5 0.xe-4-3-0.BR1.IAD8.ALTER.NET [152.63.37.37]
6 192.205.36.141
7 cr2.wswdc.ip.att.net [12.122.81.250]
8 cr1.cgcil.ip.att.net [12.122.18.21]
9 cr2.dvmco.ip.att.net [12.122.31.85]
10 cr1.slkut.ip.att.net [12.122.30.25]
11 cr2.la2ca.ip.att.net [12.122.30.30]
12 gar29.la2ca.ip.att.net [12.122.129.241]
13 12-122-254-238.attens.net [12.122.254.238]
14 mdf001c7613r0002.lax1.attens.net [206.16.68.54]
15 * * *
Computing statistics for 350 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Vanyel-PC.home [192.168.1.6]
0/ 100 = 0% |
1 4ms 0/ 100 = 0% 0/ 100 = 0% Wireless_Broadband_Router.home [192.168.1.1]
0/ 100 = 0% |
2 14ms 0/ 100 = 0% 0/ 100 = 0% L100.BLTMMD-VFTTP-53.verizon-gni.net [96.244.132.1]
0/ 100 = 0% |
3 11ms 0/ 100 = 0% 0/ 100 = 0% G0-10-4-4.BLTMMD-LCR-21.verizon-gni.net [130.81.216.192]
0/ 100 = 0% |
4 16ms 0/ 100 = 0% 0/ 100 = 0% so-1-1-0-0.RES-BB-RTR1.verizon-gni.net [130.81.199.2]
0/ 100 = 0% |
5 22ms 0/ 100 = 0% 0/ 100 = 0% 0.xe-4-3-0.BR1.IAD8.ALTER.NET [152.63.37.37]
0/ 100 = 0% |
6 21ms 0/ 100 = 0% 0/ 100 = 0% 192.205.36.141
100/ 100 =100% |
7 --- 100/ 100 =100% 0/ 100 = 0% cr2.wswdc.ip.att.net [12.122.81.250]
0/ 100 = 0% |
8 --- 100/ 100 =100% 0/ 100 = 0% cr1.cgcil.ip.att.net [12.122.18.21]
0/ 100 = 0% |
9 --- 100/ 100 =100% 0/ 100 = 0% cr2.dvmco.ip.att.net [12.122.31.85]
0/ 100 = 0% |
10 --- 100/ 100 =100% 0/ 100 = 0% cr1.slkut.ip.att.net [12.122.30.25]
0/ 100 = 0% |
11 --- 100/ 100 =100% 0/ 100 = 0% cr2.la2ca.ip.att.net [12.122.30.30]
0/ 100 = 0% |
12 --- 100/ 100 =100% 0/ 100 = 0% gar29.la2ca.ip.att.net [12.122.129.241]
0/ 100 = 0% |
13 --- 100/ 100 =100% 0/ 100 = 0% 12-122-254-238.attens.net [12.122.254.238]
0/ 100 = 0% |
14 --- 100/ 100 =100% 0/ 100 = 0% mdf001c7613r0002.lax1.attens.net [206.16.68.54]

Trace complete.
Tichondrius
New York, NY
I can't log on to server, and if I do I get disconnected shortly after. I can log onto other servers.

Tracing route to 12.129.209.68 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 7 ms 6 ms 7 ms L100.NYCMNY-VFTTP-97.verizon-gni.net [96.232.82.1]
3 10 ms 8 ms 10 ms G0-11-1-0.NYCMNY-LCR-21.verizon-gni.net [130.81.96.184]
4 7 ms 9 ms 9 ms ae0-0.NY325-BB-RTR1.verizon-gni.net [130.81.209.102]
5 * * * Request timed out.
6 51 ms 53 ms 55 ms 192.205.34.49
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 133 ms * * cr2.dvmco.ip.att.net [12.122.31.85]
11 81 ms 79 ms 79 ms cr1.slkut.ip.att.net [12.122.30.25]
12 * * 138 ms cr2.la2ca.ip.att.net [12.122.30.30]
13 * * * Request timed out.
14 * 130 ms 77 ms 12-122-254-238.attens.net [12.122.254.238]
15 129 ms * * mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250]
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.
Diablo 3 Americas
New York, NY

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

C:\Users\David>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 7 ms 6 ms L100.NYCMNY-VFTTP-156.verizon-gni.net [98.113.86
.1]
3 9 ms 11 ms 11 ms G0-1-3-2.NYCMNY-LCR-21.verizon-gni.net [130.81.1
87.226]
4 9 ms 8 ms 9 ms 130.81.199.10
5 * 96 ms * 0.xe-9-0-0.BR2.NYC4.ALTER.NET [152.63.20.189]
6 56 ms 57 ms 57 ms 192.205.34.49
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 79 ms 82 ms 78 ms cr2.dvmco.ip.att.net [12.122.31.85]
11 * * * Request timed out.
12 * * * Request timed out.
13 129 ms * * gar29.la2ca.ip.att.net [12.122.129.241]
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * ^C
C:\Users\David>pathping 12.129.209.68

Tracing route to 12.129.209.68 over a maximum of 30 hops

0 GatewayFX.home [192.168.1.3]
1 Wireless_Broadband_Router.home [192.168.1.1]
2 L100.NYCMNY-VFTTP-156.verizon-gni.net [98.113.86.1]
3 G0-1-3-2.NYCMNY-LCR-21.verizon-gni.net [130.81.187.226]
4 130.81.199.10
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 * * *
Computing statistics for 175 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 GatewayFX.home [192.168.1.3]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% Wireless_Broadband_Router.home [19
2.168.1.1]
0/ 100 = 0% |
2 8ms 0/ 100 = 0% 0/ 100 = 0% L100.NYCMNY-VFTTP-156.verizon-gni.
net [98.113.86.1]
0/ 100 = 0% |
3 11ms 0/ 100 = 0% 0/ 100 = 0% G0-1-3-2.NYCMNY-LCR-21.verizon-gni
.net [130.81.187.226]
0/ 100 = 0% |
4 15ms 0/ 100 = 0% 0/ 100 = 0% 130.81.199.10
0/ 100 = 0% |
5 80ms 20/ 100 = 20% 20/ 100 = 20% 0.xe-9-0-0.BR2.NYC4.ALTER.NET [152
.63.20.189]
0/ 100 = 0% |
6 78ms 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]

Trace complete.

C:\Users\David>
Moon Guard
Murrieta, CA
Got to Launcher, then Disconnected now cannot get past "updating Blizzard Launcher"
Verizon Fios

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.LSANCA-VFTTP-86.verizon-gni.net [96.229.107.1]

3 13 ms 11 ms 19 ms G0-3-4-5.LSANCA-LCR-22.verizon-gni.net [130.81.182.144]

4 11 ms 11 ms 39 ms so-6-0-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.126]

5 11 ms 13 ms 13 ms 0.xe-4-0-0.BR3.LAX15.ALTER.NET [152.63.115.61]

6 16 ms 12 ms 14 ms 204.255.168.134

7 27 ms 24 ms 29 ms cr1.la2ca.ip.att.net [12.123.30.6]

8 28 ms 27 ms 27 ms cr2.phmaz.ip.att.net [12.122.31.190]

9 26 ms 24 ms 24 ms 12.123.206.241

10 25 ms 24 ms 25 ms 12-122-254-50.attens.net [12.122.254.50]

11 25 ms 26 ms 25 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

Pathping

Tracing route to mdf1-bi8k-1-ve-87.phx1.attens.net [63.241.138.161]

over a maximum of 30 hops:

0 tardis.home [192.168.1.3]

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-22.verizon-gni.net [130.81.182.144]

4 so-6-0-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81.29.126]

5 0.xe-4-0-0.BR3.LAX15.ALTER.NET [152.63.115.61]

6 204.255.168.134

7 cr1.la2ca.ip.att.net [12.123.132.129]

8 cr2.phmaz.ip.att.net [12.122.31.190]

9 12.123.206.241

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 300 seconds...
Realm (if a WoW player): Crushridge (Cyclone Battlegroup)
Your Location (city, state): West Chester, Pennsylvania (40 minutes westof Philadelphia)
Brief Description of Issue: I have never had this happen when I am not in an instance. In the instance, heroics or raids, I will suddenly hit huge lag spikes. I am still always connected to Mumble fine and can talk to alert people I am lagging severly. Sometimes this will correct it self quickly and I continue the rest of the raid or dungeon fine. Other times I get disconnected.

Normal latency: 95-110ms When this occurs 3000+ is normal.

This started happening 2/6/2013 for me and so far has never persisted through the entire evening. Usually about 10-20 minutes of annoyance and the rest of the night I am fine.

C:\Users\Josh>tracert 12.129.209.68

Tracing route to 12.129.209.68 over a maximum of 30 hops

1 10 ms 1 ms <1 ms 192.168.1.1
2 8 ms 18 ms 7 ms L100.PHLAPA-VFTTP-64.verizon-gni.net [98.111.132
.1]
3 24 ms 11 ms 10 ms G0-6-1-0.PHLAPA-LCR-21.verizon-gni.net [130.81.1
33.186]
4 30 ms 12 ms 9 ms ae0-0.PHIL-BB-RTR1.verizon-gni.net [130.81.209.1
78]
5 18 ms 14 ms 20 ms 0.xe-7-1-0.BR1.IAD8.ALTER.NET [152.63.3.85]
6 19 ms 18 ms 17 ms 192.205.36.141
7 * * * Request timed out.
8 90 ms 98 ms 121 ms cr1.cgcil.ip.att.net [12.122.18.21]
9 98 ms 91 ms 112 ms cr2.dvmco.ip.att.net [12.122.31.85]
10 91 ms 90 ms 94 ms cr1.slkut.ip.att.net [12.122.30.25]
11 * 227 ms 168 ms cr2.la2ca.ip.att.net [12.122.30.30]
12 140 ms 139 ms 145 ms gar29.la2ca.ip.att.net [12.122.129.241]
13 102 ms 89 ms 108 ms 12.122.251.190
14 101 ms 97 ms 95 ms mdf001c7613r0004-gig-10-1.lax1.attens.net [12.12
9.193.250]
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 ^C


Stopped because I hit blizzard servers.

Thank you for looking into this. It is always reassuring to have a Blue post to address an issue that people are having. Especially when the ISP will generally say, "Not our problem"
Realm : Kel'thuzad, Tich, Arthas, Darkspear (all US)
Your Location (city, state): Woodhaven Queens, New York City
Brief Description of Issue: Battle.net crashed, relogged to get real id back online, cant log back in.

The tracer automatically starts timing out, i ran it about 5 different times. My internet it working for everything else though, no lag on other multiplayer games, youtube, etc.

Tracert:
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 16 ms 9 ms 10 ms lo0-100.NYCMNY-VFTTP-303.verizon-gni.net [96.246.81.1]
3 21 ms 13 ms 19 ms G0-13-4-4.NYCMNY-LCR-22.verizon-gni.net [130.81.187.224]
4 10 ms 23 ms 95 ms ae0-0.NY5030-BB-RTR1.verizon-gni.net [130.81.209.118]
5 12 ms 15 ms 23 ms 0.xe-11-1-0.BR2.NYC4.ALTER.NET [152.63.23.137]
6 109 ms 101 ms 101 ms 192.205.36.57
7 94 ms 104 ms 104 ms cr2.n54ny.ip.att.net [12.122.86.10]
8 87 ms 91 ms 97 ms gar1.nw2nj.ip.att.net [12.122.130.93]
9 55 ms 22 ms 19 ms 12.122.251.6
10 98 ms 100 ms 97 ms mdf001c7613r0003-gig-12-1.nyc3.attens.net [63.240.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 *
02/08/2013 04:26 PMPosted by Celestïal
Come cry with me in Staten Island LOL I'm so bored, especially with this blizzard going on.


honestly about all we can do right now, /sadface
Server: Hyjal
Location: Murrieta, CA
Issue: Horrible lag after 7:30PM server time and becomes progressively worse after 8:00PM server time. Issue started on the 29th of January.

Tracing route to 63.241.183.161 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 10.0.0.1
2 1 ms <1 ms <1 ms 192.168.1.1
3 4 ms 2 ms 5 ms L100.LSANCA-VFTTP-85.verizon-gni.net [72.67.127.1]
4 12 ms 11 ms 11 ms G0-3-3-6.LSANCA-LCR-21.verizon-gni.net [130.81.48.124]
5 11 ms 9 ms 9 ms so-4-1-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81.151.246]
6 8 ms 7 ms 8 ms 0.xe-3-0-0.BR3.LAX15.ALTER.NET [152.63.114.241]
7 9 ms 10 ms 8 ms 204.255.168.134
8 20 ms 19 ms 23 ms cr1.la2ca.ip.att.net [12.123.132.129]
9 22 ms 23 ms 23 ms cr2.phmaz.ip.att.net [12.122.31.190]
10 21 ms 22 ms 19 ms 12.123.206.225
11 116 ms 203 ms 202 ms 12-122-254-50.attens.net [12.122.254.50]
12 * 63.241.183.161 reports: Destination host unreachable.

Trace complete.
Proudmoore - US
Philadelphia PA
World spiking 5k-6k then disconnected.

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 13 ms 9 ms 9 ms L100.PHLAPA-VFTTP-53.verizon-gni.net [96.227.232
.1]
3 8 ms 8 ms 9 ms G0-10-1-3.PHLAPA-LCR-21.verizon-gni.net [130.81.
182.66]
4 9 ms 8 ms 9 ms ae0-0.PHIL-BB-RTR1.verizon-gni.net [130.81.209.1
78]
5 57 ms * 64 ms 0.xe-7-1-0.BR1.IAD8.ALTER.NET [152.63.3.85]
6 23 ms 18 ms 20 ms 192.205.36.141
7 143 ms 141 ms 143 ms cr2.wswdc.ip.att.net [12.122.81.250]
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 124 ms 121 ms * cr2.la2ca.ip.att.net [12.122.30.30]
12 87 ms 96 ms 89 ms gar29.la2ca.ip.att.net [12.122.129.241]
13 140 ms 92 ms 129 ms 12-122-254-234.attens.net [12.122.254.234]
14 86 ms 87 ms 87 ms 206.16.68.46
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.
Most of the people here seem to be from NY! This stupid blizzard is keeping us trapped inside and we can't even nerd it up!
Illidan
Shirley, Massachusetts
Extremely high latency, unresponsive to anything in game, multiple disconnects.

TRACER:

Tracing route to 63.240.161.189 over a maximum of 30 hops

1 1 ms 4 ms <1 ms 192.168.1.1
2 49 ms 38 ms 36 ms 10.9.72.1
3 58 ms 38 ms 38 ms P0-3-1-3.BSTNMA-LCR-21.verizon-gni.net [130.81.197.60]
4 40 ms 40 ms 45 ms ae0-0.BOS-BB-RTR1.verizon-gni.net [130.81.209.86]
5 77 ms 64 ms 60 ms 0.xe-3-3-0.BR2.NYC4.ALTER.NET [152.63.23.133]
6 65 ms 58 ms 52 ms 192.205.36.57
7 96 ms 98 ms 92 ms cr1.n54ny.ip.att.net [12.122.86.6]
8 * 118 ms 115 ms cr2.cgcil.ip.att.net [12.122.1.2]
9 85 ms 110 ms 85 ms gar3.cgcil.ip.att.net [12.122.132.213]
10 84 ms 82 ms 108 ms 12.122.251.50
11 181 ms 223 ms 251 ms 63.240.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.

PATHPING:

Tracing route to 63.240.161.189 over a maximum of 30 hops

0 Brandon-PC.domain.actdsltmp [192.168.1.2]
1 192.168.1.1
2 10.9.72.1
3 P0-3-1-3.BSTNMA-LCR-21.verizon-gni.net [130.81.197.60]
4 ae0-0.BOS-BB-RTR1.verizon-gni.net [130.81.209.86]
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 * 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.210
12 * * *
Computing statistics for 275 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Brandon-PC.domain.actdsltmp [192.168.1.2]
0/ 100 = 0% |
1 3ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1
0/ 100 = 0% |
2 58ms 0/ 100 = 0% 0/ 100 = 0% 10.9.72.1
0/ 100 = 0% |
3 59ms 0/ 100 = 0% 0/ 100 = 0% P0-3-1-3.BSTNMA-LCR-21.verizon-gni.net [130.81.197.60]
0/ 100 = 0% |
4 61ms 0/ 100 = 0% 0/ 100 = 0% ae0-0.BOS-BB-RTR1.verizon-gni.net [130.81.209.86]
0/ 100 = 0% |
5 60ms 0/ 100 = 0% 0/ 100 = 0% 0.xe-3-3-0.BR2.NYC4.ALTER.NET [152.63.23.133]
0/ 100 = 0% |
6 61ms 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% 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.210

Trace complete.
Runetotem - US
Great Neck, NY
Currently can't even log into servers, keep getting disconnected. Otherwise I have latency on home and or world servers as high as 8000ms sometimes. Normal is 80 - 90 when its not spiking. Occurrs from 8pm est to about 10ish pm est

Traceroute:
1 wireless_broadband_router (192.168.1.1) 0.589 ms 0.425 ms 0.337 ms
2 l100.nycmny-vfttp-92.verizon-gni.net (71.190.236.1) 5.689 ms 6.187 ms 8.217 ms
3 g0-11-4-0.nycmny-lcr-22.verizon-gni.net (130.81.104.24) 7.201 ms 11.828 ms 10.126 ms
4 so-3-1-0-0.ny5030-bb-rtr2.verizon-gni.net (130.81.199.12) 6.961 ms 6.184 ms 8.120 ms
5 * * *
6 192.205.36.57 (192.205.36.57) 89.737 ms 90.845 ms
192.205.34.49 (192.205.34.49) 119.996 ms
7 * cr1.n54ny.ip.att.net (12.122.86.6) 128.103 ms *
8 cr2.cgcil.ip.att.net (12.122.1.2) 103.108 ms 77.345 ms 79.814 ms
9 * * cr1.cgcil.ip.att.net (12.122.2.53) 128.886 ms
10 * * *
11 cr1.slkut.ip.att.net (12.122.30.25) 128.936 ms * *
12 * * *
13 gar29.la2ca.ip.att.net (12.122.129.241) 75.076 ms 96.918 ms 124.643 ms
14 * * *
15 * * mdf001c7613r0002.lax1.attens.net (206.16.68.54) 105.637 ms
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
31 * *


Pathping:

1 wireless_broadband_router (192.168.1.1) 0.561 ms 0.363 ms 0.309 ms 0.324 ms 0.323 ms 0.290 ms * 0.493 ms 0.332 ms 0.332 ms 0.361 ms 0.423 ms * 0.573 ms 0.411 ms 0.305 ms 0.297 ms 0.373 ms * 0.636 ms 0.520 ms 0.470 ms 0.451 ms 0.354 ms * 0.709 ms 0.385 ms 0.336 ms 0.310 ms 0.313 ms (13% loss)
2 l100.nycmny-vfttp-92.verizon-gni.net (71.190.236.1) 7.392 ms 7.464 ms 7.273 ms 7.227 ms 7.558 ms 7.286 ms 7.654 ms 8.092 ms 7.061 ms 7.706 ms 7.293 ms 7.176 ms 7.612 ms 10.225 ms 7.511 ms 7.381 ms 7.092 ms 7.554 ms 7.425 ms 7.637 ms 8.127 ms 7.122 ms 7.514 ms 7.513 ms 7.085 ms 7.613 ms 7.374 ms 7.547 ms 8.059 ms 7.026 ms (0% loss)
3 g0-11-4-0.nycmny-lcr-22.verizon-gni.net (130.81.104.24) 9.770 ms 12.235 ms 12.786 ms 9.833 ms 10.235 ms 9.645 ms 10.304 ms 9.729 ms 10.273 ms 9.597 ms 10.347 ms 9.734 ms 10.250 ms 9.676 ms 10.316 ms 9.723 ms 10.392 ms 9.494 ms 10.291 ms 9.723 ms 10.139 ms 9.792 ms 10.285 ms 9.666 ms 10.330 ms 9.732 ms 10.230 ms 9.735 ms 10.201 ms 9.758 ms (0% loss)
4 so-3-1-0-0.ny5030-bb-rtr2.verizon-gni.net (130.81.199.12) 44.964 ms 7.102 ms 7.750 ms 8.046 ms 6.983 ms 7.625 ms 7.379 ms 7.090 ms 7.618 ms 7.379 ms 7.540 ms 8.177 ms 7.026 ms 7.610 ms 7.397 ms 7.151 ms 7.517 ms 7.400 ms 7.589 ms 8.122 ms 7.929 ms 8.878 ms 7.460 ms 7.514 ms 8.116 ms 7.179 ms 7.489 ms 7.405 ms 7.067 ms 7.547 ms (0% loss)
5 * * * * * * * * * * * * * * * * * * 0.xe-1-1-1.br2.nyc4.alter.net (152.63.23.169) 56.030 ms * * * * 55.898 ms * * * * * * (93% loss)
6 192.205.34.49 (192.205.34.49) 90.554 ms 91.775 ms
192.205.36.57 (192.205.36.57) 87.598 ms
192.205.34.49 (192.205.34.49) 89.221 ms 90.173 ms 90.220 ms 89.635 ms 89.583 ms
192.205.36.57 (192.205.36.57) 90.306 ms
192.205.34.49 (192.205.34.49) 92.241 ms
192.205.36.57 (192.205.36.57) 89.413 ms 92.618 ms 89.562 ms 87.744 ms 87.552 ms 84.588 ms 85.010 ms
192.205.34.49 (192.205.34.49) 90.415 ms 89.282 ms
192.205.36.57 (192.205.36.57) 85.429 ms
192.205.34.49 (192.205.34.49) 88.929 ms
192.205.36.57 (192.205.36.57) 147.731 ms
192.205.34.49 (192.205.34.49) 87.096 ms 89.246 ms 90.337 ms
192.205.36.57 (192.205.36.57) 84.577 ms 82.570 ms 107.475 ms 85.012 ms
192.205.34.49 (192.205.34.49) 89.496 ms (0% loss)
7 * * * * * cr1.n54ny.ip.att.net (12.122.86.6) 133.500 ms * * 130.603 ms * * * * * * * * * *
Shu' Halo
Marriottsville, Maryland
Verizon Fios

Random disconnects.

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

C:\Users\*******>tracert 63.241.138.161

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 6 ms 6 ms 6 ms L100.BLTMMD-VFTTP-15.verizon-gni.net [71.179.190
.1]
3 8 ms 7 ms 5 ms G11-0-2-415.BLTMMD-LCR-04.verizon-gni.net [130.8
1.49.6]
4 9 ms 9 ms 10 ms so-6-0-3-0.PHIL-BB-RTR2.verizon-gni.net [130.81.
28.82]
5 12 ms 14 ms 12 ms 0.xe-7-3-0.BR1.IAD8.ALTER.NET [152.63.3.125]
6 13 ms 13 ms 13 ms 192.205.36.141
7 138 ms 95 ms 134 ms cr1.wswdc.ip.att.net [12.122.81.246]
8 108 ms 106 ms 88 ms cr2.sl9mo.ip.att.net [12.122.18.29]
9 101 ms 104 ms 105 ms cr2.kc9mo.ip.att.net [12.122.28.89]
10 128 ms 94 ms 131 ms cr1.dlstx.ip.att.net [12.122.1.209]
11 96 ms 91 ms 96 ms cr1.phmaz.ip.att.net [12.122.28.182]
12 103 ms 104 ms 103 ms 12.123.206.161
13 129 ms * * 12-122-254-50.attens.net [12.122.254.50]
14 96 ms 98 ms 95 ms mdf002c7613r0001-gig-12-1.phx1.attens.net [63.24
1.130.210]
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.

Currently trying to contact Verizon via Phone will update after call.

Join the Conversation