dslreports logo
 
    All Forums Hot Topics Gallery
spc
Search similar:


uniqs
1376
Sylar2jz
join:2014-07-07
Belgrade, MT

Sylar2jz

Member

[Speed Issues] Terrible World of Warcraft latency

The last couple weeks I've been experiencing godawful latency when connecting to World of Warcraft. I've ran several traceroutes and pathpings to my server's IP adress and they all come up with problems around hop 13 and later. I would love to get this fixed. Charter tech support via phone has been about as helpful as I would expect. (Not at all)

Traceroute:

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 192.168.1.1
2 11 ms 7 ms 13 ms 100.68.64.1
3 8 ms 14 ms 7 ms host-72-175-111-10.bln-mt.client.bresnan.net [72.175.111.10]
4 11 ms 10 ms 12 ms 69.145.247.146
5 11 ms 10 ms 11 ms 69.144.126.8
6 37 ms 39 ms 37 ms gdjco001cr5-GE-3-0-2-U0.int.bresnan.net [72.175.110.240]
7 39 ms 40 ms 37 ms te0-0-0-12.ccr21.ord03.atlas.cogentco.com [38.104.103.117]
8 38 ms 39 ms 42 ms be2003.ccr42.ord01.atlas.cogentco.com [154.54.29.21]
9 50 ms 51 ms 50 ms be2157.ccr22.mci01.atlas.cogentco.com [154.54.6.117]
10 60 ms 71 ms 61 ms be2010.ccr22.dfw01.atlas.cogentco.com [154.54.46.218]
11 60 ms 61 ms 61 ms be2032.ccr21.dfw03.atlas.cogentco.com [154.54.6.54]
12 64 ms 67 ms 63 ms 192.205.36.221
13 169 ms 162 ms 165 ms cr1.dlstx.ip.att.net [12.122.139.18]
14 158 ms * 163 ms cr1.phmaz.ip.att.net [12.122.28.182]
15 * 150 ms 146 ms 12.123.206.165
16 203 ms * 136 ms 12-122-254-50.attens.net [12.122.254.50]
17 191 ms 191 ms 190 ms mdf002c7613r0001-gig-12-1.phx1.attens.net [63.241.130.210]

Trace complete.

__

__

Pathping:

Tracing route to mdf1-bi8k-1-ve-87.phx1.attens.net [63.241.138.161]
over a maximum of 30 hops:
0 Sylar2jz-PC [192.168.1.2]
1 192.168.1.1
2 100.68.64.1
3 host-72-175-111-10.bln-mt.client.bresnan.net [72.175.111.10]
4 69.145.247.146
5 69.144.126.8
6 gdjco001cr5-GE-3-0-2-U0.int.bresnan.net [72.175.110.240]
7 te0-0-0-12.ccr21.ord03.atlas.cogentco.com [38.104.103.117]
8 be2003.ccr42.ord01.atlas.cogentco.com [154.54.29.21]
9 be2157.ccr22.mci01.atlas.cogentco.com [154.54.6.117]
10 be2010.ccr22.dfw01.atlas.cogentco.com [154.54.46.218]
11 be2032.ccr21.dfw03.atlas.cogentco.com [154.54.6.54]
12 192.205.36.221
13 cr1.dlstx.ip.att.net [12.122.139.18]
14 cr1.phmaz.ip.att.net [12.122.28.182]
15 12.123.206.165
16 12-122-254-50.attens.net [12.122.254.50]
17 mdf002c7613r0001-gig-12-1.phx1.attens.net [63.241.130.210]
18 * * *
Computing statistics for 425 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Sylar2jz-PC [192.168.1.2]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1
0/ 100 = 0% |
2 --- 100/ 100 =100% 100/ 100 =100% 100.68.64.1
0/ 100 = 0% |
3 10ms 0/ 100 = 0% 0/ 100 = 0% host-72-175-111-10.bln-mt.client.bresnan.net [72.175.111.10]
0/ 100 = 0% |
4 14ms 0/ 100 = 0% 0/ 100 = 0% 69.145.247.146
0/ 100 = 0% |
5 14ms 0/ 100 = 0% 0/ 100 = 0% 69.144.126.8
0/ 100 = 0% |
6 40ms 0/ 100 = 0% 0/ 100 = 0% gdjco001cr5-GE-3-0-2-U0.int.bresnan.net [72.175.110.240]
0/ 100 = 0% |
7 60ms 0/ 100 = 0% 0/ 100 = 0% te0-0-0-12.ccr21.ord03.atlas.cogentco.com [38.104.103.117]
0/ 100 = 0% |
8 60ms 0/ 100 = 0% 0/ 100 = 0% be2003.ccr42.ord01.atlas.cogentco.com [154.54.29.21]
0/ 100 = 0% |
9 59ms 0/ 100 = 0% 0/ 100 = 0% be2157.ccr22.mci01.atlas.cogentco.com [154.54.6.117]
0/ 100 = 0% |
10 69ms 0/ 100 = 0% 0/ 100 = 0% be2010.ccr22.dfw01.atlas.cogentco.com [154.54.46.218]
0/ 100 = 0% |
11 70ms 0/ 100 = 0% 0/ 100 = 0% be2032.ccr21.dfw03.atlas.cogentco.com [154.54.6.54]
13/ 100 = 13% |
12 65ms 13/ 100 = 13% 0/ 100 = 0% 192.205.36.221
87/ 100 = 87% |
13 --- 100/ 100 =100% 0/ 100 = 0% cr1.dlstx.ip.att.net [12.122.139.18]
0/ 100 = 0% |
14 --- 100/ 100 =100% 0/ 100 = 0% cr1.phmaz.ip.att.net [12.122.28.182]
0/ 100 = 0% |
15 --- 100/ 100 =100% 0/ 100 = 0% 12.123.206.165
0/ 100 = 0% |
16 --- 100/ 100 =100% 0/ 100 = 0% 12-122-254-50.attens.net [12.122.254.50]
0/ 100 = 0% |
17 --- 100/ 100 =100% 0/ 100 = 0% mdf002c7613r0001-gig-12-1.phx1.attens.net [63.241.130.210]

