Verizon ISP Issues - Tracking

(Locked)

90 Pandaren Hunter
12605
02/26/2013 04:47 AMPosted by Nethril
I was hoping Blizzard would have provided an update since the last time they posted. As I said earlier in this thread, a little updating goes a long way to keeping people happy. I'm still very frustrated. My latency was a bit better last night, but I am now experiencing spikes where it will just disconnect me out of nowhere. Any update / assistance is appreciated Blizzard.

I second this. I've been using SmoothPing for a month now, and it's not even working consistently anymore. I lagged out and DC'd twice last night after my latency shot up to 2k, and that was with SmoothPing on.

I spent most of my night last night looking into different tunneling services because it's impossible to raid with lag this bad. I'm trying out BattlePing now, but it's nerve wracking constantly worrying about triggering the autoban system (which has happened twice now).

I realize this isn't actually Blizzard's fault, but this situation is really frustrating and updates go a long way when we're all sitting here eager for this to be resolved. :/
Support Forum Agent
Hey all!

Our networking staff was just informed by Verizon that some improvements have now been implemented. Let us know how things are looking, and if it still seems subpar please post some new traces. Thanks! :)
90 Pandaren Hunter
12605
Thank you for the update. Still doesn't appear to be fixed though. It's timing out in the exact same place as the last traceroute I posted. :/

Hyjal
Thousand Oaks, CA


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

1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 20 ms 19 ms 20 ms L100.LSANCA-VFTTP-109.verizon-gni.net [98.112.230.1]
3 24 ms 27 ms 28 ms G0-6-1-0.LSANCA-LCR-21.verizon-gni.net [130.81.138.60]
4 23 ms 26 ms 26 ms ae2-0.LAX01-BB-RTR1.verizon-gni.net [130.81.209.254]
5 21 ms 61 ms 25 ms 0.xe-3-0-0.BR3.LAX15.ALTER.NET [152.63.114.241]
6 28 ms 26 ms 26 ms 204.255.168.134
7 35 ms 45 ms 36 ms cr1.la2ca.ip.att.net [12.123.30.6]
8 38 ms 39 ms 43 ms cr2.phmaz.ip.att.net [12.122.31.190]
9 34 ms 33 ms 33 ms 12.123.158.133
10 32 ms 32 ms 33 ms 12-122-254-50.attens.net [12.122.254.50]
11 33 ms 33 ms 33 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.
100 Blood Elf Priest
19305
Me personally, I've been seeing weird short lagspikes but nothing unplayable (I've been in alt 10's / GDKP 25's the past few days without tunneling nor unplayable issues) and I'm one of the several from Thousand Oaks (geez, such small retirementville, so many closet wow players). I'll post another trace if things start to go sour again.

@kayari: I've been having good luck with Pingzapper so far (though I was doing okay without it this past weekend), not sure if it would work for you though because we're playing on different data centers - and I think that's the difference between us atm.
90 Pandaren Hunter
12605
Me personally, I've been seeing weird short lagspikes but nothing unplayable (I've been in alt 10's / GDKP 25's the past few days without tunneling nor unplayable issues) and I'm one of the several from Thousand Oaks (geez, such small retirementville, so many closet wow players). I'll post another trace if things start to go sour again.

@kayari: I've been having good luck with Pingzapper so far (though I was doing okay without it this past weekend), not sure if it would work for you though because we're playing on different data centers - and I think that's the difference between us atm.


So many people from Thousand Oaks! I saw quite a few scrolling through this thread.

I looked into PingZapper, so I may try it if BattlePing doesn't work as well as I'd like. I'm really not even sure what the issue is anymore, as I was originally one of the people having lag issues connecting to the Arizona data centers. I don't even know if that problem has been fixed, but I can't seem to find the thread anymore, so I guess it's not being updated. :<
90 Night Elf Rogue
12490
Here's my trace route again from Canyon Lake, CA. Unfortunately have to stick with Verizon DSL until they upgrade this area to FIOS. It's showing even more packet loss than any previous trace routes I've done.

Tracing route to 63.240.161.189 over a maximum of 30 hops

