Verizon ISP Issues - Tracking

Technical Support
Prev 1 2 3 29 Next
isn't a verizon problem its AT&T. u can talk to AT&T till you're blue in the face, blizzard. they do not care if their routers are working properly. gotta wait till the issue resolves itself. the end
Hello

I am also having this issue:

Realm > Fenris
Location > NYC, NY

I can seem to authenticate but not log on to the realm and see any of my characters

C:\>tracert www.worldofwarcraft.com

Tracing route to worldofwarcraft.com [12.129.242.22]
over a maximum of 30 hops:

1 302 ms 1 ms 1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 5 ms 4 ms 4 ms L100.NYCMNY-VFTTP-126.verizon-gni.net [96.250.10
3.1]
3 9 ms 6 ms 9 ms G0-1-4-1.NYCMNY-LCR-21.verizon-gni.net [130.81.1
87.94]
4 7 ms 7 ms 6 ms ae0-0.NY325-BB-RTR2.verizon-gni.net [130.81.209.
110]
5 24 ms 24 ms 24 ms 0.xe-3-2-0.BR2.NYC4.ALTER.NET [152.63.20.213]
6 24 ms 24 ms 24 ms 192.205.34.49
7 * * * Request timed out.
8 * * * Request timed out.
9 80 ms 79 ms 79 ms cr1.cgcil.ip.att.net [12.122.2.53]
10 130 ms * * cr2.dvmco.ip.att.net [12.122.31.85]
11 109 ms 106 ms 106 ms cr1.slkut.ip.att.net [12.122.30.25]
12 125 ms * * cr2.la2ca.ip.att.net [12.122.30.30]
13 * * * Request timed out.
14 78 ms * 119 ms 12-122-254-234.attens.net [12.122.254.234]
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 *

then this just hangs. As an outside note, I have been getting periods of extreme latency over the last couple of weeks if this helps at all.
Realm: Darkspear
New York, New York
Cannot connect to WoW/Diablo 3
1 wireless_broadband_router (192.168.1.1) 3.917 ms 0.729 ms 0.590 ms
2 74.101.93.1 (74.101.93.1) 11.392 ms 8.221 ms 8.374 ms
3 g1-5-0-4.nycmny-lcr-21.verizon-gni.net (130.81.187.178) 9.967 ms 12.299 ms 12.378 ms
4 so-11-0-0-0.ny325-bb-rtr1.verizon-gni.net (130.81.151.222) 11.742 ms 11.431 ms 9.306 ms
5 0.xe-9-0-0.br2.nyc4.alter.net (152.63.20.189) 27.937 ms 26.688 ms 25.163 ms
6 192.205.34.49 (192.205.34.49) 132.920 ms 80.799 ms 86.869 ms
7 * * cr1.n54ny.ip.att.net (12.122.86.6) 128.082 ms
8 * cr2.cgcil.ip.att.net (12.122.1.2) 128.225 ms *
9 * * *
10 cr2.dvmco.ip.att.net (12.122.31.85) 130.199 ms 97.153 ms 94.703 ms
11 * * *
12 cr2.la2ca.ip.att.net (12.122.30.30) 132.844 ms * *
13 * gar29.la2ca.ip.att.net (12.122.129.241) 124.383 ms *
14 12-122-254-238.attens.net (12.122.254.238) 178.463 ms * 79.102 ms
15 206.16.68.46 (206.16.68.46) 79.919 ms
mdf001c7613r0003-gig-12-1.lax1.attens.net (12.129.193.254) 103.625 ms
mdf001c7613r0004-gig-10-1.lax1.attens.net (12.129.193.250) 77.191 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 *
I live in Astoria, queens, NYC and have toons in the Garona realm. I can't log in, it keeps hanging me up at the password screen. I was playing tonite and then it froze.. And yes I am a verizon customer. Help.
Verizon FIOS here too, getting good speed with browsing/downloading - just having intermittent problems with WoW.

Realm: The Forgotten Coast
Location: Plainview, NY (Long Island)

Been getting high latency at times over the last week+, most noticeable during LFR raids with lots of players and action going on. I'd be up at 12000ms game (world) latency. Even last night I simply log into Orgrimmar and can't even see the text I'm typing after I hit enter. It was fine after a few more logins.

