Verizon ISP Issues - Tracking

Technical Support
Prev 1 9 10 11 29 Next
Germantown MD here. Still laggy and terrible. I can log in and get into my character list just like normal. In fact the game world loads quite quickly for me and even has a 50ms ping when I first load in. However after about 2 minutes it was already up past 1000ms. I called Verizon and their response was "World of what? Let me search my database..."

Most recent tracert:

Tracing route to 63.240.161.189 over a maximum of 30 hops

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

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

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

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

5 10 ms 9 ms 10 ms 0.xe-5-3-0.BR1.IAD8.ALTER.NET [152.63.37.49]

6 * 16 ms 14 ms 192.205.36.141

7 * * * Request timed out.

8 36 ms 34 ms 35 ms cr1.cgcil.ip.att.net [12.122.18.21]

9 33 ms 32 ms 32 ms gar2.clboh.ip.att.net [12.122.133.197]

10 64 ms 194 ms 62 ms 12.122.251.50

11 34 ms 35 ms 34 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
Well, could not even get the forums from my home network now lol

Posting with a phone. Oh well.
Bayside, New York
Earthen Ring - US

Trace Route!! -

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 6 ms 6 ms 7 ms L100.NYCMNY-VFTTP-48.verizon-gni.net [71.167.106.1]
3 13 ms 8 ms 10 ms G0-1-1-3.NYCMNY-LCR-21.verizon-gni.net [130.81.188.74]
4 11 ms 9 ms 12 ms 130.81.151.228
5 26 ms 35 ms 16 ms 0.xe-3-2-0.BR2.NYC4.ALTER.NET [152.63.20.213]
6 13 ms 9 ms 8 ms 192.205.36.57
7 46 ms * 42 ms cr1.n54ny.ip.att.net [12.122.86.6]
8 42 ms 47 ms 41 ms cr2.cgcil.ip.att.net [12.122.1.2]
9 * 40 ms * gar3.cgcil.ip.att.net [12.122.132.213]
10 41 ms 53 ms 39 ms 12.122.251.50
11 36 ms 43 ms 34 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 Chris-PC.home [192.168.1.2]
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 * 130.81.151.228
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 gar3.cgcil.ip.att.net [12.122.132.213]
10 12.122.251.22
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 Chris-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 9ms 0/ 100 = 0% 0/ 100 = 0% L100.NYCMNY-VFTTP-48.verizon-gni.net [71.167.106.1]
0/ 100 = 0% |
3 11ms 0/ 100 = 0% 0/ 100 = 0% G0-1-1-3.NYCMNY-LCR-21.verizon-gni.net [130.81.188.74]
0/ 100 = 0% |
4 17ms 0/ 100 = 0% 0/ 100 = 0% 130.81.151.228
1/ 100 = 1% |
5 18ms 3/ 100 = 3% 2/ 100 = 2% 0.xe-3-2-0.BR2.NYC4.ALTER.NET [152.63.20.213]
0/ 100 = 0% |
6 13ms 1/ 100 = 1% 0/ 100 = 0% 192.205.36.57
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.22
0/ 100 = 0% |
11 --- 100/ 100 =100% 0/ 100 = 0% 63.240.130.210

Trace complete.
On Linux rig right now so my traceroute might look funny.