1 3 ms 1 ms 1 ms Zoom.Home [192.168.1.1]
2 45 ms 45 ms 45 ms 108.38.78.1
3 50 ms 51 ms 51 ms G0-5-4-7.LSANCA-LCR-21.verizon-gni.net [130.81.193.244]
4 50 ms 50 ms 50 ms 130.81.199.38
5 50 ms 50 ms 53 ms 0.xe-3-0-0.BR3.LAX15.ALTER.NET [152.63.114.241]
6 49 ms 49 ms 49 ms 192.205.35.161
7 105 ms * * cr2.la2ca.ip.att.net [12.123.30.150]
8 111 ms 197 ms 177 ms cr1.slkut.ip.att.net [12.122.30.29]
9 109 ms 108 ms 110 ms cr2.dvmco.ip.att.net [12.122.30.26]
10 110 ms * 105 ms cr1.cgcil.ip.att.net [12.122.31.86]
11 * 105 ms 104 ms gar2.clboh.ip.att.net [12.122.133.197]
12 106 ms * 107 ms 12.122.251.22
13 106 ms * 106 ms 63.240.130.214
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.

Oh nvm for now, just reset the modem and it appears to be working for now. I guess I'll wait and see if I could play this evening or not. Hopefully it's fixed.
Edited by Celar on 2/26/2013 3:17 PM PST
86 Tauren Druid
6995
lol I read this thread just to know how peoples name their PC
Support Forum Agent
Thank you for the update. Still doesn't appear to be fixed though. It's timing out in the exact same place as the last traceroute I posted. :/


Hi Kayari!

Where you see the trace as timing out, it's actually reaching our datacenter. Our datacenter garbles data intentionally, so your trace is actually clean and normal. What symptoms are you experiencing? Also, can you post a pathping so we can check for packet loss that's not showing on the trace route? Thanks! :)
100 Human Warrior
14420
I am still experiencing the same issue. It took upwards of 5-10 seconds to obtain each IP listed in route that didn't have a name associated.

C:\Users\NethriL>tracert 206.18.98.160

Tracing route to 206.18.98.160.tms-idc.com [206.18.98.160]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 13 ms 11 ms 5 ms L100.BLTMMD-VFTTP-32.verizon-gni.net [96.234.147
.1]
3 12 ms 12 ms 14 ms G0-5-0-3.BLTMMD-LCR-21.verizon-gni.net [130.81.9
7.122]
4 12 ms 9 ms 8 ms so-1-1-0-0.RES-BB-RTR1.verizon-gni.net [130.81.1
99.2]
5 17 ms 9 ms 9 ms 0.xe-4-3-0.BR1.IAD8.ALTER.NET [152.63.37.37]
6 9 ms 8 ms 9 ms 192.205.36.141
7 50 ms 48 ms 52 ms cr2.wswdc.ip.att.net [12.122.81.250]
8 66 ms 71 ms 69 ms cr1.cgcil.ip.att.net [12.122.18.21]
9 118 ms 152 ms 134 ms gar2.clboh.ip.att.net [12.122.133.197]
10 59 ms 51 ms 101 ms 12.122.251.22
11 102 ms 96 ms 101 ms 63.240.130.214
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * ^C
C:\Users\NethriL>

Tracing route to 206.18.98.160.tms-idc.com [206.18.98.160]
over a maximum of 30 hops:
0 NethriL-PC.home [192.168.1.3]
1 Wireless_Broadband_Router.home [192.168.1.1]
2 L100.BLTMMD-VFTTP-32.verizon-gni.net [96.234.147.1]
3 G0-5-0-3.BLTMMD-LCR-21.verizon-gni.net [130.81.97.122]
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 gar2.clboh.ip.att.net [12.122.133.197]
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 NethriL-PC.home [192.168.1.3]
0/ 100 = 0% |
1 2ms 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.BLTMMD-VFTTP-32.verizon-gni.net [96.234.147.1]
0/ 100 = 0% |
3 13ms 0/ 100 = 0% 0/ 100 = 0% G0-5-0-3.BLTMMD-LCR-21.verizon-gni.net [130.81.97.122]
0/ 100 = 0% |
4 17ms 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 20ms 0/ 100 = 0% 0/ 100 = 0% 0.xe-4-3-0.BR1.IAD8.ALTER.NET [152.63.37.37]
0/ 100 = 0% |
6 20ms 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% gar2.clboh.ip.att.net [12.122.133.197]
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.