Right now I try to log in and it says Success but after a short while it says You've been disconnected from the server. 20 minutes of further trying I'm finally in, but I can't do anything such as mount, or interact with NPCs, and can only chat. Here's the tracert to the server IP for my battlegroup:

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 9 ms L100.NYCMNY-VFTTP-112.verizon-gni.net [98.116.47.1]

3 11 ms 8 ms 10 ms G0-1-0-6.NYCMNY-LCR-21.verizon-gni.net [130.81.105.230]

4 7 ms 6 ms 7 ms so-5-0-0-0.NY325-BB-RTR2.verizon-gni.net [130.81.22.16]

5 21 ms 19 ms 19 ms 0.xe-3-2-0.BR2.NYC4.ALTER.NET [152.63.20.213]

6 73 ms 69 ms 67 ms 192.205.34.49

7 116 ms * 116 ms cr2.n54ny.ip.att.net [12.122.86.10]

8 * 131 ms * cr2.wswdc.ip.att.net [12.122.3.38]

9 122 ms 123 ms * cr1.attga.ip.att.net [12.122.1.173]

10 83 ms 79 ms 76 ms cr2.dlstx.ip.att.net [12.122.28.174]

11 * * 129 ms cr1.dlstx.ip.att.net [12.122.1.209]

12 * * * Request timed out.

13 120 ms * * 12.123.206.181

14 102 ms 101 ms 101 ms 12-122-254-50.attens.net [12.122.254.50]

15 102 ms 102 ms 104 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.


And here's the pathping:

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

over a maximum of 30 hops:

0 rh71pc.home [192.168.1.11]

1 Wireless_Broadband_Router.home [192.168.1.1]

2 L100.NYCMNY-VFTTP-112.verizon-gni.net [98.116.47.1]

3 G0-1-0-6.NYCMNY-LCR-21.verizon-gni.net [130.81.105.230]

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.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.181

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 rh71pc.home [192.168.1.11]

0/ 100 = 0% |

1 0ms 0/ 100 = 0% 0/ 100 = 0% Wireless_Broadband_Router.home [192.168.1.1]

0/ 100 = 0% |

2 8ms 0/ 100 = 0% 0/ 100 = 0% L100.NYCMNY-VFTTP-112.verizon-gni.net [98.116.47.1]

0/ 100 = 0% |

3 9ms 0/ 100 = 0% 0/ 100 = 0% G0-1-0-6.NYCMNY-LCR-21.verizon-gni.net [130.81.105.230]

0/ 100 = 0% |

4 15ms 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 76ms 19/ 100 = 19% 19/ 100 = 19% 0.xe-3-2-0.BR2.NYC4.ALTER.NET [152.63.20.213]

0/ 100 = 0% |

6 74ms 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.181

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.
Crushridge-US
Queens, NY

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 12 ms 8 ms 9 ms L100.NYCMNY-VFTTP-72.verizon-gni.net [71.183.243.1]
3 19 ms 17 ms 19 ms G0-14-2-3.NYCMNY-LCR-21.verizon-gni.net [130.81.180.104]
4 9 ms 9 ms 13 ms so-11-0-0-0.NY325-BB-RTR1.verizon-gni.net [130.81.151.222]
5 27 ms 33 ms 23 ms 0.xe-9-0-0.BR2.NYC4.ALTER.NET [152.63.20.189]
6 76 ms 76 ms 68 ms 192.205.36.57
7 125 ms * * cr1.n54ny.ip.att.net [12.122.86.6]
8 119 ms 111 ms 112 ms cr2.cgcil.ip.att.net [12.122.1.2]
9 * * 133 ms cr1.cgcil.ip.att.net [12.122.2.53]
10 * * 128 ms cr2.dvmco.ip.att.net [12.122.31.85]
11 86 ms 77 ms 83 ms cr1.slkut.ip.att.net [12.122.30.25]
12 110 ms 114 ms 116 ms cr2.la2ca.ip.att.net [12.122.30.30]
13 83 ms 85 ms 86 ms gar29.la2ca.ip.att.net [12.122.129.241]
14 102 ms 108 ms * 12.122.251.190
15 107 ms 107 ms 112 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.


Tracing route to 12.129.209.68 over a maximum of 30 hops

