Web Hosting Talk : Web Hosting Main Forums : Web Hosting : MY Site Down .. Advice Me Please with Good hosting.

[Fudevs]

Hello,

My Website www.Saharny.com ... is Down .. this is not the first time.. also i cant login to my FTP ..
Every time i told my hosting provider this .. he told me .. everything is good and there is no problem at his end..

So whats to do ?
is this really problem from my side ? or what ..

here is Screen for the problem

http://img182.imageshack.us/img182/7137/ftpjz4.jpg

anyone advice me what to do ? as i paid for one year.
also is this any good web site ?
is the website working with anyone ?
what this Error Message in the Photo means ?

Regards

[JPC-Tracie]

Have you tried tracerts to the domain/IP to see where the timeout is occurring?

[CodyRo]

Originally Posted by Fudevs

Hello,

My Website www.Saharny.com ... is Down .. this is not the first time.. also i cant login to my FTP ..
Every time i told my hosting provider this .. he told me .. everything is good and there is no problem at his end..

So whats to do ?
is this really problem from my side ? or what ..

here is Screen for the problem

http://img182.imageshack.us/img182/7137/ftpjz4.jpg

anyone advice me what to do ? as i paid for one year.
also is this any good web site ?
is the website working with anyone ?
what this Error Message in the Photo means ?

Regards

It appears to be working now for me, is it still down for you? If so its likely its on your end (routing, firewall, etc).

[MyWinsVPS]

Seems to be ISP issue or maybe the host is having FTP software issues at the moment. Give it a couple of hours and see if the problem clears up.

[markjut]

Your site is working fine for me

[Blue316]

Your site is currently resolving on my end aswell. It could be if you are FTPing allot of data or connecting to the site that your current hosts firewall is grabbing you. In either case your host should be attempting to trouble shoot it with you. Either by having you do tracerts or checking the FW. If the issue still happens and they do not help you resolve it I would say your better off finding a new host.

[koolcards]

Originally Posted by JPC-Tracie

Have you tried tracerts to the domain/IP to see where the timeout is occurring?

Yep, what JPC-Tracie said.
The site is in Texas in the U.S. and you're in Egypt. The odds are good your FTP client is timing out because of something in between rather than at the server end.

Open a command window under your "Start" button, "Run", and type "cmd" in the DOS window that opens. Then type "tracert Saharny.com" and hit <enter>.

tracert Saharny.com

You can also use "tracert 75.126.158.98" (that's your site's IP address).

tracert 75.126.158.98

The list shown as a result will show you all the connections between your PC and the site along with the amount of time each node takes.

[Fudevs]

First of all many thanks for all my friends here.. i really appreciate ur help all.

here is screen from Firefox

http://img395.imageshack.us/img395/1350/sahuj9.jpg

here is screen from IE

http://img180.imageshack.us/img180/6369/sahahx1.jpg

here is my tracert result

http://img180.imageshack.us/img180/9106/traceqq0.jpg

I tires to connect using WS_FTP Program & Filezella .. but i cant access my FTP
Also i tires to access the site from many different location .. but the same Result .. NO ACCESS

So ?

[Blue316]

From your tracert you are getting droped at the switch right before your site. If you supply your current host your tracert they should be able to resolve the issue for you.

[Fudevs]

Originally Posted by Blue316

From your tracert you are getting droped at the switch right before your site. If you supply your current host your tracert they should be able to resolve the issue for you.

So my problem is from my Hosting Provider ? i just want the clear answer to know whats wrong .. and whats the reason !!

[koolcards]

Originally Posted by Blue316

From your tracert you are getting droped at the switch right before your site. If you supply your current host your tracert they should be able to resolve the issue for you.

No, traces from other places are fine. Yours is one of the worst I've seen and bounces around a lot where it doesn't need to.

At the same time, what Blue316 said is correct. Your host may be able to help by referring the trace you provide him to the Network people in the NOC who may be able to advertise a different routing.

[gameforever]

I think that should be the provider's server has a problem.

Your site is normal now, but if it is often down, I think you should consider replacing a good host provider.

But I want to remind you:
1. When you find your satisfaction hosting provider, you should search for their related post in the Forum and read others opinions, then decide.

2. When you choose hosting, you should take into account upgrade, so find whether they support the corresponding services.

[Blue316]

Originally Posted by koolcards

No, traces from other places are fine. Yours is one of the worst I've seen and bounces around a lot where it doesn't need to.

At the same time, what Blue316 said is correct. Your host may be able to help by referring the trace you provide him to the Network people in the NOC who may be able to advertise a different routing.

You have to remember hes in Egypt so his route is going to be a little longer then here in the states.

But I asure you "po1.fcr02.dal01.dallas-datacenter.com [66.228.118.178]" Is the switch in front of the server hes on so he is either blocked on the server or null routed there is no other cause. Have your host check the firewall odd's are your blocked.

[koolcards]

Originally Posted by Blue316

You have to remember hes in Egypt so his route is going to be a little longer then here in the states.

