Jump to content

site slow - requesting tracert to site (halleminlures.com)


berklee.grad

Recommended Posts

Greetings All,

 

Am in a 'conversation' with our host (ipage.com) and before it escalates to a full fledged argument I am requesting some additional trace routes to QED the issue. 

 

When I run a trace route the result never ends at our domain ( halleminlures.com [66.96.182.208]) - instead I get a destination unreachable from my ping plotter tool. Tracert fails at this hop - endurance-international-group.demarc.cogentco.com [38.97.106.34]. BTW, Pingdom Tools also corroborates that same fail point .  The host implicates my ISP for the reason that the destination is unreachable from my location :rolleyes:

 

Can I impose upon the good will of just a couple of you to run a  tracert to halleminlures.com and paste the results in a reply below?

 

thanks in advance, -Rick

Link to comment
Share on other sites

C:\Program Files (x86)\ICW>tracert halleminlures.com

 

Tracing route to halleminlures.com [66.96.182.208]

over a maximum of 30 hops:

 

  1     1 ms    <1 ms    <1 ms  192.168.1.1

  2    38 ms    26 ms    20 ms  cpe-72-225-192-1.nyc.res.rr.com [72.225.192.1]

  3    14 ms    12 ms    12 ms  tenge-0-2-0-0-nycmnyr-rtr01.nyc.rr.com [24.168.135.121]

  4    19 ms    23 ms    15 ms  bun120.nycmnytg-rtr001.nyc.rr.com [184.152.112.63]

  5    23 ms    11 ms    15 ms  bun6-nycmnytg-rtr002.nyc.rr.com [24.29.148.250]

  6    14 ms    15 ms    19 ms  107.14.19.24  7     *        *        *     Request timed out.

  8    19 ms    45 ms    21 ms  te0-0-0-17.ccr21.jfk05.atlas.cogentco.com [154.54.13.81]

  9    17 ms    15 ms    12 ms  be2061.ccr22.jfk02.atlas.cogentco.com [154.54.3.69]

 10    20 ms    19 ms    25 ms  te0-2-0-1.ccr22.bos01.atlas.cogentco.com [154.54.44.22]

 11    23 ms    19 ms    28 ms  endurance-international-group.demarc.cogentco.com [38.97.106.34]

 12    26 ms    25 ms    25 ms  238.252.148.207.static.yourhostingaccount.com [207.148.252.238]

 13     *        *        *     Request timed out.

 14     *        *        *     Request timed out.

 15     *        *        *     Request timed out.

 16     *        *        *     Request timed out.

 17     *        *        *     Request timed out.

 18     *        *        *     Request timed out.

Link to comment
Share on other sites

greetings tomerg3,

 

thank for taking the time to trace route and post the results!

 

They were indeed helpful.  Your results show an additional hop - before the time out than mine do! interesting Not to mention that you have about half as many hops to the host as I do ;-)

 

your time is greatly appreciated.

 

thanks, -Rick

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...