0 Ming.home [192.168.1.2]
1 Wireless_Broadband_Router.home [192.168.1.1]
2 L100.NYCMNY-VFTTP-72.verizon-gni.net [71.183.243.1]
3 G0-14-2-3.NYCMNY-LCR-21.verizon-gni.net [130.81.180.104]
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.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-234.attens.net [12.122.254.234]
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 Ming.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 12ms 0/ 100 = 0% 0/ 100 = 0% L100.NYCMNY-VFTTP-72.verizon-gni.net [71.183.243.1]
0/ 100 = 0% |
3 13ms 0/ 100 = 0% 0/ 100 = 0% G0-14-2-3.NYCMNY-LCR-21.verizon-gni.net [130.81.180.104]
0/ 100 = 0% |
4 13ms 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 51ms 13/ 100 = 13% 13/ 100 = 13% 0.xe-9-0-0.BR2.NYC4.ALTER.NET [152.63.20.189]
0/ 100 = 0% |
6 62ms 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-234.attens.net [12.122.254.234]
0/ 100 = 0% |
15 --- 100/ 100 =100% 0/ 100 = 0% mdf001c7613r0002.lax1.attens.net [206.16.68.54]

Trace complete.
Boulderfist-US
Port Washington, NY
World MS spikes, everything freezing for minutes at a time, sometimes unfreezing and doing a fastforward, other times leading to a DC. Sometimes the connection is fine, seems random. Often trouble trying to log back in after a DC.

1 wireless_broadband_router (192.168.8.1) 0.725 ms 0.371 ms 0.268 ms
2 74.101.228.1 (74.101.228.1) 5.350 ms 4.473 ms 4.929 ms
3 g0-11-4-2.nycmny-lcr-21.verizon-gni.net (130.81.131.74) 7.551 ms 9.437 ms 7.462 ms
4 ae0-0.ny325-bb-rtr2.verizon-gni.net (130.81.209.110) 5.001 ms 4.441 ms 4.990 ms
5 0.xe-11-0-0.br2.nyc4.alter.net (152.63.20.221) 10.025 ms 9.410 ms 7.398 ms
6 192.205.34.49 (192.205.34.49) 42.602 ms 39.581 ms 37.478 ms
7 * * *
8 * * *
9 * * *
10 * * *
11 cr1.slkut.ip.att.net (12.122.30.25) 121.482 ms 109.487 ms *
12 * * *
13 * * *
14 * 12.122.251.190 (12.122.251.190) 94.394 ms 94.536 ms
15 * mdf001c7613r0004-gig-10-1.lax1.attens.net (12.129.193.250) 94.851 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 * * *
Note: i don't play WoW anymore, this information is for Diablo III, as follows:

...The Americas
New York
Problem started occuring this afternoon with a very rapid lag spike, that did not go away. disconnected me and since have had problems connecting to even the us.battle.net/d3 website. Logging into the game itself is currently not possible.

Here is the actual information:


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 3 ms 4 ms L100.NYCMNY-VFTTP-164.verizon-gni.net [96.246.52.1]
3 8 ms 7 ms 8 ms G0-11-3-6.NYCMNY-LCR-21.verizon-gni.net [130.81.137.52]
4 40 ms 50 ms 8 ms ae0-0.NY325-BB-RTR2.verizon-gni.net [130.81.209.110]
5 * * 52 ms 0.xe-11-0-0.BR2.NYC4.ALTER.NET [152.63.20.221]
6 51 ms 51 ms 52 ms 192.205.34.49
7 128 ms * * cr1.n54ny.ip.att.net [12.122.86.6]
8 * 121 ms * cr2.cgcil.ip.att.net [12.122.1.2]
9 108 ms 109 ms 106 ms cr1.cgcil.ip.att.net [12.122.2.53]
10 76 ms 75 ms 76 ms cr2.dvmco.ip.att.net [12.122.31.85]
11 78 ms 75 ms 76 ms cr1.slkut.ip.att.net [12.122.30.25]
12 * * 124 ms cr2.la2ca.ip.att.net [12.122.30.30]
13 100 ms 101 ms 100 ms gar29.la2ca.ip.att.net [12.122.129.241]
14 74 ms 96 ms 98 ms 12.122.251.190
15



