tenzan
09-21-2005, 10:22 AM
I'm very sorry if I'm wrong.
I'm not able to access www.site5.com but can ping.
Can anyone else access the page?
tenzan
I'm not able to access www.site5.com but can ping.
Can anyone else access the page?
tenzan
![]() | View Full Version : Is www.site5.com working now? tenzan 09-21-2005, 10:22 AM I'm very sorry if I'm wrong. I'm not able to access www.site5.com but can ping. Can anyone else access the page? tenzan catfished 09-21-2005, 10:31 AM I'm accessing it just fine here in Northern California. tenzan 09-21-2005, 10:38 AM Originally posted by catfished I'm accessing it just fine here in Northern California. I'm in Kyrgyzstan. Couldn't access at work, and even from home... Smth strange with my internet... :( osphere 09-21-2005, 11:57 AM Maybe a down link from your ISP... works great from Mexico City heh tenzan 09-21-2005, 12:14 PM Originally posted by osphere Maybe a down link from your ISP... works great from Mexico City heh I'm going to confirm from my ISP...:crying: ACcomunica 09-21-2005, 01:39 PM I was having the same problem earlier to access Site5 and other sites in the US. I've done a tracert and the connection was timing out in a Telegloble Miami node. Everything is working fine now. tenzan 09-21-2005, 01:52 PM Originally posted by ACcomunica I was having the same problem earlier to access Site5 and other sites in the US. I've done a tracert and the connection was timing out in a Telegloble Miami node. Everything is working fine now. How did you fix it? My tracert gave me: Tracing route to www.site5.com [216.118.110.8] over a maximum of 30 hops: 1 <10 ms <10 ms <10 ms SAMBA [192.168.0.1] 2 16 ms 15 ms 16 ms loop-cs1.elcat.kg [212.42.96.213] 3 16 ms 16 ms 15 ms cs7206.elcat.kg [212.42.96.24] 4 531 ms 531 ms 563 ms 217.151.224.65 5 531 ms 547 ms 562 ms 217.151.224.90 6 563 ms 546 ms 610 ms ffm-k88-i1-feth2-15.telia.net [213.248.68.193] 7 531 ms 563 ms 547 ms ffm-b2-geth3-1.telia.net [213.248.68.33] 8 547 ms 562 ms 531 ms ffm-bb1-pos7-3-3.telia.net [213.248.65.33] 9 547 ms 562 ms 609 ms prs-bb1-pos7-0-0.telia.net [213.248.64.110] 10 547 ms 563 ms 562 ms ldn-bb1-pos7-2-0.telia.net [213.248.64.10] 11 625 ms 641 ms 641 ms nyk-bb1-link.telia.net [213.248.65.98] 12 625 ms 625 ms 641 ms nyk-b2-pos1-0-0.telia.net [213.248.80.78] 13 625 ms 625 ms 640 ms ft-gw.sffca.ip.att.net [192.205.32.89] 14 688 ms 641 ms 640 ms tbr1-p012201.n54ny.ip.att.net [12.123.3.106] 15 625 ms 656 ms 657 ms gar1-p3100.nwrnj.ip.att.net [12.123.214.181] 16 625 ms 641 ms 640 ms att-gige.esd1.nwr.nac.net [12.119.140.26] 17 641 ms 625 ms 641 ms 2.ge-0-0-0.gbr1.nwr.nac.net [209.123.11.213] 18 625 ms 688 ms 640 ms 0.ge-0-0-0.gbr1.oct.nac.net [209.123.11.49] 19 625 ms 688 ms 640 ms site5.com [216.118.110.8] Trace complete. ldcdc 09-21-2005, 02:04 PM How did you fix it?He didn't. :) It was probably fixed by whomever was in charge of the failing node, or it just fixed itself. ACcomunica 09-21-2005, 02:04 PM It was an external problem, i didn't do anything but it's working now. :) whoiscartpro 09-21-2005, 04:44 PM We have an account on Site5. Their and our sites have been working everytime. The uptime is %99.9 layer0 09-21-2005, 04:47 PM Originally posted by tenzan How did you fix it? My tracert gave me: Tracing route to www.site5.com [216.118.110.8] over a maximum of 30 hops: 1 <10 ms <10 ms <10 ms SAMBA [192.168.0.1] 2 16 ms 15 ms 16 ms loop-cs1.elcat.kg [212.42.96.213] 3 16 ms 16 ms 15 ms cs7206.elcat.kg [212.42.96.24] 4 531 ms 531 ms 563 ms 217.151.224.65 5 531 ms 547 ms 562 ms 217.151.224.90 6 563 ms 546 ms 610 ms ffm-k88-i1-feth2-15.telia.net [213.248.68.193] 7 531 ms 563 ms 547 ms ffm-b2-geth3-1.telia.net [213.248.68.33] 8 547 ms 562 ms 531 ms ffm-bb1-pos7-3-3.telia.net [213.248.65.33] 9 547 ms 562 ms 609 ms prs-bb1-pos7-0-0.telia.net [213.248.64.110] 10 547 ms 563 ms 562 ms ldn-bb1-pos7-2-0.telia.net [213.248.64.10] 11 625 ms 641 ms 641 ms nyk-bb1-link.telia.net [213.248.65.98] 12 625 ms 625 ms 641 ms nyk-b2-pos1-0-0.telia.net [213.248.80.78] 13 625 ms 625 ms 640 ms ft-gw.sffca.ip.att.net [192.205.32.89] 14 688 ms 641 ms 640 ms tbr1-p012201.n54ny.ip.att.net [12.123.3.106] 15 625 ms 656 ms 657 ms gar1-p3100.nwrnj.ip.att.net [12.123.214.181] 16 625 ms 641 ms 640 ms att-gige.esd1.nwr.nac.net [12.119.140.26] 17 641 ms 625 ms 641 ms 2.ge-0-0-0.gbr1.nwr.nac.net [209.123.11.213] 18 625 ms 688 ms 640 ms 0.ge-0-0-0.gbr1.oct.nac.net [209.123.11.49] 19 625 ms 688 ms 640 ms site5.com [216.118.110.8] Trace complete. The problem appears to start at 217.151.224.65 whcih is what results in high latency to everything after it. I would suggest calling your ISP and mentioning this. Regards, IGobyTerry 09-21-2005, 06:11 PM Originally posted by elix The problem appears to start at 217.151.224.65 whcih is what results in high latency to everything after it. I would suggest calling your ISP and mentioning this. Regards, It's a cross country link. More than likely Kyrgyzstan has a pretty small connection leaving the country, that is at it's max. Since you're able to traceroute to the server, it's not a network problem. It's possible that Site5 is blocking you with some other kind of security feature, due to fraud, attacks ... etc. The 217 IP Range does have a high fraud rate in my experiences, so it's very likely that may be the problem, and they've just used something like a .htaccess file to block it out. webhostingwiz 09-21-2005, 06:29 PM up for me... Los Angeles 3:29PM Pinging site5.com [216.118.110.8]: Ping #1: Got reply from 216.118.110.8 in 12ms [TTL=53] Ping #2: Got reply from 216.118.110.8 in 13ms [TTL=53] Ping #3: Got reply from 216.118.110.8 in 12ms [TTL=53] Ping #4: Got reply from 216.118.110.8 in 12ms [TTL=53] Done pinging site5.com! ldcdc 09-21-2005, 08:00 PM It's possible that Site5 is blocking you with some other kind of security feature, due to fraud, attacks ... etc. The 217 IP Range does have a high fraud rate in my experiences, so it's very likely that may be the problem, and they've just used something like a .htaccess file to block it out.I remember Godaddy used to do something like this for my country for about a year or so. Anyway, I tried to visit site5.com several times today and had no problem doing so. (not that I'm as accurate as a monitoring service) :) RackWorx 09-21-2005, 08:42 PM Works fine for me from Ft. Lauderdale, Florida. You might want to try contacting your ISP and Site5 support. tenzan 09-21-2005, 11:36 PM Originally posted by ihtech Works fine for me from Ft. Lauderdale, Florida. You might want to try contacting your ISP and Site5 support. I contacted my ISP. Seems external problem. Maybe Site5 blocks our IP addresses...:( tenzan 10-02-2005, 01:27 AM Very strange! Yesterday for the 1st time I could access site5.com, but today I can't. Will confirm my ISP tomorrow... tenzan cwheat 10-02-2005, 06:16 AM Does not pull up for me. I am located in Thailand. tenzan 10-02-2005, 06:53 AM Originally posted by cwheat Does not pull up for me. I am located in Thailand. Do you mean you are also unable to access? premium20 10-02-2005, 07:09 AM Works fine for me from India. Thanks cwheat 10-02-2005, 08:56 AM Do you mean you are also unable to access? Yes I am not able to pull it up in the browser, unable to ping... it can not resolve site5.com... and of course can not do a trace route. However if I take the IP address that was resolved when WebRhino did his ping test. I still can not pull the site in the browser, ping shows Request timed out, and here are the tracert results: C:\Documents and Settings\Me>tracert 216.118.110.8 Tracing route to 216.118.110.8 over a maximum of 30 hops 1 42 ms 41 ms 42 ms 192.168.1.1 2 43 ms 43 ms 43 ms adsl-bkkSP13.csloxinfo.net [210.1.48.17] 3 44 ms 45 ms 43 ms 203.146.61.49 4 49 ms 43 ms 47 ms 203.170.226.129 5 49 ms 44 ms 44 ms 61.19.15.217 6 44 ms 48 ms 45 ms 202.47.253.148 7 * * * Request timed out. 8 * * * Request timed out. 9 * * * Request timed out. 10 * * * Request timed out. From their it is just request timed out... Hope this helps some one. Chris tenzan 10-02-2005, 09:05 AM It seems not only with me this happens. Maybe Site5 side problem?.. |