dslreports logo
 
    All Forums Hot Topics Gallery
spc
Search similar:


uniqs
1903
Ainshi
join:2002-07-09
Woodstock, IL

Ainshi

Member

Gaming and U-verse

Got U-verse here in Northern Illinois (Woodstock), and going in I knew that gaming would be an issue. But as I found out, it only seems to be particularly affecting World of Warcraft, and only sporadically. Yes, my issue is the latency. I know there's the thread in Direct about latency tracking and whatnot, but since I can't actually read Direct I want to know if anybody has ever really had this issue fixed. It's not a deal breaker, but more an annoyance.
I would be more willing to chalk it up to just the way the service is, except for the fact that my 3rd hop on a traceroute to Blizzard's Login Server is always timed out - and sometimes that spills over to the 4th hop. The rest of the hops look reasonable for the distance (cross-country). In-game the problem manifests itself as not so much a high latency, but visual and command lag. I suppose in the end i'm just curious if this is the normal experience of players with U-verse, or if this is a more correctable issue.

Traceroute:

1 1 ms 1 ms 1 ms home [192.168.1.254]
2 24 ms 22 ms 23 ms 76-234-40-2.lightspeed.cicril.sbcglobal.net [76.
234.40.2]
3 24 ms 23 ms 25 ms 71.145.96.8
4 * * * Request timed out.
5 24 ms 23 ms 24 ms 71.145.64.58
6 23 ms 23 ms 23 ms bb1-g3-0.chcgil.sbcglobal.net [151.164.43.204]
7 23 ms 23 ms 23 ms ex2-p1-0.eqchil.sbcglobal.net [151.164.189.80]
8 23 ms 23 ms 23 ms gar8.cgcil.ip.att.net [12.122.79.85]
9 72 ms 71 ms 72 ms tbr1.cgcil.ip.att.net [12.122.99.6]
10 72 ms 72 ms 72 ms cr1.cgcil.ip.att.net [12.122.17.129]
11 72 ms 71 ms 72 ms cr2.dvmco.ip.att.net [12.122.31.85]
12 71 ms 72 ms 71 ms cr1.slkut.ip.att.net [12.122.30.25]
13 72 ms 72 ms 71 ms cr2.la2ca.ip.att.net [12.122.30.30]
14 72 ms 72 ms 72 ms tbr2.la2ca.ip.att.net [12.122.19.230]
15 71 ms 71 ms 71 ms 12.127.3.189
16 72 ms 71 ms 71 ms 12.122.255.74
17 72 ms 72 ms 72 ms mdf001c7613r0004-gig-12-1.lax1.attens.net [12.12
9.193.246]
18 72 ms 72 ms 72 ms 12.129.209.74
19 72 ms 72 ms 72 ms 12.129.232.112

gdm
MVM
join:2001-06-15
Mchenry, IL

gdm

MVM

Ignore the time out that's just some thing on att's end and is normal on U-Verse or DSL.

This is from my U-Verse line to that IP.

Tracing route to 12.129.232.112 over a maximum of 30 hops

1 1 ms 1 ms 1 ms home [192.168.1.254]
2 25 ms 22 ms 22 ms 76-245-0-2.lightspeed.cicril.sbcglobal.net [76.245.0.2]
3 26 ms 28 ms 23 ms 71.145.96.8
4 * * * Request timed out.
5 * * * Request timed out.
6 25 ms 24 ms 23 ms bb1-g3-0.chcgil.sbcglobal.net [151.164.43.204]
7 25 ms 23 ms 23 ms ex2-p1-1.eqchil.sbcglobal.net [151.164.189.82]
8 26 ms 25 ms 24 ms gar8.cgcil.ip.att.net [12.122.79.89]
9 73 ms 74 ms 72 ms tbr1.cgcil.ip.att.net [12.122.85.98]
10 73 ms 71 ms 71 ms cr1.cgcil.ip.att.net [12.122.17.129]
11 74 ms 71 ms 71 ms cr2.dvmco.ip.att.net [12.122.31.85]
12 74 ms 71 ms 72 ms cr1.slkut.ip.att.net [12.122.30.25]
13 73 ms 71 ms 72 ms cr2.la2ca.ip.att.net [12.122.30.30]
14 74 ms 72 ms 72 ms tbr2.la2ca.ip.att.net [12.122.19.214]
15 71 ms 75 ms 71 ms 12.127.3.189
16 73 ms 71 ms 71 ms 12.122.255.74
17 74 ms 72 ms 72 ms mdf001c7613r0004-gig-12-1.lax1.attens.net [12.12
9.193.246]
18 73 ms 72 ms 72 ms 12.129.209.74
19 74 ms 72 ms 73 ms 12.129.232.112