traceroute to us.battle.net (12.129.242.40), 30 hops max, 60 byte packets
1 Wireless_Broadband_Router.home (192.168.1.1) 2.330 ms 2.330 ms *
2 L100.WASHDC-VFTTP-92.verizon-gni.net (71.191.59.1) 4.349 ms 4.359 ms 4.347 ms
3 G0-12-3-4.WASHDC-LCR-21.verizon-gni.net (130.81.184.72) 9.311 ms 9.302 ms 9.291 ms
4 ae3-0.RES-BB-RTR1.verizon-gni.net (130.81.199.130) 6.558 ms 6.568 ms 9.183 ms
5 0.xe-5-3-0.BR1.IAD8.ALTER.NET (152.63.37.49) 9.191 ms 9.180 ms 9.187 ms
6 192.205.36.141 (192.205.36.141) 18.828 ms 17.883 ms 17.883 ms
7 cr2.wswdc.ip.att.net (12.122.81.250) 117.850 ms 117.844 ms 117.777 ms
8 cr1.cgcil.ip.att.net (12.122.18.21) 85.463 ms 85.486 ms 85.482 ms
9 cr2.dvmco.ip.att.net (12.122.31.85) 85.508 ms 85.494 ms 85.488 ms
10 cr1.slkut.ip.att.net (12.122.30.25) 85.419 ms 85.414 ms 85.407 ms
11 cr2.la2ca.ip.att.net (12.122.30.30) 85.330 ms 87.344 ms 87.350 ms
12 gar29.la2ca.ip.att.net (12.122.129.241) 149.495 ms 149.498 ms 149.490 ms
13 12-122-254-234.attens.net (12.122.254.234) 116.770 ms 12.122.251.190 (12.122.251.190) 79.552 ms 79.568 ms
14 206.16.68.46 (206.16.68.46) 79.560 ms 79.559 ms mdf001c7613r0003-gig-12-1.lax1.attens.net (12.129.193.254) 79.536 ms
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
Fresh Meadows, NY
Shadowsong US (Reckoning)

Been the same thing for two days, and by the same thing I mean very varied but with the same end (not connecting or crappy connection when I finally make it online) - stuck at "Connecting", stuck at "Success!" stuck after trying to access my character, sometimes getting "Character not found" when I try to log in, or "You have been disconnected from the server." or "Error 2", etc...

When I *do* get online, I'm okay for a little bit, but my latency gradually increases and then spikes big time. Highest I got was 10,000 ms. Not fun.

Pathping:

1 192.168.1.1 (192.168.1.1) 3.477 ms 1.164 ms 1.161 ms 0.997 ms 1.079 ms 1.173 ms * 1.632 ms 4.172 ms 1.034 ms 1.054 ms 1.127 ms * 1.082 ms 1.050 ms 1.037 ms 1.110 ms 1.024 ms * 1.546 ms 1.982 ms 1.144 ms 1.116 ms 2.944 ms * 2.407 ms 1.051 ms 1.160 ms 1.195 ms 1.241 ms (13% loss)
2 l100.nycmny-vfttp-48.verizon-gni.net (71.167.106.1) 9.730 ms 15.557 ms 9.750 ms 11.840 ms 8.614 ms 9.688 ms 10.233 ms 8.836 ms 9.989 ms 9.817 ms 9.254 ms 9.949 ms 9.822 ms 16.815 ms 14.790 ms 8.414 ms 9.212 ms 10.874 ms 9.041 ms 10.035 ms 9.973 ms 11.734 ms 18.295 ms 13.001 ms 15.645 ms 10.176 ms 18.964 ms 9.971 ms 10.167 ms 9.751 ms (0% loss)
3 g0-1-1-4.nycmny-lcr-21.verizon-gni.net (130.81.146.230) 16.622 ms 15.103 ms 12.913 ms 19.863 ms 21.606 ms 17.324 ms 21.016 ms 15.488 ms 12.648 ms 20.874 ms 20.032 ms 19.858 ms 18.957 ms 20.165 ms 15.310 ms 11.894 ms 19.826 ms 20.061 ms 19.990 ms 23.596 ms 17.242 ms 16.475 ms 19.132 ms 21.593 ms 19.138 ms 20.077 ms 18.988 ms 19.961 ms 19.879 ms 21.988 ms (0% loss)
4 ae0-0.ny325-bb-rtr2.verizon-gni.net (130.81.209.110) 39.968 ms 55.274 ms 43.707 ms * 10.694 ms 10.128 ms 12.639 ms 104.447 ms 99.195 ms 57.310 ms 14.437 ms * * * * 11.196 ms 15.497 ms 14.501 ms 11.535 ms 18.316 ms 19.080 ms 9.981 ms 10.912 ms 18.258 ms 11.490 ms 18.378 ms 11.720 ms 18.167 ms 10.148 ms * (20% loss)
5 0.xe-11-0-0.br2.nyc4.alter.net (152.63.20.221) 19.839 ms 20.947 ms 20.405 ms 17.479 ms 9.912 ms 10.075 ms 19.051 ms 20.314 ms 19.529 ms 19.157 ms 10.012 ms 19.866 ms 9.039 ms 10.814 ms 18.603 ms 10.538 ms 9.846 ms 10.051 ms 19.053 ms 9.991 ms 10.148 ms 18.950 ms 9.752 ms 11.045 ms 19.960 ms 18.258 ms 9.814 ms 9.953 ms 9.985 ms 9.961 ms (0% loss)
6 192.205.34.49 (192.205.34.49) 9.996 ms 17.115 ms 10.983 ms 18.178 ms 10.008 ms 18.896 ms 10.992 ms 8.960 ms 9.915 ms 10.192 ms 19.831 ms 19.973 ms 9.034 ms 9.946 ms 10.207 ms 19.759 ms 11.171 ms 17.905 ms 9.535 ms 10.352 ms 20.923 ms 18.170 ms 9.840 ms 11.682 ms 18.267 ms 9.390 ms 9.655 ms 9.960 ms 9.064 ms 10.960 ms (0% loss)
7 cr1.n54ny.ip.att.net (12.122.86.6) 95.458 ms 99.878 ms 95.386 ms 96.263 ms 91.880 ms 99.231 ms 96.118 ms 98.240 ms 99.937 ms * 99.148 ms 98.959 ms * 104.826 ms 122.322 ms * 101.762 ms 96.377 ms * 101.904 ms 101.789 ms 93.548 ms 96.381 ms 98.305 ms 98.456 ms * 100.462 ms 103.602 ms 92.898 ms 97.013 ms (16% loss)
8 cr2.cgcil.ip.att.net (12.122.1.2) 101.827 ms * 103.530 ms 95.213 ms 100.216 ms 97.319 ms 99.759 ms 104.348 ms * 91.772 ms 100.838 ms 96.472 ms 98.978 ms 97.172 ms 99.050 ms 99.091 ms 96.435 ms 100.818 ms 99.091 ms 98.136 ms 98.182 ms 97.302 ms 116.271 ms 99.016 ms 100.929 ms 96.465 ms 99.857 ms 95.412 ms 92.665 ms 96.477 ms (6% loss)
9 cr1.cgcil.ip.att.net (12.122.2.53) 116.278 ms 123.615 ms 121.616 ms 108.176 ms 142.709 ms 112.658 ms 109.082 ms 113.646 ms 117.177 ms * 116.888 ms * 121.269 ms * * 117.575 ms 120.178 ms 114.653 ms 120.547 ms 150.912 ms 117.829 ms 115.955 ms 119.704 ms 114.556 ms 120.875 ms 119.929 ms 124.545 ms * 129.868 ms 152.504 ms (16% loss)
10 cr2.dvmco.ip.att.net (12.122.31.85) 119.993 ms 126.280 ms 124.553 ms 118.259 ms * 117.239 ms 123.716 ms 118.094 ms * 114.517 ms 119.198 ms 116.121 ms * 117.280 ms * 121.970 ms 116.409 ms 128.719 ms 121.799 ms 113.711 ms 122.684 ms * 113.003 ms 119.293 ms 118.872 ms 115.641 ms 119.948 ms 115.273 ms 107.284 ms 113.579 ms (16% loss)
11 cr1.slkut.ip.att.net (12.122.30.25) 119.121 ms 120.599 ms 123.676 ms 130.912 ms 120.934 ms * 132.486 ms 122.761 ms * 119.037 ms * 125.678 ms 123.137 ms 114.921 ms 122.474 ms 115.132 ms 118.239 ms 119.981 ms 114.553 ms * 125.370 ms 134.621 ms * * 118.024 ms * 121.012 ms 116.130 ms 128.360 ms 127.845 ms (23% loss)
12 cr2.la2ca.ip.att.net (12.122.30.30) 96.639 ms 98.992 ms 99.977 ms 100.707 ms 96.390 ms 96.371 ms * 95.068 ms 93.889 ms 100.038 ms 129.028 ms 104.152 ms 108.101 ms 100.735 ms 96.567 ms 110.052 ms 133.483 ms 93.384 ms 96.362 ms 100.014 ms 101.914 ms 95.479 ms 101.689 ms 93.504 ms 100.087 ms * 127.900 ms 97.235 ms 94.494 ms 94.446 ms (6% loss)
13 gar29.la2ca.ip.att.net (12.122.129.241) 108.267 ms 100.739 ms 100.872 ms 98.289 ms 96.302 ms 98.030 ms 98.235 ms 99.208 ms 99.847 ms * * 99.450 ms 106.386 ms 101.001 ms 99.737 ms * 175.492 ms 148.936 ms 114.761 ms 100.101 ms 103.154 ms 94.705 ms 98.644 ms 97.759 ms * 99.942 ms 99.807 ms 98.197 ms 97.274 ms * (16% loss)
14 12-122-254-238.attens.net (12.122.254.238) 100.001 ms
12.122.251.190 (12.122.251.190) 89.910 ms
12-122-254-238.attens.net (12.122.254.238) 103.190 ms
12.122.251.190 (12.122.251.190) 78.905 ms 80.722 ms 78.903 ms
12-122-254-238.attens.net (12.122.254.238) 93.670 ms 98.813 ms *
12.122.251.190 (12.122.251.190) 81.880 ms 78.745 ms *
12-122-254-238.attens.net (12.122.254.238) 97.218 ms *
12.122.251.190 (12.122.251.190) 211.324 ms *
12-122-254-238.attens.net (12.122.254.238) 94.162 ms 99.623 ms
12-122-254-234.attens.net (12.122.254.234) 128.274 ms 138.020 ms
12.122.251.190 (12.122.251.190) 136.469 ms
12-122-254-238.attens.net (12.122.254.238) 95.055 ms
12.122.251.190 (12.122.251.190) 78.971 ms 78.012 ms 79.027 ms 79.052 ms
12-122-254-238.attens.net (12.122.254.238) 95.437 ms
12.122.251.190 (12.122.251.190) 81.548 ms *
12-122-254-238.attens.net (12.122.254.238) 97.858 ms (16% loss)
15 206.16.68.46 (206.16.68.46) 132.629 ms
mdf001c7613r0003-gig-12-1.lax1.attens.net (12.129.193.254) 100.670 ms *
mdf001c7613r0002.lax1.attens.net (206.16.68.54) 93.549 ms * *
mdf001c7613r0003-gig-12-1.lax1.attens.net (12.129.193.254) 95.802 ms *
mdf001c7613r0002.lax1.attens.net (206.16.68.54) 100.027 ms
206.16.68.46 (206.16.68.46) 130.784 ms
mdf001c7613r0002.lax1.attens.net (206.16.68.54) 133.000 ms * * 180.251 ms *
mdf001c7613r0003-gig-12-1.lax1.attens.net (12.129.193.254) 97.842 ms *
mdf001c7613r0002.lax1.attens.net (206.16.68.54) 96.782 ms *
mdf001c7613r0003-gig-12-1.lax1.attens.net (12.129.193.254) 102.585 ms
mdf001c7613r0004-gig-10-1.lax1.attens.net (12.129.193.250) 130.788 ms
206.16.68.46 (206.16.68.46) 136.257 ms
mdf001c7613r0002.lax1.attens.net (206.16.68.54) 102.329 ms
mdf001c7613r0004-gig-10-1.lax1.attens.net (12.129.193.250) 130.773 ms
mdf001c7613r0003-gig-12-1.lax1.attens.net (12.129.193.254) 94.121 ms * 97.943 ms *
mdf001c7613r0002.lax1.attens.net (206.16.68.54) 96.796 ms
mdf001c7613r0003-gig-12-1.lax1.attens.net (12.129.193.254) 101.687 ms (36% loss)
16 * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * (100% loss)
17 * * * * * * * *
Same issue as the rest, long lags which eventually lead to a game crash. Usually precursored by sporadic lag spikes for about 10 minutes, then full lag out and inability to reconnect. Usually get to "Success!" and then freeze. Windows 7.