Thank you very much for the update and effort on your part. Verizon has been unwilling to even entertain it as a possible issue. I appreciate your continued support to resolve it. Unfortunately, the issue still exists.
Edited by Nethril on 2/26/2013 5:22 PM PST
I haven't had issues since I last posted on this forum until tonight. I was doing my Klaxxi dailies when all of a sudden all the mobs just stopped moving and when I tried to attack something nothing would happen, the mob would continue to stand there. I see that Verizon has been notified, so I'm hoping this stops happening soon.

1 wireless_broadband_router (192.168.1.1) 3.113 ms 1.560 ms 0.989 ms
2 72.80.102.1 (72.80.102.1) 6.817 ms 125.448 ms 3.419 ms
3 g0-10-4-0.nycmny-lcr-22.verizon-gni.net (130.81.184.6) 8.413 ms 8.446 ms 10.922 ms
4 ae0-0.ny5030-bb-rtr1.verizon-gni.net (130.81.209.118) 15.847 ms 3.170 ms 10.777 ms
5 0.xe-3-3-0.br2.nyc4.alter.net (152.63.23.133) 45.303 ms * *
6 192.205.36.57 (192.205.36.57) 39.521 ms 39.416 ms 48.846 ms
7 cr2.n54ny.ip.att.net (12.122.86.10) 86.661 ms 89.881 ms 87.672 ms
8 cr2.wswdc.ip.att.net (12.122.3.38) 90.008 ms 92.821 ms 90.452 ms
9 cr1.attga.ip.att.net (12.122.1.173) 76.258 ms 80.102 ms 84.446 ms
10 cr2.dlstx.ip.att.net (12.122.28.174) 88.988 ms 91.660 ms 91.640 ms
11 cr1.dlstx.ip.att.net (12.122.1.209) 72.878 ms 88.436 ms 78.306 ms
12 cr1.phmaz.ip.att.net (12.122.28.182) 76.392 ms 78.060 ms 75.711 ms
13 cr1.phmaz.ip.att.net (12.123.206.185) 123.335 ms 74.400 ms 85.085 ms
14 12-122-254-50.attens.net (12.122.254.50) 92.497 ms 88.960 ms 88.299 ms
15 mdf002c7613r0002-gig-10-1.phx1.attens.net (63.241.130.206) 85.442 ms
mdf002c7613r0001-gig-12-1.phx1.attens.net (63.241.130.210) 87.962 ms
mdf002c7613r0002-gig-10-1.phx1.attens.net (63.241.130.206) 88.815 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 * * *
90 Pandaren Hunter
12605
02/26/2013 05:07 PMPosted by Kaltonis
Thank you for the update. Still doesn't appear to be fixed though. It's timing out in the exact same place as the last traceroute I posted. :/


Hi Kayari!

Where you see the trace as timing out, it's actually reaching our datacenter. Our datacenter garbles data intentionally, so your trace is actually clean and normal. What symptoms are you experiencing? Also, can you post a [url="https://www.battle.net/support/article/718?utm_source=internal&utm_medium=support_forums&utm_campaign=BlizzardCS"]pathping[/url] so we can check for packet loss that's not showing on the trace route? Thanks! :)

Thanks for the response. :>

