dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
913
share rss forum feed


odog
Cable Centric Vendor Biased
Premium,VIP
join:2001-08-05
Atlanta, GA
kudos:14
Reviews:
·Comcast

2 edits

[ALL] Blizzard traceroutes to Chicago

Can you please commence the tracerouting!

We have made adjustments that will hopefully improve performance. These adjustments should allow us to avoid the Cogent/AT&T peer point in Chicago. This should only affect the Blizzard bound traffic.

208.18.148.176

Don't use (63.240.161.189) this is an AT&T loopback that should not be customer/WoW affecting.


bchandler02

join:2011-07-08
Oklahoma City, OK

1 edit

deleted


Rakeesh

join:2011-10-30
Mesa, AZ
Reviews:
·Sprint Mobile Br..
·Cox HSI
reply to odog

said by odog:

Can you please commence the tracerouting!

We have made adjustments that will hopefully improve performance. These adjustments should allow us to avoid the Cogent/AT&T peer point in Chicago. This should only affect the Blizzard bound traffic.

208.18.148.176
63.240.161.189

So at&t and cogent haven't fixed their problems? What idiots. You'd figure a saturated link would be something they'd want to address rather quickly rather than leave at the wayside, especially if they're a tier 2 ISP. There's no excuse for that kind of thing these days as virtually all vendors provide ample monitoring systems and high availability is relatively cheap now.

Well at least you guys are routing around their mistakes. I'm not a wow player, but that scores a few points in my book regardless.

If you guys would fix the CCI problem I'd change my review.


ikyuaoki

join:2011-04-12
Wichita, KS
Reviews:
·Cox HSI
reply to odog

I'd found that 63.240.161.189 was on the att routing there.

Tracing route to 63.240.161.189 over a maximum of 30 hops

1 6 ms 9 ms 7 ms 10.32.32.1
2 20 ms 7 ms 6 ms 70.183.70.185
3 56 ms 74 ms 75 ms kscydsrj02-ae2.rd.ks.cox.net [70.183.71.105]
4 13 ms 14 ms 13 ms 70.183.71.66
5 12 ms 37 ms 14 ms 70.183.71.64
6 * * 26 ms 68.1.2.109
7 31 ms 25 ms 26 ms ae-12.r08.dllstx09.us.bb.gin.ntt.net [129.250.19
4.173]
8 28 ms 25 ms 25 ms ae-5.r01.dllstx04.us.bb.gin.ntt.net [129.250.3.2
33]
9 30 ms 53 ms 32 ms ae-0.att.dllstx04.us.bb.gin.ntt.net [129.250.8.2
38]
10 58 ms 78 ms 54 ms cr1.dlstx.ip.att.net [12.122.85.234]
11 52 ms 52 ms 55 ms cr2.kc9mo.ip.att.net [12.122.28.86]
12 54 ms 55 ms 55 ms cr2.sl9mo.ip.att.net [12.122.28.90]
13 67 ms 55 ms 55 ms cr2.cgcil.ip.att.net [12.122.2.21]
14 50 ms 51 ms 50 ms gar3.cgcil.ip.att.net [12.122.132.213]
15 52 ms 56 ms 88 ms 12.122.251.22
16 53 ms 52 ms 58 ms 63.240.130.210
17 * * * Request timed out.
18 * * ^C



odog
Cable Centric Vendor Biased
Premium,VIP
join:2001-08-05
Atlanta, GA
kudos:14
reply to odog

Skip that IP, just found out it is an AT&T loopback and shouldn't relate to WoW.


lilstone87

join:2009-04-09
Portsmouth, VA
kudos:3
Reviews:
·Cox HSI

Well here is a traceroute to the top IP address you listed.

Tracing route to 208.18.148.176 over a maximum of 30 hops