Tracing route to 12.129.209.68 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 7 ms 7 ms 9 ms L100.NYCMNY-VFTTP-125.verizon-gni.net [72.89.93.1]
3 6 ms 7 ms 10 ms G1-5-5-0.NYCMNY-LCR-22.verizon-gni.net [130.81.189.102]
4 7 ms 7 ms 8 ms so-6-1-0-0.NY5030-BB-RTR2.verizon-gni.net [130.81.151.224]
5 10 ms 7 ms 7 ms 0.xe-9-1-0.BR2.NYC4.ALTER.NET [152.63.23.141]
6 11 ms 11 ms 9 ms 192.205.36.57
7 78 ms 78 ms 80 ms cr1.n54ny.ip.att.net [12.122.86.6]
8 77 ms 77 ms 81 ms cr2.cgcil.ip.att.net [12.122.1.2]
9 123 ms * * cr1.cgcil.ip.att.net [12.122.2.53]
10 * * 130 ms cr2.dvmco.ip.att.net [12.122.31.85]
11 93 ms 96 ms 94 ms cr1.slkut.ip.att.net [12.122.30.25]
12 * * * Request timed out.
13 * * 123 ms gar29.la2ca.ip.att.net [12.122.129.241]
14 * * 74 ms 12.122.251.190
15 127 ms * * 206.16.68.46
16 * * * Request timed out.
17