Originally, I was one of the many people having issues connecting to servers in the Arizona data centers (http://us.battle.net/wow/en/forum/topic/7593741008), which started about six weeks ago. My latency is normally around 35ms, but ever since this started, it would randomly shoot up to anywhere from 1k to 10k and I would completely lag out. It would do that weird thing where everything stops and everyone is running in place and eventually sort of fast forward. It was constantly happening and completely unplayable.

A blue poster in that thread suggested SmoothPing, which I've been using for about a month now to bypass the lag so I could raid. It worked fine up until about a week ago, and now I'm having lag issues even with SmoothPing turned on, although not nearly as bad. Last night my latency shot up to around 2k a few times, and eventually I lagged out completely and had to alt+F4 and restart my game on a different SmoothPing server to be able to play again. I'm on Verizon FiOS and never had any issues with it until the problem with the Arizona data centers started.

Here's my pathping:


Tracing route to mdf1-bi8k-1-ve-87.phx1.attens.net [63.241.138.161]
over a maximum of 30 hops:
0 Kynzu-PC.home [192.168.1.4]
1 Wireless_Broadband_Router.home [192.168.1.1]
2 L100.LSANCA-VFTTP-109.verizon-gni.net [98.112.230.1]
3 G0-6-1-0.LSANCA-LCR-21.verizon-gni.net [130.81.138.60]
4 ae2-0.LAX01-BB-RTR1.verizon-gni.net [130.81.209.254]
5 0.xe-3-0-0.BR3.LAX15.ALTER.NET [152.63.114.241]
6 204.255.168.134
7 cr1.la2ca.ip.att.net [12.123.30.6]
8 cr2.phmaz.ip.att.net [12.122.31.190]
9 12.123.158.133
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 Kynzu-PC.home [192.168.1.4]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% Wireless_Broadband_Router.home [192.168.1.1]
0/ 100 = 0% |
2 21ms 0/ 100 = 0% 0/ 100 = 0% L100.LSANCA-VFTTP-109.verizon-gni.net [98.112.230.1]
0/ 100 = 0% |
3 26ms 0/ 100 = 0% 0/ 100 = 0% G0-6-1-0.LSANCA-LCR-21.verizon-gni.net [130.81.138.60]
0/ 100 = 0% |
4 29ms 0/ 100 = 0% 0/ 100 = 0% ae2-0.LAX01-BB-RTR1.verizon-gni.net [130.81.209.254]
0/ 100 = 0% |
5 27ms 0/ 100 = 0% 0/ 100 = 0% 0.xe-3-0-0.BR3.LAX15.ALTER.NET [152.63.114.241]
0/ 100 = 0% |
6 26ms 0/ 100 = 0% 0/ 100 = 0% 204.255.168.134
100/ 100 =100% |
7 --- 100/ 100 =100% 0/ 100 = 0% cr1.la2ca.ip.att.net [12.123.30.6]
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.158.133
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.
100 Blood Elf Paladin
17595
Issues: This usually happens during peak hours (8-9pm est), I DC from the game, but chat logs are still going, ventrillo isn't lagging, and I can still surf the internet at my usual speed. I have to alt + F4 and relog into the game, and even then I get the 101error. Somedays this happens, somedays it does not, very inconsistent

Not sure if I should run the tracer when I'm experiencing the issue, but this is what I got:

Tracing route to xxx.xxx.xxx.xxx [199.101.28.20]
over a maximum of 30 hops:

1 <1 ms 1 ms 1 ms dslrouter [192.168.1.1]
2 28 ms 29 ms 28 ms 10.29.24.1
3 30 ms 30 ms 30 ms P2-0-3.SCTNPA-LCR-02.verizon-gni.net [130.81.193.90]
4 48 ms 146 ms 99 ms so-2-1-1-0.NY5030-BB-RTR2.verizon-gni.net [130.81.22.14]
5 49 ms 49 ms 49 ms 0.xe-3-1-0.BR3.NYC4.ALTER.NET [152.63.26.117]
6 75 ms 73 ms 73 ms 204.255.168.194
7 48 ms 47 ms 48 ms NOMINUM.Gi9-7.ar3.DCA3.gblx.net [64.212.109.90]
8 49 ms 50 ms 49 ms search.dnsassist.verizon.net [199.101.28.20]

Trace complete.

Edit: Here's one of me when the issue is occuring
Tracing route to xxx.xxx.xxx.xxx [199.101.28.20]
over a maximum of 30 hops:

1 <1 ms 1 ms 1 ms dslrouter [192.168.1.1]
2 28 ms 28 ms 29 ms 10.29.24.1
3 30 ms 30 ms 30 ms P2-0-3.SCTNPA-LCR-02.verizon-gni.net [130.81.193.90]
4 51 ms 48 ms 60 ms so-2-1-1-0.NY5030-BB-RTR2.verizon-gni.net [130.81.22.14]
5 48 ms 49 ms 49 ms 0.xe-3-1-0.BR3.NYC4.ALTER.NET [152.63.26.117]
6 62 ms 63 ms 115 ms 204.255.168.194
7 48 ms 47 ms 46 ms NOMINUM.Gi9-7.ar3.DCA3.gblx.net [64.212.109.90]
8 48 ms 48 ms 49 ms search.dnsassist.verizon.net [199.101.28.20]

Trace complete.
Edited by Captdeadman on 2/26/2013 6:46 PM PST
70 Pandaren Monk
12380
server - uldum
location bronx n.y
isp verizon
had this problem for a couple weeks then it cleared up for id say the last two weeks and it came back around 9 30 est tonight .. dont know what changed
Tracing route to 12.129.223.28 over a maximum of 30 hops

1 51 ms <1 ms <1 ms 192.168.1.1
2 4 ms 4 ms 3 ms L100.NYCMNY-VFTTP-169.verizon-gni.net [71.190.13
5.1]
3 9 ms 7 ms 7 ms G1-5-1-5.NYCMNY-LCR-22.verizon-gni.net [130.81.1
91.28]
4 6 ms 6 ms 6 ms so-5-0-0-0.NY5030-BB-RTR1.verizon-gni.net [130.8
1.22.18]
5 * * * Request timed out.
6 90 ms 113 ms 88 ms 192.205.34.49
7 92 ms 91 ms 91 ms cr1.n54ny.ip.att.net [12.122.86.6]
8 82 ms 86 ms 122 ms cr2.cgcil.ip.att.net [12.122.1.2]
9 89 ms 91 ms 91 ms cr1.cgcil.ip.att.net [12.122.2.53]
10 96 ms 87 ms 86 ms cr2.dvmco.ip.att.net [12.122.31.85]
11 86 ms 82 ms 85 ms cr1.slkut.ip.att.net [12.122.30.25]
12 83 ms 83 ms 83 ms cr2.la2ca.ip.att.net [12.122.30.30]
13 83 ms 82 ms 83 ms gar29.la2ca.ip.att.net [12.122.129.241]
14 89 ms 84 ms 88 ms 12-122-254-234.attens.net [12.122.254.234]
15 84 ms 84 ms 84 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.
Edited by Wasu on 2/26/2013 7:00 PM PST
90 Human Warrior
11020
Realm (if a WoW player): Kel'Thuzad
Your Location (city, state): Brooklyn, NY
Still happening mainly during prime time hours. Got Disconnected tonight around 9pm and latency went up from 28ms world/home to 150ms.

C:\Users\>pathping 63.240.104.93

Tracing route to 63.240.104.93 over a maximum of 30 hops

0 XXX-PC.westell.com [192.168.1.16]
1 dslrouter.westell.com [192.168.1.1]
2 10.32.170.1
3 P0-7-1-4.NYCMNY-LCR-21.verizon-gni.net [130.81.136.166]
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 gar1.nw2nj.ip.att.net [12.122.130.93]
9 12.122.251.6
10 mdf001c7613r0004-gig-10-1.nyc3.attens.net [63.240.65.18]
11 * * *
Computing statistics for 250 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Ilya-PC.westell.com [192.168.1.16]

0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% dslrouter.westell.com [192.168.1.1
]
0/ 100 = 0% |
2 24ms 0/ 100 = 0% 0/ 100 = 0% 10.32.170.1
0/ 100 = 0% |
3 28ms 0/ 100 = 0% 0/ 100 = 0% P0-7-1-4.NYCMNY-LCR-21.verizon-gni
.net [130.81.136.166]
0/ 100 = 0% |
4 37ms 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 75ms 8/ 100 = 8% 8/ 100 = 8% 0.xe-9-0-0.BR2.NYC4.ALTER.NET [152
.63.20.189]
0/ 100 = 0% |
6 90ms 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% gar1.nw2nj.ip.att.net [12.122.130.
93]
0/ 100 = 0% |
9 --- 100/ 100 =100% 0/ 100 = 0% 12.122.251.6
0/ 100 = 0% |
10 --- 100/ 100 =100% 0/ 100 = 0% mdf001c7613r0004-gig-10-1.nyc3.att
ens.net [63.240.65.18]

Trace complete.

C:\Users\>tracert 63.240.104.93

Tracing route to 63.240.104.93 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms dslrouter.westell.com [192.168.1.1]
2 24 ms 24 ms 24 ms 10.32.170.1
3 27 ms 27 ms 27 ms P0-7-1-4.NYCMNY-LCR-21.verizon-gni.net [130.81.1
36.166]
4 27 ms 26 ms 26 ms so-11-0-0-0.NY325-BB-RTR1.verizon-gni.net [130.8
1.151.222]
5 32 ms 81 ms 35 ms 0.xe-9-0-0.BR2.NYC4.ALTER.NET [152.63.20.189]
6 163 ms 72 ms 81 ms 192.205.36.57
7 30 ms 32 ms 31 ms cr2.n54ny.ip.att.net [12.122.86.10]
8 32 ms 95 ms 74 ms gar1.nw2nj.ip.att.net [12.122.131.81]
9 110 ms 112 ms 111 ms 12.122.251.6
10 116 ms 118 ms 118 ms mdf001c7613r0004-gig-10-1.nyc3.attens.net [63.24
0.65.18]

100 Night Elf Druid
13365
Just ducking my head in to say that I'm no longer having an issues (So far...) tonight like I was a week ago. Here's a pathping just for old time's sake. :)

Tracing route to 12.129.209.68 over a maximum of 30 hops

0 Midnight-PC.home [192.168.1.21]
1 192.168.1.1
2 L100.LSANCA-VFTTP-54.verizon-gni.net [96.251.184.1]
3 P0-2-0-2.LSANCA-LCR-21.verizon-gni.net [130.81.60.108]
4 so-4-1-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81.151.246]
5 0.xe-3-0-0.BR3.LAX15.ALTER.NET [152.63.114.241]
6 192.205.35.161
7 cr2.la2ca.ip.att.net [12.123.30.134]
8 gar29.la2ca.ip.att.net [12.122.129.241]
9 12.122.251.190
10 206.16.68.46
11 * * *
Computing statistics for 250 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Midnight-PC.home [192.168.1.21]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1
0/ 100 = 0% |
2 11ms 0/ 100 = 0% 0/ 100 = 0% L100.LSANCA-VFTTP-54.verizon-gni.n
et [96.251.184.1]
0/ 100 = 0% |
3 15ms 0/ 100 = 0% 0/ 100 = 0% P0-2-0-2.LSANCA-LCR-21.verizon-gni
.net [130.81.60.108]
0/ 100 = 0% |
4 16ms 0/ 100 = 0% 0/ 100 = 0% so-4-1-0-0.LAX01-BB-RTR1.verizon-g
ni.net [130.81.151.246]
0/ 100 = 0% |
5 17ms 0/ 100 = 0% 0/ 100 = 0% 0.xe-3-0-0.BR3.LAX15.ALTER.NET [15
2.63.114.241]
0/ 100 = 0% |
6 16ms 0/ 100 = 0% 0/ 100 = 0% 192.205.35.161
100/ 100 =100% |
7 --- 100/ 100 =100% 0/ 100 = 0% cr2.la2ca.ip.att.net [12.123.30.13
4]
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% 206.16.68.46