1 1 ms 1 ms 1 ms www.asusnetwork.net [192.168.1.1]
2 8 ms 7 ms 8 ms 10.5.0.1
3 8 ms 7 ms 8 ms 68.10.10.65
4 10 ms 9 ms 10 ms 172.22.60.169
5 9 ms 10 ms 10 ms 68.10.8.157
6 * 15 ms * 68.1.4.139
7 17 ms 14 ms 13 ms ae0-202.was14.ip4.tinet.net [77.67.78.49]
8 20 ms 19 ms 19 ms xe-10-0-0.nyc32.ip4.tinet.net [89.149.181.178]
9 * * * Request timed out.
10 * * * Request timed out.



ikyuaoki

join:2011-04-12
Wichita, KS
Reviews:
·Cox HSI
reply to odog

I see. glad that you made a right adjustments to turn the cox customers away from the hosed of AT&T network to other place that i have tested this 208.18.148.176 and it goes away from the AT&T network hosed. good work.

Tracing route to 208.18.148.176 over a maximum of 30 hops

1 6 ms 17 ms 8 ms 10.32.32.1
2 7 ms 11 ms 6 ms 70.183.70.181
3 15 ms 13 ms 13 ms kscydsrj01-ae2.rd.ks.cox.net [70.183.71.101]
4 16 ms 17 ms 19 ms 70.183.71.62
5 15 ms 13 ms 14 ms 70.183.71.109
6 * * * Request timed out.
7 30 ms 52 ms 27 ms ae-12.r08.dllstx09.us.bb.gin.ntt.net [129.250.19
4.173]
8 25 ms 54 ms 51 ms ae-5.r01.dllstx04.us.bb.gin.ntt.net [129.250.3.2
33]
9 * * * Request timed out.
10 * * * Request timed out.
11 ^C



aed

@cox.net

Just noticed the ip address to trace was incorrect.

Cogent is still on the path from Cox in Scottsdale AZ. Can't even trace past their network!

Tracing route to 208.18.148.176 over a maximum of 30 hops

1 1 ms 1 ms 1 ms 192.168.1.1
2 11 ms 8 ms 10 ms 10.85.0.1
3 9 ms 9 ms 8 ms 172.21.1.116
4 27 ms 15 ms 18 ms 70.169.75.116
5 10 ms 12 ms 11 ms chnddsrj01-ae2.0.rd.ph.cox.net [70.169.76.229]
6 75 ms 26 ms 23 ms 68.1.5.139
7 24 ms 25 ms 23 ms te0-0-0-21.ccr22.lax05.atlas.cogentco.com [38.104.84.13]
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.


VentShop

join:2009-08-21
Oklahoma City, OK

1 edit
reply to odog

For some reason I do not thing your routing changes have worked. In fact I have begun to have some major problems since the posting which I did not have before. Could be the local service area and I am testing that as well.

C:\Users\user>tracert 208.18.148.176

Tracing route to 208.18.148.176 over a maximum of 30 hops

1 1 ms 1 ms 1 ms DD-WRT [192.168.10.1]
2 7 ms 8 ms 9 ms 10.3.192.1
3 8 ms 7 ms 7 ms COX-68-12-8-156-static.coxinet.net [68.12.8.156]

4 9 ms 9 ms 7 ms COX-68-12-10-66-static.coxinet.net [68.12.10.66]

5 * * * Request timed out.
6 13 ms 13 ms 28 ms xe-4-3-0.edge4.Dallas3.Level3.net [4.59.32.69]
7 13 ms 15 ms 14 ms ae-4-90.edge2.Dallas3.Level3.net [4.69.145.204]

8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

Looked up some information and it seems that there would have been about 16 hops in total around november 27th of 2012. After being dumped into dallas Level3 communications I am going to figure it would take the same routing through att lines to chicago.

I will have packet loss from 1 to 5 seconds in ping plotter and generally at those times I will have a ping in the range of 300 to 700 come up or be disconnected from the servers. My average ping runs 41 to 43. I rebooted my router as well as my modem and was still having problems and waited to post until after that point in case a route had a need to be refreshed in my equipments tables. I will be changing out my modem on Monday sometime and see if that helps to alleviate the issues but I started to have this particular problem at about the same time that the original post was made and it has steadily gotten worse.