Trace complete.

____________________________

I have no idea why the pings on the pathping are so low. That's where they should be in-game, and I'm just not seeing that.

That damn server in Dallas though. (192.205.36.221 @ hop 12) I googled it and apparently it's been a problem area for a lot of people over the last year. That's what led me to this forum. A guy got a tech rep from his ISP on here and had his data rerouted, completely fixing the problem. How do I go about getting a similar fix?
Double OH 7
join:2009-10-19

Double OH 7

Member

said by Sylar2jz:

I googled it and apparently it's been a problem area for a lot of people over the last year. That's what led me to this forum. A guy got a tech rep from his ISP on here and had his data rerouted, completely fixing the problem. How do I go about getting a similar fix?

Sad to say, Charter no longer has any of their team members active on this form... With out direct support, stuff like this, is often an uphill battle... Best bet would be to call in and hopefully you get someone with experience and capability.

Sorry.

mixdup
join:2003-06-28
Alpharetta, GA

mixdup to Sylar2jz

Member

to Sylar2jz
The problem is that the trouble link is between Cogent and AT&T. It's well outside of Charter's network by the time it has a problem. There's nothing that Charter can do, other than complain to Cogent, and getting in touch with the right person to get that done is going to be troublesome.

It's likely that Cogent already knows about the problem. Hundred million dollar companies don't get that way by not knowing what's going on in their network.

You can attempt to contact the Charter Network Operations Center, but it may or may not do you any good. They'll want that traceroute information you have there.

OrgNOCHandle: NNOC16-ARIN
OrgNOCName: National Network Operations Center
OrgNOCPhone: +1-314-288-3111
OrgNOCEmail: dlnocip@chartercom.com
OrgNOCRef: »whois.arin.net/rest/poc/NNOC16-ARIN

Calero27
join:2014-01-13
Chatham, ON

Calero27 to Sylar2jz

Member

to Sylar2jz
This has been an ongoing problem for years and it doesn't really matter who your ISP is. Until Blizzard stops peering directly with AT&T it will most likely always be there. If you go to Blizzards forum site there are tons of these complaints going back 10 years. Sorry bud.

mixdup
join:2003-06-28
Alpharetta, GA

mixdup

Member

said by Calero27:

This has been an ongoing problem for years and it doesn't really matter who your ISP is. Until Blizzard stops peering directly with AT&T it will most likely always be there. If you go to Blizzards forum site there are tons of these complaints going back 10 years. Sorry bud.

It's not that Blizzard is peering with AT&T, it's that AT&T is providing Blizzard's transit services. Essentially, they are Blizzard's ISP.

The problem is when your ISP (in this case Charter) gets to AT&T through Cogent. Cogent is one of the major transit providers that Netflix uses that is having disputes with AT&T, Verizon, and Comcast. This is actually a side effect of the Netflix issues.