Trace complete.
Tracing route to 12.129.209.68 over a maximum of 30 hops

0 Midnight-PC.home [192.168.1.21]
1 192.168.1.1
2 L100.LSANCA-VFTTP-54.verizon-gni.net [96.251.184.1]
3 P0-2-0-2.LSANCA-LCR-21.verizon-gni.net [130.81.60.108]
4 so-4-1-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81.151.246]
5 0.xe-3-0-0.BR3.LAX15.ALTER.NET [152.63.114.241]
6 192.205.35.161
7 cr2.la2ca.ip.att.net [12.123.30.134]
8 gar29.la2ca.ip.att.net [12.122.129.241]
9 12.122.251.190
10 206.16.68.46
11 * * *
Computing statistics for 250 seconds...Tracing route to 12.129
.209.68 over a maximum of 30 hops
0 Midnight-PC.home [192.168.1.21]
1 192.168.1.1
2 L100.LSANCA-VFTTP-54.verizon-gni.net [96.251.184.1]
3 P0-2-0-2.LSANCA-LCR-21.verizon-gni.net [130.81.60.108]
4 so-4-1-0-0.LAX01-BB-RTR1.verizon-gni.net [130.81.151.246]
5 0.xe-3-0-0.BR3.LAX15.ALTER.NET [152.63.114.241]
6 192.205.35.161
7 cr2.la2ca.ip.att.net [12.123.30.134]
8 gar29.la2ca.ip.att.net [12.122.129.241]
9 12.122.251.190
10 206.16.68.46
11 * * *
>Computing statistics for 250 seconds...


