Hi,

Just last week I moved my sites to icdsoft.com from cyberwings after reading the many excellent reviews that they've received.

The setup process was very smooth - they sent me the nameservers and IP address info within 10 minutes of my ordering. I had a couple of customer service questions and they were all answered within a few minutes using their online support system.

That was last week.

This morning, my sites are down. Their own site (icdsoft.com) is down. Their support site (suresupport.com) is down and the site that the domains are hosted on (thehosting123.com) is down.

Doing a tracert to any of these domain names reaches ge-0-0-0.a01.newthk01.hk.ra.verio.net [203.131.240.35] after which it times out.

Any suggestions? Am I jinxed?

-ThickAsABrick.

They all work for me just fine. Might be your ISP is having problems??

Here's what I get when I do a tracert to icdsoft.com:

Trace icdsoft.com; Start time 07/18/02 05:31:37
Tracing route to 203.194.209.185
Timed out
Timed out from 203.194.209.185: time=0 ms
Hop Avg Diff Address
1 163 163 63.55.0.37 tnt15.sfo8.da.uu.net
2 151 -12 67.193.208.129
3 153 2 152.63.54.178 221.ATM2-0.XR1.SFO4.ALTER.NET
4 151 -2 152.63.55.57 0.so-0-0-0.XL1.SFO4.ALTER.NET
5 148 -3 152.63.145.242 0.so-6-0-0.XL1.SAC1.ALTER.NET
6 142 -6 152.63.52.249 POS6-0.BR6.SAC1.ALTER.NET
7 149 7 129.250.9.97 p4-2-2-0.r01.scrmca01.us.bb.verio.net
8 153 4 129.250.3.33 p4-7-1-0.r04.snjsca03.us.bb.verio.net
9 158 5 129.250.4.154 p4-0-0-0.r80.snjsca03.us.bb.verio.net
10 358 200 129.250.4.141 p1-0-2-1.r00.newthk01.hk.bb.verio.net
11 358 0 203.131.240.35 ge-0-0-0.a01.newthk01.hk.ra.verio.net
12 * * Timed out
13 * * Timed out
14 * * Timed out
15 * * Timed out
16 * * Timed out

Could you please verify if you are seeing this as well? Thanks.

Also, my site hosted on icdsoft is "ravisnet.com". Could you please try pinging this as well? Thanks.

-ThickAsABrick.

My previous post used WS-PingProPack for the tracert and may seem confusing. Here's a DOS tracert to my domain:


C:\>tracert www.ravisnet.com

Tracing route to ravisnet.com [203.194.209.193]
over a maximum of 30 hops:

1 157 ms 159 ms 149 ms tnt15.sfo8.da.uu.net [63.55.0.37]
2 150 ms 148 ms 139 ms 67.193.208.129
3 150 ms 139 ms 139 ms 221.ATM2-0.XR1.SFO4.ALTER.NET [152.63.54.178]
4 140 ms 139 ms 139 ms 0.so-0-0-0.XL1.SFO4.ALTER.NET [152.63.55.57]
5 150 ms 139 ms 149 ms 0.so-6-0-0.XL1.SAC1.ALTER.NET [152.63.145.242]
6 150 ms 150 ms 139 ms POS6-0.BR6.SAC1.ALTER.NET [152.63.52.249]
7 150 ms 139 ms 150 ms p4-2-2-0.r01.scrmca01.us.bb.verio.net [129.250.9.97]
8 160 ms 140 ms 159 ms p4-7-1-0.r04.snjsca03.us.bb.verio.net [129.250.3.33]
9 160 ms 150 ms 159 ms p4-2-3-0.r80.snjsca03.us.bb.verio.net [129.250.4.87]
10 351 ms 359 ms 359 ms p1-0-2-1.r00.newthk01.hk.bb.verio.net [129.250.4.141]
11 360 ms 350 ms 350 ms ge-0-0-0.a01.newthk01.hk.ra.verio.net [203.131.240.35]
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.

You're up and running for me from here "Got New Host" in spiffy metal font...

