| [Connectivity] Lag in WOW - Jacksonville Everytime I do it I seem to get some sort of spike in Atlanta. This is causing bad lag and ping spikes in WOW.
Tracing route to 12.129.206.130 over a maximum of 30 hops
1 29 ms 20 ms 51 ms c-67-190-248-1.hsd1.fl.comcast.net [67.190.248.1
]
2 10 ms 9 ms 8 ms te-9-2-ur01.stjohns.fl.jacksvil.comcast.net [68.
85.94.21]
3 15 ms 11 ms 11 ms 69.139.222.197
4 21 ms 55 ms 23 ms pos-0-4-0-0-cr01.charlotte.nc.ibone.comcast.net
[68.86.91.81]
5 25 ms 27 ms 27 ms pos-3-8-0-0-cr01.56marietta.ga.ibone.comcast.net
[68.86.89.21]
6 31 ms 25 ms 27 ms pos-0-1-0-0-pe01.56marietta.ga.ibone.comcast.net
[68.86.86.86]
7 1275 ms 24 ms 29 ms as7018-pe01.56marietta.ga.ibone.comcast.net [75.
149.228.86]
8 77 ms 78 ms 92 ms cr1.attga.ip.att.net [12.122.141.182]
9 80 ms 75 ms 79 ms cr2.dlstx.ip.att.net [12.122.28.174]
10 89 ms 76 ms 75 ms cr2.la2ca.ip.att.net [12.122.28.178]
11 89 ms 99 ms 74 ms gar29.la2ca.ip.att.net [12.122.129.241]
12 75 ms 75 ms 74 ms 12-122-254-238.attens.net [12.122.254.238]
13 76 ms 74 ms 74 ms mdf001c7613r0004-gig-10-1.lax1.attens.net [12.12
9.193.250]
14 * * * Request timed out.
15 ^C |
|
| Without getting into the finer points of this, that hop is part of AT&T's network. Ergo, Comcast is completely in the clear. |
|
 Tobin
join:2003-09-21
Burlingame, CA | reply to JWJAX
The last hop to WoW 'realm' IPs always times out. It has no particular bearing on your lag spikes. |
|
|
|
Reviews:
 ·Comcast
 ·AT&T U-Verse
| Tracing route to 12.129.206.130 over a maximum of 30 hops
1 * * * Request timed out.
2 8 ms 7 ms 7 ms -------------
3 13 ms 11 ms 11 ms be-52-ar01.chartford.ct.hartford.comcast.net [68.85.162.194]
4 17 ms 15 ms 15 ms pos-1-5-0-0-ar01.needham.ma.boston.comcast.net [68.85.162.73]
5 26 ms 23 ms 23 ms he-2-7-0-0-cr01.newyork.ny.ibone.comcast.net [68.86.95.29]
6 20 ms 31 ms 21 ms pos-0-0-0-0-pe01.111eighthave.ny.ibone.comcast.net [68.86.87.122]
7 21 ms 23 ms 23 ms 192.205.37.33
8 102 ms 103 ms 99 ms cr1.n54ny.ip.att.net [12.122.131.86]
9 102 ms 103 ms 103 ms cr2.cgcil.ip.att.net [12.122.1.2]
10 101 ms 103 ms 105 ms cr1.cgcil.ip.att.net [12.122.2.53]
11 102 ms 103 ms 105 ms cr2.dvmco.ip.att.net [12.122.31.85]
12 103 ms 103 ms 103 ms cr1.slkut.ip.att.net [12.122.30.25]
13 104 ms 103 ms 104 ms cr2.la2ca.ip.att.net [12.122.30.30]
14 100 ms 100 ms 100 ms gar29.la2ca.ip.att.net [12.122.129.241]
15 101 ms 101 ms 99 ms 12.122.251.190
16 100 ms 101 ms 106 ms 206.16.68.46
17 * * * Request timed out.
This is what I get. Your ping is normal since you're trying to tracert to a server in CA. Like stated above, Blizzard servers give a time out when you hit it. |
|
 EGThe wings of lovePremium