Tracing route to 12.129.209.68 over a maximum of 30 hops

0 Alex-PC.home [192.168.1.14]
1 Wireless_Broadband_Router.home [192.168.1.1]
2 L100.NYCMNY-VFTTP-164.verizon-gni.net [96.246.52.1]
3 G0-11-3-6.NYCMNY-LCR-21.verizon-gni.net [130.81.137.52]
4 ae0-0.NY325-BB-RTR2.verizon-gni.net [130.81.209.110]
5 * * *
Computing statistics for 100 seconds...
Sen'jin-US
Waipahu, Hawaii

I've been having latency issues for the last couple days on WoW and Diablo3. I am linking my pathping and trace route that was requested but my ISP is Oceanic Time Warner and I have already talked to them and there is nothing wrong with my connection with them.

Pathping

Tracing route to 12.129.209.68 over a maximum of 30 hops

0 Joshua79-PC [192.168.0.2]
1 cpe-98-150-172-1.hawaii.res.rr.com [98.150.172.1]
2 24.25.229.201
3 agg11.milnhixd-ccr01.hawaii.rr.com [72.129.45.64]
4 agg31.lsancarc-ccr01.socal.rr.com [72.129.45.0]
5 ae-5-0.cr0.lax00.tbone.rr.com [66.109.6.102]
6 107.14.19.138
7 ix-9-2-0-0.tcore2.LVW-LosAngeles.as6453.net [64.86.252.173]
8 if-2-2.tcore1.LVW-LosAngeles.as6453.net [66.110.59.1]
9 66.110.59.42
10 cr1.la2ca.ip.att.net [12.122.84.202]
11 gar29.la2ca.ip.att.net [12.122.129.241]
12 12.122.251.190
13 mdf001c7613r0002.lax1.attens.net [206.16.68.54]
14 * * *
Computing statistics for 325 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Joshua79-PC [192.168.0.2]
0/ 100 = 0% |
1 78ms 2/ 100 = 2% 2/ 100 = 2% cpe-98-150-172-1.hawaii.res.rr.com [98.150.172.1]
0/ 100 = 0% |
2 107ms 0/ 100 = 0% 0/ 100 = 0% 24.25.229.201
1/ 100 = 1% |
3 97ms 1/ 100 = 1% 0/ 100 = 0% agg11.milnhixd-ccr01.hawaii.rr.com [72.129.45.64]
1/ 100 = 1% |
4 --- 100/ 100 =100% 98/ 100 = 98% agg31.lsancarc-ccr01.socal.rr.com [72.129.45.0]
0/ 100 = 0% |
5 134ms 2/ 100 = 2% 0/ 100 = 0% ae-5-0.cr0.lax00.tbone.rr.com [66.109.6.102]
0/ 100 = 0% |
6 124ms 2/ 100 = 2% 0/ 100 = 0% 107.14.19.138
0/ 100 = 0% |
7 117ms 2/ 100 = 2% 0/ 100 = 0% ix-9-2-0-0.tcore2.LVW-LosAngeles.as6453.net [64.86.252.173]
1/ 100 = 1% |
8 109ms 4/ 100 = 4% 1/ 100 = 1% if-2-2.tcore1.LVW-LosAngeles.as6453.net [66.110.59.1]
0/ 100 = 0% |
9 102ms 3/ 100 = 3% 0/ 100 = 0% 66.110.59.42
97/ 100 = 97% |
10 --- 100/ 100 =100% 0/ 100 = 0% cr1.la2ca.ip.att.net [12.122.84.202]
0/ 100 = 0% |
11 --- 100/ 100 =100% 0/ 100 = 0% gar29.la2ca.ip.att.net [12.122.129.241]
0/ 100 = 0% |
12 --- 100/ 100 =100% 0/ 100 = 0% 12.122.251.190
0/ 100 = 0% |
13 --- 100/ 100 =100% 0/ 100 = 0% mdf001c7613r0002.lax1.attens.net [206.16.68.54]

Trace complete.


Tracert

Tracing route to 12.129.209.68 over a maximum of 30 hops