Trace complete.
Ainshi
join:2002-07-09
Woodstock, IL

Ainshi

Member

I don't know if I should be happy or upset that someone can confirm the traceroute! At least it's good to know that whatever latency i'm experiencing is systemic, so I wont worry about what I may or may not be able to harass AT&T into doing about. It's not so bad, so I can live with it. Thanks and greetings from 10 miles away!

gdm
MVM
join:2001-06-15
Mchenry, IL

gdm

MVM

The latency isn't that bad. It's really adding about 10ms at most from my comcast line.

Heavy end gamers say it's to much latency and they go back to DSL. Others say it's fine and host games so I guess you can take it with grain assault.

According to your profile you aren't 10 miles away .
Ainshi
join:2002-07-09
Woodstock, IL

Ainshi

Member

Things can change in seven years!

djrobx
Premium Member
join:2000-05-31
Reno, NV

djrobx to Ainshi

Premium Member

to Ainshi
I don't think there's anything to fix on that trace. Given VDSL's interleave "tax", 72ms seems very reasonable for Chicago to Los Angeles.

apeface
join:2000-09-16
Mckinney, TX

apeface to Ainshi

Member

to Ainshi
Looks fine to me, if there was something to fix there, I would.

ILpt4U
Premium Member
join:2006-11-12
Saint Louis, MO

ILpt4U

Premium Member

When I get back home, I'll do a trace from Crystal Lake on my U-Verse Internet for comparison's sake. But it should look about the same as Woodstock and McHenry.

Deckoh
Premium Member
join:2002-07-24
Chesapeake, VA

Deckoh to Ainshi

Premium Member

to Ainshi
Click for full size
mines a lot lower in san diego.

ILpt4U
Premium Member
join:2006-11-12
Saint Louis, MO

ILpt4U

Premium Member

I would hope the ping is lower from San Diego to LA than Chicago to LA -- just a little shorter distance...

tlylework
@sbcglobal.net

tlylework to Ainshi

Anon

to Ainshi
I play a lot of COD4 and CS:Source. I can confirm my pings on average are 15-20ms higher than they were with straight up AT&T DSL, but my gaming seems more fluid.

Before with source, even though I would be pinging 20ms, I would get choke sporadically. I don't seem to get much choke anymore.. Only going on my second week with Uverse, but so far no problems with anything.

Wish me luck!!

Deckoh
Premium Member
join:2002-07-24
Chesapeake, VA

Deckoh to ILpt4U

Premium Member

to ILpt4U
ooops.
mr_baldeagle
join:2003-04-26
Tomball, TX

mr_baldeagle to Ainshi

Member

to Ainshi
We (the kids and I) play WOW and no issues at all 3 cpu's. Only thing I noticed is about 8ms more on my end; average ping from us to our server 32-40ms. We have a few other Shooter games the kids and their friends play and have not had one issue at all with Uverse like some folks mention. All and all VERY VERY happy with it.
Learux
join:2001-10-23
Valencia, CA

Learux to Ainshi

Member

to Ainshi
When U-verse came out I had serious issues, now I have good(not great) pings to most servers. I am getting older and don't care that much anymore.