Player Location: Antelope Valley, CA
Battlegroup: Bloodlust
Latency: 11 ms HOME, 9 ms WORLD
90 Pandaren Monk
10280

C:\>pathping 12.129.254.248

Tracing route to 12.129.254.248 over a maximum of 30 hops

0 Euphy-PC.home [192.168.1.5]
1 Wireless_Broadband_Router.home [192.168.1.1]
2 L100.BLTMMD-VFTTP-32.verizon-gni.net [96.234.147.1]
3 G0-5-0-3.BLTMMD-LCR-21.verizon-gni.net [130.81.97.122]
4 so-1-1-0-0.RES-BB-RTR1.verizon-gni.net [130.81.199.2]
5 0.xe-3-1-0.BR1.IAD8.ALTER.NET [152.63.37.61]
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 mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250]
15 * * *
Computing statistics for 350 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Euphy-PC.home [192.168.1.5]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% Wireless_Broadband_Router.home [19
2.168.1.1]
0/ 100 = 0% |
2 12ms 0/ 100 = 0% 0/ 100 = 0% L100.BLTMMD-VFTTP-32.verizon-gni.n
et [96.234.147.1]
0/ 100 = 0% |
3 7ms 0/ 100 = 0% 0/ 100 = 0% G0-5-0-3.BLTMMD-LCR-21.verizon-gni
.net [130.81.97.122]
0/ 100 = 0% |
4 12ms 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 16ms 0/ 100 = 0% 0/ 100 = 0% 0.xe-3-1-0.BR1.IAD8.ALTER.NET [152
.63.37.61]
0/ 100 = 0% |
6 16ms 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.25
0]
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% mdf001c7613r0004-gig-10-1.lax1.att
ens.net [12.129.193.250]

