I've been chasing more red herrings on this issue than I'd like to admit, and this might be just another....
Suddenly, around June 17th, a new site I've been working on for a couple of months would just time-out randomly and be inaccessible (either "Time-Out" or "Connection Interrupted" depending on factors that are a mystery to me) for 5-10 minutes. I thought maybe my CMS program was inefficient and causing server load issues, so I've been stripping down functionality like crazy. Then I went to my host's website, dinsol.com, pressed refresh rapidly like 5 times and got the same error.
(sometimes I have to hit reload rapidly 25-30 times, which I can understand a site blocking someone doing that, but sometimes it times-out during your typical viewing)
I have 2 other accounts with the host, one of them also suddenly has this problem, the other doesn't.
I contacted the host, and they say they cannot repeat the error and to check the site by connecting through another ISP. I did, and after duplicating this error consistently through my telephone company's DSL, cable company's broadband, and a wide range of web-based proxys, using PC, Mac, Firefox, Opera, IE I don't see how it can only be me.
They requested I do a traceroute on my site. I ended up doing one on all the sites that give me this error. The all have identical first 10 hops before the final 11th connection
Code:
1 2 ms 1 ms 1 ms 192.168.0.1
2 13 ms 9 ms 8 ms dsl1-fairport.roc.ny.frontiernet.net [70.100.96.1]
3 11 ms 10 ms 9 ms 216.190.217.19
4 11 ms 9 ms 10 ms 65.73.205.13
5 12 ms 9 ms 9 ms ge-1-1-0--0.cr01.roch.ny.frontiernet.net [74.40.3.205]
6 37 ms 47 ms 18 ms so-0-0-0--0.cr01.nwrk.nj.frontiernet.net [74.40.3.233]
7 20 ms 17 ms 17 ms so-0-0-0--0.br01.nwrk.nj.frontiernet.net [74.40.3.146]
8 19 ms 18 ms 18 ms equinix.tge4-3.ar1.ewr1.us.nlayer.net [206.223.131.61]
9 19 ms 17 ms 18 ms as25653.ge3-3.ar1.ewr1.us.nlayer.net [69.31.95.82]
10 19 ms 18 ms 17 ms 208.116.63.254
11 20 ms 19 ms 19 ms 65.98.111.65
When the site comes up as "timed-out" or "connection interrupted" hop #11 is "Request Timed Out"
then I ran a tracert on a site I have hosted with them that doesn't have this problem:
Code:
1 1 ms 1 ms 1 ms 192.168.0.1
2 149 ms 100 ms 90 ms dsl1-fairport.roc.ny.frontiernet.net [70.100.96.1]
3 287 ms 312 ms 158 ms 216.190.217.19
4 49 ms 177 ms 41 ms 65.73.205.5
5 94 ms 41 ms 144 ms ge-1-1-0--0.cr01.roch.ny.frontiernet.net [74.40.3.205]
6 66 ms 173 ms 181 ms so-0-0-0--0.cr01.nwrk.nj.frontiernet.net [74.40.3.233]
7 134 ms 178 ms 181 ms so-0-0-0--0.br01.nwrk.nj.frontiernet.net [74.40.3.146]
8 89 ms 177 ms 179 ms equinix.tge4-3.ar1.ewr1.us.nlayer.net [206.223.131.61]
9 84 ms 180 ms 194 ms as25653.ge3-3.ar1.ewr1.us.nlayer.net [69.31.95.82]
10 112 ms 181 ms 179 ms 208.116.63.252
11 108 ms 185 ms 180 ms server4.rightdns.com [65.98.41.98]
If you noticed, connection #10 is different.
I presented this to my host, and they say:
Quote:
We have checked the issue. The traceroute results convey that you are not able to access your site due to a problem with the local ISP at your end.
Kindly try to access your site using another ISP and check. Also, could you please get back to us with your exact error message and the local IP so that we can check if it is blocked in the server firewall settings.
|
I've been with this hosting company for over 5 years, and their customer service has been so helpful, and before this issue came up, their hosting so reliable, I hate to think that they are trying to avoid blame and avoid having to fix this problem, but I really don't see the logic in having it be on my side of the connection when the only difference between a site that works and one that doesn't is the final connection to their servers.
Unfortunately, I know nothing about what these traceroutes are suppose to tell me.
Are they handing me a line?