END

Tracing route to 12.129.209.68 over a maximum of 30 hops

0 Me-PC.home [192.168.1.13]
1 Wireless_Broadband_Router.home [192.168.1.1]
2 L100.NYCMNY-VFTTP-125.verizon-gni.net [72.89.93.1]
3 G1-5-5-0.NYCMNY-LCR-22.verizon-gni.net [130.81.189.102]
4 so-6-1-0-0.NY5030-BB-RTR2.verizon-gni.net [130.81.151.224]
5 0.xe-9-1-0.BR2.NYC4.ALTER.NET [152.63.23.141]
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 * * *
Computing statistics for 200 seconds...
Well i posted earlier that verizon called and said that the issue may be resolved. ha thats a lie. it is now 7 pm in new york and i can't connect to the game. this issue needs to be fixed. better yet i think i am going to go back to cable and when i lag i will know its cable and that is how cable rolls. at least i will still be able to play during the lag, but not well. at this point i don't know who to blame. just getting tired of the same !@#$ing bull%^-*. someone needs to stay on top of this issue instead of taking feedback of what the !@#$ is going on and get this %^-* fixed. so glad that i wasn't in a dungeon or yet a raid. i am not even confident to run a dungeon during off peak hours because of this issue.
spotflux is a bandaid but it still lags at about 300ms when in an LFR. Get this routing issue addressed ASAP please.

EDIT>> well last time spotflux kept me at 300ms, but this time after logging in it has failed to get me better than 1200ms. It's not a fix after all.

Besides, it makes me reset my password every time because I'm logging in from a "different IP" in effect.
02/09/2013 04:21 PMPosted by Gilraen
Well i posted earlier that verizon called and said that the issue may be resolved. ha thats a lie. it is now 7 pm in new york and i can't connect to the game. this issue needs to be fixed. better yet i think i am going to go back to cable and when i lag i will know its cable and that is how cable rolls. at least i will still be able to play during the lag, but not well. at this point i don't know who to blame. just getting tired of the same !@#$ing bull%^-*. someone needs to stay on top of this issue instead of taking feedback of what the !@#$ is going on and get this %^-* fixed. so glad that i wasn't in a dungeon or yet a raid. i am not even confident to run a dungeon during off peak hours because of this issue.


Uh, just letting you know...your network is working as intended!! :)
I still have that same issues, but it's whenever it decides it wants to happen... very annoying.
Boulderfist - US
Yonkers, NY

Tracing route to 213-155-155-233.customer.teliacarrier.com [213.155.155.233]
over a maximum of 30 hops:

1 30 ms 3 ms 28 ms Wireless_Broadband_Router.home [192.168.1.1]
2 10 ms 9 ms 9 ms L100.NYCMNY-VFTTP-166.verizon-gni.net [71.251.25.1]
3 15 ms 14 ms 14 ms G0-13-2-4.NYCMNY-LCR-21.verizon-gni.net [130.81.137.56]
4 13 ms 11 ms 11 ms ae0-0.NY325-BB-RTR1.verizon-gni.net [130.81.209.102]
5 17 ms 14 ms 14 ms ge-13-1-0-0.PHIL-BB-RTR1.verizon-gni.net [130.81.23.130]
6 26 ms 24 ms 24 ms 0.xe-5-1-0.XL3.IAD8.ALTER.NET [152.63.6.9]
7 47 ms 29 ms 19 ms TenGigE0-6-1-0.GW1.IAD8.ALTER.NET [152.63.35.137]
8 41 ms 41 ms 42 ms teliasonera-gw.customer.alter.net [63.125.125.42]
9 56 ms 38 ms 39 ms ash-bb4-link.telia.net [213.155.136.38]
10 93 ms 94 ms 94 ms ldn-bb2-link.telia.net [80.91.251.208]
11 137 ms 137 ms 138 ms adm-bb3-link.telia.net [80.91.253.146]
12 130 ms 139 ms 128 ms adm-b5-link.telia.net [80.91.253.171]
13