Trace complete.

C:\>tracert 12.129.254.248

Tracing route to 12.129.254.248 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-32.verizon-gni.net [96.234.147
.1]
3 8 ms 6 ms 8 ms G0-5-0-3.BLTMMD-LCR-21.verizon-gni.net [130.81.9
7.122]
4 7 ms 9 ms 6 ms so-1-1-0-0.RES-BB-RTR1.verizon-gni.net [130.81.1
99.2]
5 13 ms 12 ms 9 ms 0.xe-3-1-0.BR1.IAD8.ALTER.NET [152.63.37.61]
6 10 ms 10 ms 13 ms 192.205.36.141
7 91 ms 90 ms 91 ms cr2.wswdc.ip.att.net [12.122.81.250]
8 94 ms 90 ms 93 ms cr1.cgcil.ip.att.net [12.122.18.21]
9 95 ms 91 ms 93 ms cr2.dvmco.ip.att.net [12.122.31.85]
10 91 ms 94 ms 92 ms cr1.slkut.ip.att.net [12.122.30.25]
11 91 ms 91 ms 91 ms cr2.la2ca.ip.att.net [12.122.30.30]
12 90 ms 97 ms 91 ms gar29.la2ca.ip.att.net [12.122.129.241]
13 89 ms 86 ms 89 ms 12-122-254-238.attens.net [12.122.254.238]
14 90 ms 90 ms 86 ms mdf001c7613r0004-gig-10-1.lax1.attens.net [12.12
9.193.250]
15 * ^C
C:\>


Still not right. Hover at 90 ping and constantly get lag spike. Wouldn't be bad if I just stayed at 90. Would be better if it went back to 40 where it started before this whole mess, but I doubt that will happen...ever. 192.205.36.141 seems to be where this sewer line starts. Maybe start your investigation there.