But I asure you "po1.fcr02.dal01.dallas-datacenter.com [66.228.118.178]" Is the switch in front of the server hes on so he is either blocked on the server or null routed there is no other cause. Have your host check the firewall odd's are your blocked.

I have had routes almost as long in some places just going across the U.S. (13 jumps). But not times that bad. He's showing 15 hops with times as high as 454ms.
He is dying within the local network at a switch just before his server and, just my opinion,but there may not be anything his host can do directly but something that NOC personnel may have to adjust.

Here's a trace from a machine in San Diego (further away) to his gateway IP in Egypt (with about the same number of hops):

2 216.98.153.22 0.294 ms 0.321 ms 0.492 ms
3 gi0-6.na21.b006463-1.san01.atlas.cogentco.com (66.28.28.125) 1.049 ms 0.781 ms 0.715 ms
4 gi1-45.3512.ccr01.san01.atlas.cogentco.com (38.20.33.125) 1.634 ms 1.136 ms 0.923 ms
5 te4-1.ccr01.sna02.atlas.cogentco.com (154.54.25.125) 3.444 ms 3.326 ms 3.497 ms
6 te3-4.mpd01.lax01.atlas.cogentco.com (154.54.3.38) 4.056 ms 4.325 ms *
7 te4-2.ccr01.lax04.atlas.cogentco.com (154.54.24.70) 4.427 ms te3-2.ccr01.lax04.atlas.cogentco.com (154.54.24.62) 4.101 ms te4-2.ccr01.lax04.atlas.cogentco.com (154.54.24.70) 4.502 ms
8 62.216.144.181 12.443 ms flagtelecom.lax04.atlas.cogentco.com (154.54.11.78) 12.177 ms 62.216.144.181 11.980 ms
9 so-0-3-2.0.pjr01.nyc007.flagtel.com (62.216.128.133) 232.065 ms 232.139 ms 232.163 ms
10 * * *
11 * * *
12 so-0-0-0.0.cjr04.alx001.flagtel.com (62.216.129.198) 235.113 ms 235.135 ms 231.971 ms
13 80.77.0.190 242.007 ms 243.287 ms 242.754 ms
14 host-62-135-105-1.static.link.net (62.135.105.1) 245.212 ms 244.908 ms 242.901 ms

Times are marginally high, but nothing like he's showing in his trace to his machine.
And here's the same server in San Diego to his site (with more hops):

2 216.98.153.22 9.189 ms 8.084 ms 6.259 ms
3 gi0-6.na21.b006463-1.san01.atlas.cogentco.com (66.28.28.125) 0.567 ms 0.641 ms 0.962 ms
4 gi1-45.3512.ccr01.san01.atlas.cogentco.com (38.20.33.125) 1.213 ms 0.841 ms 0.964 ms
5 te4-1.ccr01.sna02.atlas.cogentco.com (154.54.25.125) 3.278 ms 3.221 ms 3.348 ms
6 te3-4.mpd01.lax01.atlas.cogentco.com (154.54.3.38) 23.905 ms * *
7 * * *
8 savvis.lax05.atlas.cogentco.com (154.54.14.30) 6.263 ms pr2-ge-0-1-1.losangelesequinix.savvis.net (208.174.196.105) 6.227 ms savvis.lax05.atlas.cogentco.com (154.54.14.30) 5.536 ms
9 * * *
10 cr2-tengige0-7-5-0.dallas.savvis.net (204.70.196.29) 37.697 ms 37.144 ms 37.412 ms
11 dpr1-ge-4-0-0.dallasequinix.savvis.net (204.70.196.30) 36.238 ms 36.229 ms 36.110 ms
12 er1-te-2-1.dallasequinix.savvis.net (204.70.204.145) 37.327 ms 37.967 ms 38.097 ms
13 te1-1.cer02.dal01.dallas-datacenter.com (208.175.175.10) 36.785 ms 36.075 ms 36.026 ms
14 po2.dar01.dal01.dallas-datacenter.com (66.228.118.205) 34.749 ms 34.708 ms 34.692 ms
15 po1.fcr02.dal01.dallas-datacenter.com (66.228.118.178) 34.811 ms 34.940 ms 35.147 ms
16 * * *
17 * * *
18 * * *
19 * * *

The same 13 or more hops from machines in Pennsylvania and even from servers in Atlanta, Georgia, all in the U.S., but the times are all better. And it appears that ICMP returns are blocked after a certain point in the dallas-datacenter.com.

Given that his host has filled whatever connection they're on or has his machine overloaded and can't respond, which could cause this type of blockage/bottleneck (although everyone else seems to have been able to load his site), I didn't want to get into the whole thing about his host's upstream being somebody elses NOC. And I don't want to accuse his host (whoever it is) of anything until they've had a chance to fix whatever the problem may be.

Fudevs: Just my 2 cents but, first, if you forward that copy of your tracert to your host and they can't do anything to help, then start looking around for a new home.

[Phynom Technologies]

It is working over here for me.

Also I think you should never pre-pay more than 3 Months without properly knowing the host.

Go on the monthly plan first then if you like it, upgrade to the yearly.

Good Luck