Yesterday I couldn't even login/connect, today its at around 235/675ms but it's causing at least a 5-10 second delay with all actions.
Daggerspine - US
Clarkburg - MD
Verizon FIOS

as of 1947 hours EST 02/09/2013
5222 home 79 world

about 20 min ago was 1180 h / 7639
with fps from 14 to 20

C:\Users\admin>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 4 ms 4 ms L100.WASHDC-VFTTP-92.verizon-gni.net [71.191.59.
1]
3 4 ms 9 ms 6 ms G0-12-3-5.WASHDC-LCR-21.verizon-gni.net [130.81.
184.76]
4 6 ms 7 ms 6 ms so-7-1-0-0.RES-BB-RTR1.verizon-gni.net [130.81.1
99.30]
5 33 ms * * 0.xe-4-3-0.BR1.IAD8.ALTER.NET [152.63.37.37]
6 11 ms 9 ms 9 ms 192.205.36.141
7 88 ms 81 ms 84 ms cr2.wswdc.ip.att.net [12.122.81.250]
8 117 ms * 113 ms cr1.cgcil.ip.att.net [12.122.18.21]
9 82 ms 81 ms 84 ms cr2.dvmco.ip.att.net [12.122.31.85]
10 * 118 ms * cr1.slkut.ip.att.net [12.122.30.25]
11 113 ms 114 ms * cr2.la2ca.ip.att.net [12.122.30.30]
12 81 ms 82 ms 81 ms gar29.la2ca.ip.att.net [12.122.129.241]
13 81 ms 79 ms 79 ms 12-122-254-238.attens.net [12.122.254.238]
14 * 115 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 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.
Sigh here we go again! Lagging like crazy! Disconnecting from Arena matches. #@!$!@$
Can we get some feedback from blizzard, an update or something. I was able to log in today after i reset my router. It was fine for a while but then went back up to 7685 latency.
Posted pathping earlier (page 5, I think). I was on earlier today from 12-3pm EST, then logged back on around 7:40pm with no issues. Started disconnecting at 8:05pm, and now I either get stuck at "Success!" or get repeated "Battle.net Error#2" messages.

Personally, this issue appears, or becomes more evident during peak hours; it persists for about ~3 hours and then everything becomes *magically* fixed once everyone goes to bed.

I really do hope this gets resolved and permanently, because the alternative is imgur-lurking all night. -_-;;
Diablo 3
New York, NY

Was up this afternoon, but this evening it's pretty much the same as it was 24 hours ago. Thanks to the one blue, who posted "Thanks for posting." Makes me feel at least that someone is looking into this.

Here's the latest tracert...pretty much the same as the one I posted 24 hours ago.

