New I.P. address?

[Scratchman]

I tried to run a trace route to the game sites, and after the update with A.T.&.T I get nothing but timeouts now. The last good I.P. addy I had is 206.16.60.39. Was wondering if there has been a new I.P. address assignment?

[Skuzzy]

Nope, that is still good.  However, I would prefer players used 206.16.60.38.

You are on Comcast, so I expect you to have some problems.  Here is why.

traceroute 76.31.215.225
traceroute to 76.31.215.225 (76.31.215.225), 30 hops max, 40 byte packets
 1  206.16.60.46 (206.16.60.46)  0.377 ms  0.319 ms  0.234 ms
 2  mdf001c7613r0001-gig-12-2.dal1.attens.net (63.241.193.13)  0.270 ms  0.276 ms  0.247 ms
 3  12-122-254-29.attens.net (12.122.254.29)  174.483 ms  2.256 ms  204.815 ms
 4  cr1.dlstx.ip.att.net (12.122.139.182)  2.182 ms  1.391 ms  1.241 ms
 5  ggr3.dlstx.ip.att.net (12.122.139.25)  1.241 ms  1.185 ms  1.113 ms
 6  cr2-pos-0-3-3-3.dallas.savvis.net (208.172.139.225)  1.273 ms  1.220 ms  1.248 ms
 7  cr2-tengig-0-7-0-0.losangeles.savvis.net (204.70.196.154)  34.235 ms * *
 8  er2-tengig-3-1.lay.savvis.net (204.70.198.10)  33.794 ms  33.771 ms  33.717 ms
 9  comcast-net.lay.savvis.net (208.172.41.162)  35.040 ms  34.833 ms  34.838 ms
10  pos-0-15-0-0-cr01.dallas.tx.ibone.comcast.net (68.86.85.138)  35.735 ms  35.704 ms  35.992 ms
11  68.86.91.194 (68.86.91.194)  40.506 ms  40.497 ms  40.551 ms
12  po-12-ar01.greenspoint.tx.houston.comcast.net (68.85.244.153)  40.505 ms  40.569 ms  40.568 ms
13  po-16-ar02.bearcreek.tx.houston.comcast.net (68.85.244.74)  42.218 ms  42.267 ms  42.214 ms
14  po-15-ur01.bearcreek.tx.houston.comcast.net (68.85.244.70)  42.376 ms  42.319 ms  46.256 ms
15  68.85.253.26 (68.85.253.26)  45.016 ms  45.114 ms  45.080 ms
16  * * *
17  *^C

Notice hop #7?  This has been an ongoing issue with Comcast for several months now.  Comcast and Savvis know about the problem, but both refuse to fix it.

Our only option is to find another ISP.  We will be working to get test servers into other ISP's and see what they look like.  It is not something we can simply do overnight.

[Scratchman]

Yes I did notice # 7, it makes you wonder, I live outside Houston, yet you show me being routed thru Los Angeles to savvis.net on the way to the Dallas area.
 Here is my trace route to you, which doesn't show me being routed thru savvis. Oh well, since your upgrade I am noticing a better connection. Thanks for all that you do making this such a great game.

Trace Route for http://206.16.60.38/ by Trellian Trace

http://206.16.60.38/
1   192.168.1.1   unknown   0ms
2   206.16.60.38   unknown   62ms
3   68.85.253.33   unknown   16ms
4   68.85.244.81   po-11-ur01.bearcreek.tx.houston.comcast.net   15ms
5   68.85.244.69   po-15-ar02.bearcreek.tx.houston.comcast.net   15ms
6   68.85.244.73   po-16-ar01.greenspoint.tx.houston.comcast.net   15ms
7   68.85.244.154   po-12-ar02.greenspoint.tx.houston.comcast.net   15ms
8   68.86.91.57   te-0-1-0-4-cr01.dallas.tx.ibone.comcast.net   15ms
9   206.82.142.5   a190103.sandpiper.net   62ms
10   209.58.47.13   Vlan6.icore1.DTX-Dallas.as6453.net   46ms
11   192.205.35.57   unknown   62ms
12   12.122.139.106   cr1.dlstx.ip.att.net   46ms
13   12.122.139.153   gar23.dlstx.ip.att.net   62ms
14   12.122.254.154   12-122-254-154.attens.net   46ms
15   63.241.193.22   22.0/26.193.241.63.in-addr.arpa   62ms

[Skuzzy]

It is is any better, it is an accident or a placebo.  Nothing has changed on the routing side of things, which is the problem all Comcast customers are having.

The routing problem is Savvis generated.  We have no control over routes.