1 51 ms 25 ms 16 ms cpe-98-150-172-1.hawaii.res.rr.com [98.150.172.1]
2 12 ms 11 ms 11 ms 24.25.229.201
3 61 ms 58 ms 59 ms agg11.milnhixd-ccr01.hawaii.rr.com [72.129.45.64]
4 63 ms 64 ms 63 ms agg31.lsancarc-ccr01.socal.rr.com [72.129.45.0]
5 59 ms 63 ms 64 ms ae-5-0.cr0.lax00.tbone.rr.com [66.109.6.102]
6 57 ms 58 ms 57 ms 107.14.19.138
7 59 ms 60 ms 64 ms ix-9-2-0-0.tcore2.LVW-LosAngeles.as6453.net [64.86.252.173]
8 71 ms 59 ms 73 ms if-2-2.tcore1.LVW-LosAngeles.as6453.net [66.110.59.1]
9 57 ms 57 ms 63 ms 66.110.59.42
10 60 ms 60 ms 60 ms cr1.la2ca.ip.att.net [12.122.84.202]
11 78 ms 57 ms 59 ms gar20.la2ca.ip.att.net [12.122.128.181]
12 58 ms 58 ms 58 ms 12-122-254-238.attens.net [12.122.254.238]
13 60 ms 58 ms 59 ms mdf001c7613r0002.lax1.attens.net [206.16.68.54]
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.


I hope this helps.
Draka Server
New York City

Here is the actual information: problem started roughly around thursday of last week, huge latency issues that appeared to at first have been partially resolved. However, around 9:00 and 10:05 PM EST, almost like clock work i will start to lag really heavily and maybe get disconnected(9:00 PM EST), or i will just be disconnected from the server itself (10:05 PM EST).