(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 7 ms 8 ms 6 ms L100.NYCMNY-VFTTP-156.verizon-gni.net [98.113.86
.1]
3 14 ms 11 ms 9 ms G0-1-3-2.NYCMNY-LCR-21.verizon-gni.net [130.81.1
87.226]
4 9 ms 11 ms 9 ms 130.81.199.10
5 12 ms 8 ms 9 ms 0.xe-9-0-0.BR2.NYC4.ALTER.NET [152.63.20.189]
6 52 ms 51 ms 53 ms 192.205.34.49
7 * 127 ms 131 ms cr1.n54ny.ip.att.net [12.122.86.6]
8 * * * Request timed out.
9 131 ms * * cr1.cgcil.ip.att.net [12.122.2.53]
10 92 ms 91 ms 96 ms cr2.dvmco.ip.att.net [12.122.31.85]
11 * 129 ms * cr1.slkut.ip.att.net [12.122.30.25]
12 * * * Request timed out.
13 110 ms 77 ms 78 ms gar29.la2ca.ip.att.net [12.122.129.241]
14 78 ms 78 ms 79 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 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * ^C
C:\Users\David>
Can we get some feedback from blizzard, an update or something....


This
Here is a new pathping as of a few minutes ago:

Tracing route to mdf1-bi8k-1-ve-87.phx1.attens.net [63.241.138.161]
over a maximum of 30 hops:
0 <Removed>
1 <Removed>
2 dslrouter [192.168.1.1]
3 10.32.71.1
4 P0-6-2-2.NYCMNY-LCR-22.verizon-gni.net [130.81.46.62]
5 so-3-1-0-0.NY5030-BB-RTR2.verizon-gni.net [130.81.199.12]
6 0.xe-9-1-0.BR2.NYC4.ALTER.NET [152.63.23.141]
7 192.205.34.49
8 cr2.n54ny.ip.att.net [12.122.86.10]
9 cr2.wswdc.ip.att.net [12.122.3.38]
10 * * *
Computing statistics for 225 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% 192.168.100.1
0/ 100 = 0% |
2 1ms 0/ 100 = 0% 0/ 100 = 0% dslrouter [192.168.1.1]
0/ 100 = 0% |
3 23ms 0/ 100 = 0% 0/ 100 = 0% 10.32.71.1
0/ 100 = 0% |
4 26ms 0/ 100 = 0% 0/ 100 = 0% P0-6-2-2.NYCMNY-LCR-22.verizon-gni.net [130.81.46.62]
0/ 100 = 0% |
5 32ms 0/ 100 = 0% 0/ 100 = 0% so-3-1-0-0.NY5030-BB-RTR2.verizon-gni.net [130.81.199.12]
0/ 100 = 0% |
6 47ms 20/ 100 = 20% 20/ 100 = 20% 0.xe-9-1-0.BR2.NYC4.ALTER.NET [152.63.23.141]
0/ 100 = 0% |
7 30ms 0/ 100 = 0% 0/ 100 = 0% 192.205.34.49
100/ 100 =100% |
8 --- 100/ 100 =100% 0/ 100 = 0% cr2.n54ny.ip.att.net [12.122.86.10]
0/ 100 = 0% |
9 --- 100/ 100 =100% 0/ 100 = 0% cr2.wswdc.ip.att.net [12.122.3.38]

Trace complete.


I do see a 20% packet loss between Verizon and Alter.net, which didn't appear yesterday. Grawrgh.
Realm: Shu'halo
Location: Staten Island, New York
Description: Server lag every hour so makes game unplayable, I have 4 other friends with Verizon as well who also have the same issue.

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

1 68 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 8 ms 6 ms 7 ms L100.NYCMNY-VFTTP-114.verizon-gni.net [98.113.34.1]
3 9 ms 11 ms 12 ms G0-10-4-2.NYCMNY-LCR-22.verizon-gni.net [130.81.37.20]
4 11 ms 104 ms 74 ms so-3-1-0-0.NY5030-BB-RTR2.verizon-gni.net [130.81.199.12]
5 10 ms 9 ms 10 ms 0.xe-9-1-0.BR2.NYC4.ALTER.NET [152.63.23.141]
6 79 ms 77 ms 77 ms 192.205.36.57
7 93 ms 92 ms 93 ms cr2.n54ny.ip.att.net [12.122.86.10]
8 92 ms 92 ms 94 ms cr2.wswdc.ip.att.net [12.122.3.38]
9 104 ms 96 ms 91 ms cr1.attga.ip.att.net [12.122.1.173]
10 99 ms 93 ms 94 ms cr2.dlstx.ip.att.net [12.122.28.174]
11 120 ms * 128 ms cr1.dlstx.ip.att.net [12.122.1.209]
12 95 ms 97 ms 91 ms cr1.phmaz.ip.att.net [12.122.28.182]
13 101 ms 122 ms 86 ms 12.123.206.165
14 123 ms 91 ms 92 ms 12-122-254-50.attens.net [12.122.254.50]
15 191 ms 95 ms 95 ms mdf002c7613r0001-gig-12-1.phx1.attens.net [63.241.130.210]
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 * *
[/code]

Join the Conversation

Return to Forum