[thelist] tracert timeout

[Anthony Baratta]

Here's a trace route from my PC.....

C:\>tracert gozz.com

Tracing route to gozz.com [216.150.6.14]
over a maximum of 30 hops:

   1   <10 ms   <10 ms   <10 ms  lanmodem [192.168.1.254]
   2    31 ms    32 ms    62 ms  max6.sktn01.pbi.net [63.200.104.135]
   3    31 ms    47 ms    31 ms  core1-fa0-1-0.sktn01.pbi.net [63.200.104.129]
   4    31 ms    32 ms    62 ms  edge1-fa4-0-0.sktn01.pbi.net [63.200.104.97]
   5    46 ms    47 ms    47 ms  sfra1sr2-0-0.ca.us.prserv.net [165.87.225.18]
   6    78 ms    94 ms    93 ms  sfra1sr3-ge-2-0-0-0.ca.us.prserv.net 
[165.87.33.121]
   7   125 ms   140 ms   125 ms  ibr03-p5-2.sntc03.exodus.net [209.185.249.245]
   8    78 ms    63 ms    94 ms  bbr01-g4-1.sntc03.exodus.net [216.33.153.97]
   9   188 ms   188 ms   203 ms  bbr01-p0-1.hrnd01.exodus.net [216.32.173.86]
  10   203 ms   203 ms   188 ms  bbr01-p5-0.jrcy01.exodus.net [209.185.249.213]
  11   140 ms   172 ms   156 ms  bbr01-p1-0.whkn01.exodus.net [209.1.169.53]
  12   125 ms   141 ms   125 ms  dcr03-g6-0.whkn01.exodus.net [216.35.65.81]
  13   125 ms   125 ms   141 ms  csr02-ve241.whkn01.exodus.net [216.35.65.211]
  14   140 ms   188 ms   141 ms  64.14.48.42
  15     *        *        *     Request timed out.

It looks like the router interface is hosed on 64.14.48.42. That means that 
routes to the "other side" of this router are not accessible. I would get 
your hosting company to contact Exodus and see if they can prod someone 
into looking into it.
---
Anthony Baratta
President
Keyboard Jockeys