I rarely have an issue before this time frame, today is the first time I had an issue any earlier then that time (got disconnected around 5:00 - 5:30 EST today and have been having issues connecting ot battlenet since then.

Tracert

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.NYCMNY-VFTTP-251.verizon-gni.net [96.246.233.1]
3 11 ms 13 ms 7 ms G0-5-4-0.NYCMNY-LCR-21.verizon-gni.net [130.81.54.88]
4 9 ms 9 ms 12 ms so-5-0-0-0.NY325-BB-RTR2.verizon-gni.net [130.81.22.16]
5 37 ms 36 ms 37 ms 0.xe-3-2-0.BR2.NYC4.ALTER.NET [152.63.20.213]
6 58 ms 56 ms 59 ms 192.205.34.49
7 97 ms 97 ms 96 ms cr1.n54ny.ip.att.net [12.122.86.6]
8 81 ms 85 ms 79 ms cr2.cgcil.ip.att.net [12.122.1.2]
9 112 ms 111 ms 114 ms cr1.cgcil.ip.att.net [12.122.2.53]
10 * * * Request timed out.
11 78 ms 78 ms 82 ms cr1.slkut.ip.att.net [12.122.30.25]
12 135 ms * * cr2.la2ca.ip.att.net [12.122.30.30]
13 * * * Request timed out.
14 106 ms 106 ms 144 ms 12-122-254-238.attens.net [12.122.254.238]
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.

Pathping

Tracing route to 12.129.209.68 over a maximum of 30 hops

0 Stylos-Laptop.home [192.168.1.4]
1 Wireless_Broadband_Router.home [192.168.1.1]
2 L100.NYCMNY-VFTTP-251.verizon-gni.net [96.246.233.1]
3 G0-5-4-0.NYCMNY-LCR-21.verizon-gni.net [130.81.54.88]
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.34.49
7 cr1.n54ny.ip.att.net [12.122.86.6]
8 cr2.cgcil.ip.att.net [12.122.1.2]
9 cr1.cgcil.ip.att.net [12.122.2.53]
10 * * *
Computing statistics for 225 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Stylos-Laptop.home [192.168.1.4]
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.NYCMNY-VFTTP-251.verizon-gni.net [96.246.233.1]
0/ 100 = 0% |
3 17ms 0/ 100 = 0% 0/ 100 = 0% G0-5-4-0.NYCMNY-LCR-21.verizon-gni.net [130.81.54.88]
0/ 100 = 0% |
4 20ms 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 57ms 7/ 100 = 7% 7/ 100 = 7% 0.xe-3-2-0.BR2.NYC4.ALTER.NET [152.63.20.213]
0/ 100 = 0% |
6 43ms 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% cr1.cgcil.ip.att.net [12.122.2.53]
Realm: Azshara
Location: Brooklyn, NY
Verizon FIOS.

high latency, unable to play and login.

traceroute to 63.240.161.189 (63.240.161.189), 64 hops max, 52 byte packets
1 wireless_broadband_router (192.168.1.1) 4.030 ms 2.043 ms 0.577 ms
2 l100.nycmny-vfttp-176.verizon-gni.net (98.113.53.1) 2.654 ms 2.162 ms 4.042 ms
3 g0-13-3-2.nycmny-lcr-22.verizon-gni.net (130.81.183.239) 8.328 ms 7.481 ms 7.952 ms
4 ae0-0.ny5030-bb-rtr1.verizon-gni.net (130.81.209.118) 128.891 ms 130.984 ms 24.169 ms
5 0.xe-11-1-0.br2.nyc4.alter.net (152.63.23.137) 27.357 ms 33.065 ms 18.628 ms
6 192.205.36.57 (192.205.36.57) 20.863 ms 20.728 ms 20.144 ms
7 cr1.n54ny.ip.att.net (12.122.86.6) 33.785 ms 33.357 ms 35.961 ms
8 cr2.cgcil.ip.att.net (12.122.1.2) 37.442 ms 37.008 ms 35.171 ms
9 gar3.cgcil.ip.att.net (12.122.132.213) 31.589 ms 31.533 ms 39.386 ms
10 12.122.251.50 (12.122.251.50) 30.864 ms
12.122.251.22 (12.122.251.22) 33.753 ms 37.434 ms
11 63.240.130.210 (63.240.130.210) 33.721 ms * 36.128 ms
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * *^C
Note: i don't play WoW anymore, this information is for Diablo III, as follows:

Draka Server
New York City

My

Here is the actual information: problem started roughly around thursday of last week, huge latency issues that appeared to at first have been partially resolved. However, around 9:00 and 10:05 PM EST, almost like clock work i will start to lag really heavily and maybe get disconnected(9:00 PM EST), or i will just be disconnected from the server itself (10:05 PM EST).

I rarely have an issue before this time frame, today is the first time I had an issue any earlier then that time (got disconnected around 5:00 - 5:30 EST today and have been having issues connecting ot battlenet since then.

Tracert

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.NYCMNY-VFTTP-251.verizon-gni.net [96.246.233.1]
3 11 ms 13 ms 7 ms G0-5-4-0.NYCMNY-LCR-21.verizon-gni.net [130.81.54.88]
4 9 ms 9 ms 12 ms so-5-0-0-0.NY325-BB-RTR2.verizon-gni.net [130.81.22.16]
5 37 ms 36 ms 37 ms 0.xe-3-2-0.BR2.NYC4.ALTER.NET [152.63.20.213]
6 58 ms 56 ms 59 ms 192.205.34.49
7 97 ms 97 ms 96 ms cr1.n54ny.ip.att.net [12.122.86.6]
8 81 ms 85 ms 79 ms cr2.cgcil.ip.att.net [12.122.1.2]
9 112 ms 111 ms 114 ms cr1.cgcil.ip.att.net [12.122.2.53]
10 * * * Request timed out.
11 78 ms 78 ms 82 ms cr1.slkut.ip.att.net [12.122.30.25]
12 135 ms * * cr2.la2ca.ip.att.net [12.122.30.30]
13 * * * Request timed out.
14 106 ms 106 ms 144 ms 12-122-254-238.attens.net [12.122.254.238]
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.

Pathping

Tracing route to 12.129.209.68 over a maximum of 30 hops

0 Stylos-Laptop.home [192.168.1.4]
1 Wireless_Broadband_Router.home [192.168.1.1]
2 L100.NYCMNY-VFTTP-251.verizon-gni.net [96.246.233.1]
3 G0-5-4-0.NYCMNY-LCR-21.verizon-gni.net [130.81.54.88]
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.34.49
7 cr1.n54ny.ip.att.net [12.122.86.6]
8 cr2.cgcil.ip.att.net [12.122.1.2]
9 cr1.cgcil.ip.att.net [12.122.2.53]
10 * * *
Computing statistics for 225 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Stylos-Laptop.home [192.168.1.4]
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.NYCMNY-VFTTP-251.verizon-gni.net [96.246.233.1]
0/ 100 = 0% |
3 17ms 0/ 100 = 0% 0/ 100 = 0% G0-5-4-0.NYCMNY-LCR-21.verizon-gni.net [130.81.54.88]
0/ 100 = 0% |
4 20ms 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 57ms 7/ 100 = 7% 7/ 100 = 7% 0.xe-3-2-0.BR2.NYC4.ALTER.NET [152.63.20.213]
0/ 100 = 0% |
6 43ms 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% cr1.cgcil.ip.att.net [12.122.2.53]


yes!! same here
well verizon fios is one of the only network providers besides optimum online for people like us that live in or very close to NYC
3 9 ms 7 ms 8 ms G0-14-4-3.NYCMNY-LCR-22.verizon-gni.net [130.81.212.216]
4 5 ms 10 ms 5 ms ae0-0.NY5030-BB-RTR2.verizon-gni.net [130.81.209.126]
5 * 76 ms 75 ms 0.xe-9-1-0.BR2.NYC4.ALTER.NET [152.63.23.141]
6 38 ms 39 ms 39 ms 192.205.34.49
7 30 ms 31 ms 30 ms cr1.n54ny.ip.att.net [12.122.86.6]
8 69 ms 32 ms 33 ms gar1.nw2nj.ip.att.net [12.122.130.93]
9 196 ms 43 ms 41 ms 12.122.251.6
10 39 ms 38 ms 39 ms mdf001c7613r0004-gig-10-1.nyc3.attens.net [63.240.65.18]

BRONX, NY 75mb/s download 35mb/s upload

Experiencing high latency over 3k+ at several points of the day, especially in arena queue, causing a disconnect and loss of points

Can't play competitively due to this as well as our rank 1 5's team losing 40 points because of the high latency disconnects very very similar to a DDOS.

Also when this spike accurs, It will disconnect you from your REAL ID battle.net.

Okay from what I understand this has been going on for a couple months now, but not as bad as it is now! As I browsed through the forums I read that people who even have the highest tier of VERIZON FIOS, are also having problems with XBOX and many other video games and consoles.

This is a matter of correctly maintaining the service they provide, but they have not over the last few months because 10%> is there gaming customer database.

I tried to speak to the customer support but only got tier 1 which had no clue what to do, I asked for a supervisor of the technical support to explain the issues and he just hung up on me. I had no problems with cablevision, just there slow speed I was not able to play the game at the same time with my girlfriend without us lagging eachother out! especially if she wanted to watch netflix as I played.

Between the new patch updates blizzard is releasing, this is jeopardizing my ranking in arena. I cannot queue up because of this issue and this is really frustrating.

I recieved an email that stated that Verizon FIOS believs that the recent storm, Nemo, is the reason why there servers are having power outages and causing there services to not perform and disconnect, this is bullcrap.

So after a couple hours of TRACERT, I came up that the
0.xe-9-1-0.BR2.NYC4.ALTER.NET [152.63.23.141]
is the problem. ALTER.NET was baught by VERIZON FIOS. FIOS has not maintained the issue with this routing server in the last couple of months and won't get to it.

It is up to ACTIVISION BLIZZARD to step up, There games like CALL OF DUTY and WORLD OF WARCRAFT can loss many subscribers because of VERIZON FIOS' issues with there ROUTING SERVERS.

So Blizzard please do your best to get this fixed, this company gets paid millions of dollars and your subscribers cannot play the game they pay for.

Thanks Meldanik
Korgath
Brooklyn, NY

Currently, I can't login. Getting Error #2.
For the last week, there has been intermittent lag. Sometimes so slow that the game was not playable.

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 6 ms 8 ms 6 ms G0-14-0-6.NYCMNY-LCR-22.verizon-gni.net [130.81.189.232]
4 5 ms 6 ms 5 ms so-3-1-0-0.NY5030-BB-RTR2.verizon-gni.net [130.81.199.12]
5 6 ms 5 ms 6 ms 0.xe-9-1-0.BR2.NYC4.ALTER.NET [152.63.23.141]
6 72 ms 72 ms 72 ms 192.205.36.57
7 * 125 ms 141 ms cr1.n54ny.ip.att.net [12.122.86.6]
8 76 ms 93 ms 77 ms cr2.cgcil.ip.att.net [12.122.1.2]
9 * * 126 ms cr1.cgcil.ip.att.net [12.122.2.53]
10 88 ms 87 ms 90 ms cr2.dvmco.ip.att.net [12.122.31.85]
11 * * * Request timed out.
12 93 ms 91 ms 91 ms cr2.la2ca.ip.att.net [12.122.30.30]
13 * * * Request timed out.
14 112 ms 89 ms 74 ms 12-122-254-238.attens.net [12.122.254.238]
15 185 ms 91 ms 90 ms mdf001c7613r0002.lax1.attens.net [206.16.68.54]
Realm : Vashj

City, State : Staten Island, New York

Issue: For the past week ( and I believe it's only been a week, thus far ), I have been getting "you have been disconnected from battle.net" messages on Chat. Eventually I'd regain connectivity, but it's gone from brief, to all the time now. Chat will be the only thing accessible to still use -- my character will continue to walk, but no actions can be made (just the visual -- can't mount, can't roll, etc).

The situation also has heightened in the past few days, where I cannot stay connected anymore (loading screens will freeze once the blue bar is full, log in screen will take forever to connect > authenticator put in > and then will disconnect me (or not connect me at all), and now in the brief times I do regain control of my character, have entered in to instances (or even just in the Overworld) and have gotten "transfer aborted: instance not found")

Prior to this post, 20 minutes ago (that's how long I've been trying to re-log back in to WoW), I had just joined a dungeon group, and stopped at the loading screen again, and have been unsuccessful in all my attempts to log back in. If I want to, I have to completely restart my computer, and even then, it will continue to disconnect me.

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-140.verizon-gni.net [98.113.69.1]
3 10 ms 12 ms 9 ms G0-14-3-6.NYCMNY-LCR-21.verizon-gni.net [130.81.188.166]
4 85 ms 9 ms 9 ms ae0-0.NY325-BB-RTR1.verizon-gni.net [130.81.209.102]
5 30 ms 29 ms 29 ms 0.xe-9-0-0.BR2.NYC4.ALTER.NET [152.63.20.189]
6 48 ms 47 ms 44 ms 192.205.34.49
7 78 ms 79 ms 79 ms cr2.n54ny.ip.att.net [12.122.86.10]
8 80 ms 82 ms 82 ms cr2.wswdc.ip.att.net [12.122.3.38]
9 * * * Request timed out.
10 101 ms 105 ms 104 ms cr2.dlstx.ip.att.net [12.122.28.174]
11 150 ms 114 ms 97 ms cr1.dlstx.ip.att.net [12.122.1.209]
12 114 ms 112 ms 112 ms cr1.phmaz.ip.att.net [12.122.28.182]
13 * * * Request timed out.
14 89 ms 89 ms 89 ms 12-122-254-50.attens.net [12.122.254.50]
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.

Thank you.
is this real? a technology problem resolving itself? downrated.
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.
Tracing route to 12.129.209.68 over a maximum of 30 hops

1 1 ms 1 ms 1 ms 172.27.35.1
2 2 ms 2 ms 2 ms 192.168.1.1
3 7 ms 7 ms 7 ms L100.NYCMNY-VFTTP-59.verizon-gni.net [96.224.241.1]
4 11 ms 11 ms 11 ms G0-1-3-3.NYCMNY-LCR-22.verizon-gni.net [130.81.190.46]
5 9 ms 76 ms 99 ms so-3-1-0-0.NY5030-BB-RTR1.verizon-gni.net [130.81.151.234]
6 * * * Request timed out.
7 89 ms 90 ms 92 ms 192.205.34.49
8 * * * Request timed out.
9 * * * Request timed out.
10 * 111 ms 108 ms cr1.cgcil.ip.att.net [12.122.2.53]
11 * * * Request timed out.
12 * * 132 ms cr1.slkut.ip.att.net [12.122.30.25]
13 * * * Request timed out.
14 * * * Request timed out.
15 75 ms * 75 ms 12.122.251.190
16 102 ms 102 ms 107 ms mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250]
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.

Join the Conversation

Return to Forum