I can usually find servers that will ping 45ms, good enough for me.

I love my U-verse.

Learux

septcasey
join:2006-09-07
United State

septcasey

Member

Be lucky you're not like me and stuck on dial up still for almost 10 years now. Don't become spoiled. There is absolutely nothing you should be complaining about with those test results. I play in the 400-700MS latency all the time in WoW. Remember that in WoW the latency bar you have will always stay green up to 299 MS. If it goes to 300 MS or more it will go yellow then red if it goes 600 MS or more. If you are 299 MS or below at all times, you will never have problems with latency or lag in WoW.
vulpine
join:2003-03-28
Willoughby, OH

1 edit

vulpine to Ainshi

Member

to Ainshi
You'll want to be more concerned about the realm server IP doing the trace to, not the logon server. Check these wikis although I dont know how accurate they are.
»www.egn.com.au/wiki/WoW_ ··· ddresses

»www.wowwiki.com/US_realm ··· tacenter

Another way to check your server ip is to completely log in to your character then do a netstat and check your connections, connection port would be 3794 i believe.

I'm downloading the new patch right now otherwise I would post my trace stats on non-uverse dsl.

is uverse seriously interleave? Thats disheartening, I imagine I would appreciate the extra data precautions and checks it gives if i actually watched tv but I dealt with interleave in columbus and hated it. is it true that i heard once you go uverse and decide to go back to dsl you would still be on interleave?

ILpt4U
Premium Member
join:2006-11-12
Saint Louis, MO
ARRIS TM822
Asus RT-N66

ILpt4U

Premium Member

said by ILpt4U:

When I get back home, I'll do a trace from Crystal Lake on my U-Verse Internet for comparison's sake. But it should look about the same as Woodstock and McHenry.
Well, I'm back...
So here is that trace:
Tracing route to 12.129.232.112 over a maximum of 30 hops

1 4 ms 1 ms 1 ms 192.168.1.254
2 24 ms 21 ms 21 ms 99-189-132-2.lightspeed.cicril.sbcglobal.net [99
.189.132.2]
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 22 ms 24 ms 23 ms bb1-g3-0.chcgil.sbcglobal.net [151.164.43.204]
7 26 ms 23 ms 25 ms ex2-p1-1.eqchil.sbcglobal.net [151.164.189.82]
8 23 ms 25 ms 25 ms gar8.cgcil.ip.att.net [12.122.79.89]
9 73 ms 72 ms 74 ms tbr1.cgcil.ip.att.net [12.122.85.98]
10 72 ms 73 ms 72 ms cr1.cgcil.ip.att.net [12.122.17.129]
11 72 ms 71 ms 71 ms cr2.dvmco.ip.att.net [12.122.31.85]
12 71 ms 74 ms 72 ms cr1.slkut.ip.att.net [12.122.30.25]
13 72 ms 71 ms 72 ms cr2.la2ca.ip.att.net [12.122.30.30]
14 71 ms 73 ms 71 ms 12.122.129.5
15 73 ms 72 ms 72 ms 12-122-254-66.attens.net [12.122.254.66]
16 73 ms 72 ms 72 ms mdf001c7613r0003-gig-10-1.lax1.attens.net [12.12
9.193.242]
17 71 ms 74 ms 72 ms 12.129.209.74
18 72 ms 72 ms 74 ms 12.129.232.112
Vtr_Racing
join:2006-09-04
Pflugerville, TX

Vtr_Racing to Ainshi

Member

to Ainshi
Your not the only one who has noticed this with UVERSE/VDSL. I think, serious gaming, is not for UVERSE. Here is a thread I posted. Mine is a lot more stable than it was but Im going to switch or add a second line if I can. Here is the link.
»ATT Uverse gaming and High pings

If gaming is your thing, I would avoid this but if TV and cool features are more your thing. Uverse is very good. I like it for that. Better than my cable service.