3 bwi2-core1-pos1-0.atlas.algx.net (165.117.60.125) 4.191 ms 4.202 ms 4.151 ms
4 dca1-core12-pos5-0.atlas.algx.net (165.117.48.74) 10.508 ms 10.578 ms 10.451 ms
5 dca1-core11-pos6-3.atlas.algx.net (165.117.63.113) 10.496 ms 10.462 ms 10.463 ms
6 dca6-core3-pos4-0.atlas.algx.net (165.117.48.78) 12.108 ms 11.832 ms 11.805 ms
7 dca6-core2-pos6-0.atlas.algx.net (165.117.48.109) 11.885 ms 11.891 ms 11.848 ms
8 p1-0-1.r01.stngva01.us.bb.verio.net (129.250.9.149) 12.973 ms 12.957 ms 12.863 ms
9 p4-1-0-0.r02.stngva01.us.bb.verio.net (129.250.4.186) 13.003 ms 13.042 ms 12.971 ms
10 p16-0-0-0.r01.chcgil01.us.bb.verio.net (129.250.5.102) 39.066 ms 39.026 ms 38.885 ms
11 p16-5-0-0.r02.chcgil01.us.bb.verio.net (129.250.2.221) 38.977 ms 38.987 ms 38.895 ms
12 p16-3-0-0.r00.chcgil06.us.bb.verio.net (129.250.5.114) 39.090 ms 39.093 ms 39.047 ms
13 p16-0-1-1.r21.sttlwa01.us.bb.verio.net (129.250.2.6) 95.710 ms 95.660 ms 95.830 ms
14 p16-3-0-0.r80.sttlwa01.us.bb.verio.net (129.250.3.19) 95.823 ms 95.679 ms 95.617 ms
15 p4-0-3-0.r00.tokyjp01.jp.bb.verio.net (129.250.4.61) 206.992 ms 206.828 ms 206.926 ms
16 p1-0-3-1.r00.newthk01.hk.bb.verio.net (129.250.4.143) 277.763 ms 276.961 ms 278.336 ms
17 ge-0-0-0.a01.newthk01.hk.ra.verio.net (203.131.240.35) 277.214 ms 277.350 ms 277.006 ms
18 61.200.84.206 (61.200.84.206) 255.163 ms 241.425 ms 250.765 ms
19 ge3-2-cor0802.hk03.iadvantage.net (202.85.168.201) 248.381 ms 249.642 ms 241.358 ms
20 v010-m02.hk03.iadvantage.net (202.85.168.163) 243.400 ms 245.555 ms 252.130 ms
21 203.194.209.193 (203.194.209.193) 256.171 ms 247.154 ms 239.248 ms

Your site comes up for me.

Thanks for checking that for me.

Considering that the tracerts work fine for you folks, I am trying to figure out why my tracerts are timing out after the verio.net step in Hong Kong. Any/all suggestions/thoughts appreciated.

Thanks again.

-ThickAsABrick.

It works ok form here in Sydney, Australia:


Tracing route to idcsoft.com [216.166.233.236]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms descartes.dc2.largenets.com [192.168.1.1]
2 8 ms 50 ms 8 ms 10.25.128.1
3 11 ms 9 ms 10 ms bla4-ge1.gw.optusnet.com.au [211.28.108.1]
4 9 ms 16 ms 9 ms ndmc1-pos5-7.gw.optusnet.com.au [198.142.195.129]
5 11 ms 10 ms 9 ms ndmc2-ge1.gw.optusnet.com.au [211.28.96.2]
6 11 ms 11 ms 11 ms pos2-3.ig5.optus.net.au [202.139.0.13]
7 160 ms 160 ms 165 ms 203.202.143.210
8 186 ms 170 ms 160 ms iar4-so-2-3-0-0.SanFrancisco.cw.net [208.173.173.217]
9 175 ms 160 ms 160 ms acr1-loopback.SanFrancisco.cw.net [206.24.210.61]
10 165 ms 160 ms 161 ms cw-gw.sffca.ip.att.net [192.205.32.109]
11 177 ms 177 ms 165 ms tbr2-p013802.sffca.ip.att.net [12.122.11.229]
12 173 ms 171 ms 194 ms tbr1-cl3.la2ca.ip.att.net [12.122.10.26]
13 219 ms 219 ms 217 ms 12.122.10.73
14 217 ms 216 ms 217 ms 12.122.12.58
15 216 ms 216 ms 219 ms gar1-p360.dlstx.ip.att.net [12.123.16.233]
16 217 ms 216 ms 216 ms gar1-p340.dlrtx.ip.att.net [12.123.196.97]
17 199 ms 200 ms 200 ms 12.119.136.22
18 199 ms 201 ms 199 ms border1.ge3-1-bbnet1.ext1a.dal.pnap.net [216.52.191.24]
19 204 ms 201 ms 200 ms madisonriver-1.border1.ext1a.dal.pnap.net [216.52.189.38]
20 233 ms 232 ms 237 ms atm-1-0-3122.rharnc.madisonriver.net [66.79.76.1]
21 * * * Request timed out.
22 240 ms 243 ms 241 ms 216-166-233-236.clec.madisonriver.net [216.166.233.236]

Trace complete.

--Shaun

Comes up nice and fast from Arizona USA.
9 out of 10 problems with the internet is caused by your own ISP and yet people fail to check that first.
Never could understand that.

this happened to one of our customers the other day and it and it ended up being that he had firewall software like "zone alarm" installed on his machine and it was blocking out ip address for some reason.
Maybe this is something you should look into and make sure you dont have anything like this happening on your machine.