- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I've been experiencing severe delays in response time recently (mostly over the last week or so) every few minutes which seem to last several seconds. This is mostly noticeable while playing online games (especially World of Warcraft) but also occasionally while just browsing the web. I've tried rebooting my modem and my router, neither seems to solve the problem.
I started by contacting technical support on Blizzard's forums, and this is what they said:
You seem to have some dropped data, which is occurring in hop 4, or it may be asked, hard to tell right now.
But it seems like there is a jump in ms when it gets handed off from Verizon a peering partner, and may be causing the issue. You may want to contact your ISP and ask them about that, since it happens before us.
We are also investigating reports of latency issues like this with Verizon and players in your area. We have a sticky thread here in the Tech forums, that you will want to post, so that we can get more examples and investigate this further as well. That would help us.
I've included a traceroute as well, hopefully that will help:
64 * * *
Traceroute has started…
traceroute to us.logon.battle.net (12.129.206.130), 64 hops max, 72 byte packets
1 wireless_broadband_router (192.168.1.1) 188.893 ms 0.837 ms 1.815 ms
2 l100.bstnma-vfttp-132.verizon-gni.net (98.118.103.1) 37.982 ms 16.070 ms 6.885 ms
3 g0-5-4-6.bstnma-lcr-22.verizon-gni.net (130.81.183.94) 7.777 ms 5.897 ms 7.452 ms
4 * * *
5 ge-1-2-0-0.ny325-bb-rtr2.verizon-gni.net (130.81.17.24) 19.976 ms 18.239 ms 35.981 ms
6 192.205.36.57 (192.205.36.57) 19.470 ms 18.526 ms 17.018 ms
7 cr1.n54ny.ip.att.net (12.122.86.6) 94.582 ms 96.442 ms 102.697 ms
8 cr2.cgcil.ip.att.net (12.122.1.2) 99.737 ms 100.391 ms 97.778 ms
9 cr1.cgcil.ip.att.net (12.122.2.53) 103.210 ms 99.671 ms 93.815 ms
10 cr2.dvmco.ip.att.net (12.122.31.85) 94.303 ms 94.819 ms 94.950 ms
11 cr1.slkut.ip.att.net (12.122.30.25) 103.396 ms 96.528 ms 91.606 ms
12 cr2.la2ca.ip.att.net (12.122.30.30) 96.116 ms 95.607 ms 98.718 ms
13 gar4.lsrca.ip.att.net (12.122.104.89) 94.559 ms 102.401 ms 93.560 ms
14 12-122-254-226.attens.net (12.122.254.226) 93.059 ms
12-122-254-230.attens.net (12.122.254.230) 96.316 ms
12-122-254-226.attens.net (12.122.254.226) 211.630 ms
15 mdf001c7613r0004-gig-12-1.lax1.attens.net (12.129.193.246) 92.562 ms 91.834 ms 91.939 ms
16 12.129.211.38 (12.129.211.38) 97.082 ms !X * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 12.129.211.38 (12.129.211.38) 106.234 ms !X * *
25 * * *
26 * 12.129.211.38 (12.129.211.38) 92.244 ms !X *
27 * * *
28 12.129.211.38 (12.129.211.38) 96.061 ms !X * *
29 * * *
30 * 12.129.211.38 (12.129.211.38) 98.671 ms !X *
31 * * *
32 12.129.211.38 (12.129.211.38) 103.054 ms !X * *
33 * * *
34 * * 12.129.211.38 (12.129.211.38) 94.519 ms !X
35 * * *
36 * 12.129.211.38 (12.129.211.38) 116.739 ms !X *
37 * * *
38 * * *
39 12.129.211.38 (12.129.211.38) 95.823 ms !X * *
40 * * 12.129.211.38 (12.129.211.38) 92.627 ms !X
41 * * *
42 * * 12.129.211.38 (12.129.211.38) 399.917 ms !X
43 * * *
44 * * *
45 * * *
46 * * *
47 * * *
48 * * *
49 * * *
50 * 12.129.211.38 (12.129.211.38) 97.657 ms !X *
51 * * *
52 * * 12.129.211.38 (12.129.211.38) 99.736 ms !X
53 * * *
54 * * *
55 * 12.129.211.38 (12.129.211.38) 94.350 ms !X *
56 * * *
57 * * 12.129.211.38 (12.129.211.38) 98.030 ms !X
58 * * *
59 * * *
60 * 12.129.211.38 (12.129.211.38) 100.276 ms !X *
61 * * *
62 * * *
63 12.129.211.38 (12.129.211.38) 95.120 ms !X * *
64 * * *
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Looking at the traceroute the latency looks to be starting after your data leaves the Verizon network. In particular note on and after hop 7. Unfortunately as far as administration goes, we do not have control over non Verizon routers.
7 cr1.n54ny.ip.att.net (12.122.86.6) 94.582 ms 96.442 ms 102.697 ms
8 cr2.cgcil.ip.att.net (12.122.1.2) 99.737 ms 100.391 ms 97.778 ms
9 cr1.cgcil.ip.att.net (12.122.2.53) 103.210 ms 99.671 ms 93.815 ms
10 cr2.dvmco.ip.att.net (12.122.31.85) 94.303 ms 94.819 ms 94.950 ms
11 cr1.slkut.ip.att.net (12.122.30.25) 103.396 ms 96.528 ms 91.606 ms
12 cr2.la2ca.ip.att.net (12.122.30.30) 96.116 ms 95.607 ms 98.718 ms
13 gar4.lsrca.ip.att.net (12.122.104.89) 94.559 ms 102.401 ms 93.560 ms
14 12-122-254-226.attens.net (12.122.254.226) 93.059 ms
12-122-254-230.attens.net (12.122.254.230) 96.316 ms
12-122-254-226.attens.net (12.122.254.226) 211.630 ms
15 mdf001c7613r0004-gig-12-1.lax1.attens.net (12.129.193.246) 92.562 ms 91.834 ms 91.939 ms
Lee_VZ
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
AT&T tends to have a funny naming system for their routers, that or they have not been updating those names, but I can tell you right off the bat the network once on AT&T shoots directly from New York to California, looks to be Los Angeles. It's impossible for the latency to start off at 90ms in New York and make it to California without a single twitch of latency (besides jitter-related variances). The latency on hops 2 and 4 is elevated and inconsistent, though it's hard to determine if that is just from someone spiking data across your line in your home since the initial latency to your router was also rediculous, or if those two Verizon routers were not prioritizing traceroute traffic. Boston to New York should be no more than a 6ms jump, since it is a short distance as technically you can go from the East Coast to the West Coast and back in no more than 70ms on some nice routes.
Here's a traceroute from my DSL connection. Notice the 10ms link between my area's core router and New York City. The latency across that path shouldn't even be that high, but I guess I'm stuck with it since ALL of my area's traffic travels down that path.
Tracing route to us.logon.battle.net [12.129.206.130]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.3.1
2 10 ms 9 ms 8 ms 10.15.3.1
3 10 ms 10 ms 9 ms so-1-1-0-0.BUFF-CORE-RTR2.verizon-gni.net [130.81.13.77]
4 19 ms 20 ms 20 ms as4-0.NY5030-BB-RTR1.verizon-gni.net [130.81.20.106]
5 20 ms 21 ms 20 ms 0.ae5.BR2.NYC4.ALTER.NET [152.63.18.29]
6 21 ms 21 ms 20 ms 192.205.34.49
7 103 ms 104 ms 101 ms cr1.n54ny.ip.att.net [12.122.86.6]
8 102 ms 103 ms 99 ms cr2.cgcil.ip.att.net [12.122.1.2]
9 102 ms 103 ms 103 ms cr1.cgcil.ip.att.net [12.122.2.53]
10 100 ms 100 ms 100 ms cr2.dvmco.ip.att.net [12.122.31.85]
11 98 ms 99 ms 135 ms cr1.slkut.ip.att.net [12.122.30.25]
12 118 ms 100 ms 100 ms cr2.la2ca.ip.att.net [12.122.30.30]
13 117 ms 100 ms 98 ms gar4.lsrca.ip.att.net [12.122.104.89]
14 170 ms 98 ms 98 ms 12-122-254-230.attens.net [12.122.254.230]
15 99 ms 98 ms 98 ms mdf001c7613r0003-gig-10-1.lax1.attens.net [12.129.193.242]
16 12.129.211.34 reports: Destination net unreachable.
Trace complete.