For all the Comcast users.

[Orin]

http://forums.worldofwarcraft.com/thread.html?topicId=13129890126

Please assist by running the tracert command and email Blizzard your results. Any additional information we can provide should help Blizzard put pressure on Comcast and AT&T to resolve these network latency issues.


tracert 63.241.255.32

(IP may change if Blizzard does maintenance, follow their instructions to ensure you have the proper address)

[Vilmah]

Yessir.

[Svetlaena]

Thanks-- and here I thought I just had a crappy router. :D

[Yichimet]

I was wondering why my ping was so bad on Monday. Will do this tonight, thanks.

[Raziel]

Comcast is installing Fiber Optic Cables in Whidbey Island this month.

woot

I like this thread. People are posting their tracerts with their IP addresses in a public forum. That's awesome.

[Taknar]

I like this thread. People are posting their tracerts with their IP addresses in a public forum. That's awesome.

*spittake* You're joking. Please tell me you're joking.

[opalexian]

Comcast is installing Fiber Optic Cables in Whidbey Island this month.

woot

I like this thread. People are posting their tracerts with their IP addresses in a public forum. That's awesome.

Uh, I think that's TN's IP. l2r ; b

[Nadea]

Ooooh, so its Comcast giving me latency hell as of late...monday was horrendus X.x

[Malethia]

Since I don't want to read through a billion posts of people bitching...what are they saying about At&t's involvement in the problem? I was having a issue Monday night where my latency got so bad I couldn't stay connected to the server, and I assume it has something to do with all of this.

[Kelven]

We don't have Comcast up here in the frigid north, but this reminds me of a story. I was raiding with some local friends one day a few years ago, when suddenly our connections got slaughtered - outright disconnections, or lag up above 15000ms eventually leading to a disconnect.

Our network tech friend followed the breadcrumbs from here to WoW and found out that some network-backbone provider had misconfigured their routers, and were routing all east-west traffic from our city through a tiny five-port Linksys router on a desk in Texas. The router was gamely trying to keep up with tens of thousands of simultaneous connections but it was kind of a losing game.

He phoned them up and explained the problem, and got a rude rebuff. About an hour later the problem mysteriously cleared up. Possibly the Linksys router caught fire and thye were forced to acknowledge that something might be wrong.

[Raziel]

Uh, I think that's TN's IP. l2r ; b

Not all of them are.

[Agnarr]

Uh, I think that's TN's IP. l2r ; b
Tracerts display the IP of where it starts (the person's home public IP address) and where it goes (the destination, or in this case WoW server) IP address, along with every hop in between.

l2internet? :p

[Karkarov]

Hell yeah consider it done, again...

*manly arm pump*

[Karkarov]

To clear up the dumbness of these posts enheilras is referencing the wow thread not this one. The ip at the top of this thread is the ip of twisting nether.

[Orin]

Ooooh, so its Comcast giving me latency hell as of late...monday was horrendus X.x


It actually is the AT&T network after Comcast hands off the traffic. Either way, we're screwed. :(

[Rhowen-Prea]

OH so it's -COMCAST- that's been the problem. My days of saying, "Geez, guys, I dunno, Comcast has never given me any trouble" are over.

[Lisbet]

Heid and I have -always- had issues with comcast and wow. Its gotten better in the last year or so, but monday was so bad we both had to drop raid, as well as cdub and his two roommates, and at least two other people. ;/

[Swerto]

On the 11th hop it starts using ATT servers for hopping.
19 and up it times out.

Hmmm...


Not having any in game issues, but I am having trouble connecting to the Yahoo main page -shrug-

I've already got my dad (Who is a private contractor for comcast) to call them and find out if it's on their end.

Internet's free, I'm not going to bitch.

[Selash]

I use Embark at home and CableONE up at school, and I find that CableONE usually isn't too bad with latency. The only time my connection starts to choke is when I was in Shattrath (before Wrath) or in Dalaran, and there it's pretty obvious as to why my connection was choking a bit.

Either way, I think this is a good idea, assuming Blizzard actually is purporting this idea.

[Dewce]

I have Comcast and I don't have any issues. I mean my latency can hit the upper 100s, but it is totally playable. As far as Comcast traffic taking a shit when it hits AT&T's network, sounds like AT&T is providing horrible QoS for Comcast traffic, possibly to sway them to another, more capable, ISP (AT&T)?