join:2006-11-18
Union, NJ
kudos:9 | reply to JWJAX
said by JWJAX :Everytime I do it I seem to get some sort of spike in Atlanta.
FWIW, that is not a lag spike. The reason for the increase at the interconnect point between Comcast and AT&T is because AT&T uses MPLS tunneling. This is known as being the "MPLS cloud". We are actually looking at the other end of the interface at this hop and since it is a coast to coast trace, the response time is normal. 100ms or less is good.
In addition, that server is firewalled / configured to not respond to ICMP packet based traceroute probes, hence the complete timeout there. |
|
| reply to JWJAX
I online playing wow now I in jacksonville no lag and i use comcast. |
|
 tshirtPremium,MVM
join:2004-07-11
Snohomish, WA
kudos:3 | Kara could you post a trace route? it would be interesting to see if you get a different server/path, or just find that latentcy acceptable.
An awful lot of people blame the network for "LAG" when the fault lies elsewhere. |
|
1 edit | reply to JWJAX
What latency are you seeing in-game? 90 ms should play fine. Another option is to transfer to a realm located closer to you (see this list). My realm is located in LA, and I usually get around 31 ms in-game. When there are problems, I don't usually notice it until it's 180+.
Edit: Here's a traceroute to my realm (Silver Hand) for the heck of it:
Tracing route to 12.129.254.196 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms DD-WRT [192.168.0.254]
2 37 ms 21 ms 26 ms 67.180.40.1
3 26 ms 9 ms 8 ms te-3-2-sr01.ukiah.ca.sfba.comcast.net [68.86.249.21]
4 10 ms 11 ms 11 ms te-8-1-ur06.rohnertpr.ca.sfba.comcast.net [68.87.226.229]
5 15 ms 15 ms 15 ms te-0-1-0-7-ar01.oakland.ca.sfba.comcast.net [68.87.192.162]
6 19 ms 16 ms 15 ms be-90-ar01.sfsutro.ca.sfba.comcast.net [68.85.155.14]
7 23 ms 23 ms 23 ms he-3-9-0-0-cr01.sanjose.ca.ibone.comcast.net [68.86.91.45]
8 22 ms 55 ms 23 ms pos-0-9-0-0-pe01.11greatoaks.ca.ibone.comcast.net [68.86.88.110]
9 93 ms 25 ms 20 ms 192.205.37.1
10 29 ms 31 ms 29 ms cr1.sffca.ip.att.net [12.122.86.198]
11 27 ms 31 ms 43 ms cr1.la2ca.ip.att.net [12.122.3.122]
12 40 ms 33 ms 28 ms gar20.la2ca.ip.att.net [12.122.128.181]
13 30 ms 36 ms 28 ms 12.122.251.190
14 34 ms 34 ms 32 ms mdf001c7613r0003-gig-12-1.lax1.attens.net [12.129.193.254]
15 * * * Request timed out.
You can see it reaching AT&T's MPLS network on hop 10, and the consistent pings from 10-14. That's what EG  is referring to.
--
KI6RIT |
|
| Don't forget guys, you're pinging the wow login server and n_w95482 pinged a server which is located in CA. 80ish latency is expected from Florida to CA. |
|
Tobin
join:2003-09-21
Burlingame, CA | reply to n_w95482
said by n_w95482:What latency are you seeing in-game? 90 ms should play fine. Another option is to transfer to a realm located closer to you (see this list). My realm is located in LA, and I usually get around 31 ms in-game. When there are problems, I don't usually notice it until it's 180+. Yes, WoW has high lag tolerance for certain things like spell queuing, but it's worse for other phenomenon like trying not to stand in fire. I was able to raid perfectly fine using tether.com's proxy through my iPhone 5 when my Comcast connection recently hiccuped. Despite having 250ms latency, I was able to play without any noticeable difficulty. |
|
| reply to JWJAX
I've had the same problem with WoW off and on for months. I have possible hardware issues not helping some of my DC issues, but this is not a comcast only deal, but a blizz/ATT deal on their end. I'm too lazy to find the threads on the wow CS forums but they're there. Many complaints of the same lag spikes across north america and different ISPs.
Some nights its intolerable and unplayable in a raid. Thankfully thats been rare for the last 4-5 months for me. I usually have a sub 100ms connection from Oregon to the Chicago based servers but it will randomly lag spike for 10-30s. Some nights it will just hit "red" lag and stay there for 30-45mins or bump back and forth. |
|
