Help with traceroute - newbie question

1 fa0-1-3.rt1.a5-3.tc.dsvr.net (212.69.210.2) 68.190 ms 231.462 ms 247.939 ms
2 195.226.52.93 (195.226.52.93) 205.809 ms 321.751 ms 0.914 ms
3 62.72.156.142 (62.72.156.142) 6.560 ms 5.760 ms 6.528 ms
4 ge-0-0-0-telee-peleg.router.clara.net (195.66.224.66) 6.720 ms 6.658 ms 7.531 ms
5 fe-4-0-redbus2-pequod.router.clara.net (195.8.68.185) 49.363 ms 9.833 ms 9.694 ms
6 * * *
7 * * *
8 * * *
9 * * *
10 * * khaki.srv2.com (217.158.136.90) 8.120 ms


Now i'm presuming those * are problems, and retries. But how do i tell where this particular problem is?

* means it got no response for that test - it tests each point three times.

As the last point suddenly came to life, it looks like it may have been an intermittent problem at fe-4-0-redbus2-pequod.router.clara.net.

I have a dsvr account, so let me know if I can do any test to help you figure something out (wiil be in the chat room)

Thanks,

The account i'm interested in is the khaki.srv2.com. I can't access the site, which is Freebieholics. This has been happening alot recently, but they generally say to me there is no problem with that server.

And if i understand what you've just said, there is no problem here. Which is what they say this time too LOL.

Here is my trace route same server

tracert khaki.srv2.com

Tracing route to khaki.srv2.com [62.149.36.22]
over a maximum of 30 hops:

1 25 ms 27 ms 27 ms lon1-adsl1.nildram.net [195.149.20.11]
2 25 ms 27 ms 27 ms lon1-9.nildram.net [213.208.106.194]
3 30 ms 29 ms 27 ms nildram-peer1.router.clara.net [195.8.68.197]
4 30 ms 75 ms 30 ms fe-4-0-redbus2-pequod.router.clara.net [195.8.68.185]
5 28 ms 30 ms 30 ms bgp-peer1.nacelle.router.ultraspeed.net [217.158.78.38]
6 30 ms 31 ms 31 ms 62.149.36.22

Trace complete.

but when you do a tracert route to both your DNS you get this

tracert 217.158.136.90

Tracing route to khaki.srv2.com [217.158.136.9<img src=http://www.gamers-forums.com/smilies/cwm/3dlil/errr.gif ALT="0]">
over a maximum of 30 hops:

1 28 ms 29 ms 27 ms lon1-adsl1.nildram.net [195.149.20.11]
2 26 ms 27 ms 27 ms lon1-9.nildram.net [213.208.106.194]
3 27 ms 31 ms 29 ms nildram-peer1.router.clara.net [195.8.68.197]
4 32 ms 29 ms 30 ms fe-4-0-redbus2-pequod.router.clara.net [195.8.68.185]
5 29 ms 30 ms 29 ms fe-4-0-0.nacelle.router.ultraspeed.net [217.158.99.57]
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.

So this says to me it's not clara.net and it's not the main server khaki.srv2.com that resolves to 62.149.36.22 however IP 217.158.136.90 that also has the look-up name khaki.srv2.com is dead as a door nail.

So problem looks to be with your name servers, both down.

Checks out ok from here (Demon), from Dsvr and from a Pipex leased line at the moment. <img src=http://www.ezboard.com/images/emoticons/ohwell.gif ALT=":\">

Next time it plays up, it may be worth trying some of the websites that offer tracert services to see if you can find a pattern. At the moment it looks like the first router that doesn't respond is the culprit.

www.traceroute-gateways.com/

Yeah, what Clarke said!!! Just checked and can't ping either NS from here either. (That blokes just too clever!)

Just got back,

thanks guys, this help is appreciated. So, effectively it is hosteroute, and they should be fixing this problem.

I have recently had their 'alert system' quoted to me , but it obviously isn't that good. Good to know this now, as i'm debating whether to give one of their dedicated servers a go.

Clarke, you may be interested in the reason for my wanting to move to a dedicated server, as you recently warned of a problem a friend of yours had regarding chat services. You posted here that she had her account terminated for too much resources being used. This wouldn't happen now, instead they have limited customers to one of two packages built in to the hosting. Neither satifies my requirments. On any less than a dedicated server they limit each site to a maximum of 20% of the CPU it seems, and other packages may exceed this.

Clarke, would your service have warned me about this? I don't mind the thought of putting them to the test properly, and having some real figures to base my decisions on.

Yes it would have alerted you straight away, and you can even alert your hosting company support if they don't mind at the same time.. Most of my clients that do that are paying the hosting company loads of money per month and as such they never say it's an issue, however if they say we have our own system in place, then ask them why my site down and you only ever notice when I tell you about it.

Many companies monitor from inside the network and using ping also, this is not a true test if your site is down to the outside world.. also a server can be up but apache can be down... at any rate your welcome to try the free 2 week trial and see what you think. www.websiteavailability.com sign up via your Paid on Results affiliate link, so if you do go for the service you will get 12% back each month in the form of affiliate commission.