Verizon Fios
Drak'thul
Pasadena, MD
Still have 35 ping to Arthas
90 Tauren Death Knight
5670
i hate to be the guy to ask this but is anything being fixed anytime soon? or is it already fixed and my pc is just messed up, i usually run 80fps with 70-90ms.. now my fps is the same but my latency is over 7k. posted my tracert stuff earlier.. just curious on any info on this getting resolved
100 Human Warrior
14420
Same issue already starting @ 7:00pm EST. I'm seeing around 200 latency world and starting to have intermittent lag spikes causing characters to freeze about every 30 seconds.
90 Night Elf Druid
10350
This problem hasn't be resolved. Worked fine all last week and back to the lag spikes, freezes and disconnects. Assuming this is a Verizon issue, their customer service is garbage. A tracert for what that's worth:

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 5 ms 4 ms 4 ms 74.101.107.1
3 5 ms 24 ms 4 ms G0-11-3-0.NYCMNY-LCR-22.verizon-gni.net [130.81.133.6]
4 * 7 ms 12 ms so-3-1-0-0.NY5030-BB-RTR1.verizon-gni.net [130.81.151.234]
5 * * * Request timed out.
6 76 ms 92 ms 90 ms 192.205.36.57
7 89 ms 89 ms 89 ms cr2.n54ny.ip.att.net [12.122.86.10]
8 86 ms * * cr2.wswdc.ip.att.net [12.122.3.38]
9 93 ms 92 ms * cr1.attga.ip.att.net [12.122.1.173]
10 91 ms 91 ms 91 ms cr2.dlstx.ip.att.net [12.122.28.174]
11 * 79 ms 79 ms cr1.dlstx.ip.att.net [12.122.1.209]
12 89 ms * 88 ms cr1.phmaz.ip.att.net [12.122.28.182]
13 * 77 ms * 12.123.206.157
14 92 ms 92 ms 92 ms 12-122-254-50.attens.net [12.122.254.50]
15 247 ms 209 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 *
91 Night Elf Mage
6180
Hi,
I am from Proudmoore
Living in Keller, Texas
For 3 weeks now I have had very high latency off and on, suddenly spiking into the thousands and tens of thousands of ms latency. Today especially has been the worse, starting at noon today I have been only been able to get a stable connection to Blizzard for maybe 15 minutes at a time (this includes the game AND the website). I have been through this over and over with Verizon and all they will do is replace the router over and over.

Note: My aunt lives nearby and also has Verizon Fios, I went to her house and have the exact same issue, on multiple computers.

Traceroute has started…

traceroute to us.battle.net (12.129.242.40), 64 hops max, 72 byte packets
1 192.168.1.1 (192.168.1.1) 1.671 ms 1.158 ms 1.161 ms
2 l100.dllstx-vfttp-69.verizon-gni.net (96.226.221.1) 7.828 ms 7.155 ms 7.844 ms
3 g0-5-1-2.dllstx-lcr-21.verizon-gni.net (130.81.215.202) 7.710 ms 8.814 ms 10.301 ms
4 so-5-0-0-0.dfw9-bb-rtr1.verizon-gni.net (130.81.199.34) 9.745 ms 7.698 ms 9.926 ms
5 0.xe-3-1-2.br1.dfw13.alter.net (152.63.98.73) 9.999 ms 9.674 ms 10.003 ms
6 192.205.37.125 (192.205.37.125) 10.032 ms 12.013 ms 9.646 ms
7 cr2.dlstx.ip.att.net (12.122.212.14) 42.575 ms 42.479 ms 45.222 ms
8 cr2.la2ca.ip.att.net (12.122.28.178) 42.590 ms 46.569 ms 45.511 ms
9 gar29.la2ca.ip.att.net (12.122.129.241) 41.939 ms 42.643 ms 169.398 ms
10 12.122.251.190 (12.122.251.190) 43.302 ms
12-122-254-234.attens.net (12.122.254.234) 48.284 ms
12.122.251.190 (12.122.251.190) 45.953 ms
11 206.16.68.46 (206.16.68.46) 43.796 ms 42.305 ms 42.293 ms
12 * * *
13 * * *
14 * * *
Edited by Pällas on 2/27/2013 6:08 PM PST
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)

Reported!

[Close]