I hope some one has some ideas and/or experience with my problem. I help run animereviewed.info we just recently moved to a new host. Our new host is Nexgenhosting.com . We got things set up after a few problems. Anyways my issue is in the process of restoring all our files to the new host, the host's site and animereviewed.info started timing out. I have no way to view them without using a proxy. This of course is limiting when you are trying to upload and edit files. I talked with the host and they told me it was my end and to contact the ISP. I of course contacted my ISP, Comcast. They had me run trace route. I did this and they informed me it wasn't their end. The ISP wasn't helpful at all I do wanna mention. So I have submitted an email to my host. In the mean time I am hoping to get some ideas or advice. Here is the traceroute results: Tracing route to animereviewed.info [69.4.230.17] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.1.1 2 * * * Request timed out. 3 12 ms 25 ms 20 ms ge-1-4-ur01.corvallis.or.bverton.comcast.net [68.87.216.209] 4 10 ms 12 ms 12 ms te-8-3-ur03.salem.or.bverton.comcast.net [68.87.216.54] 5 26 ms 22 ms 18 ms te-7-2-ar01.beaverton.or.bverton.comcast.net [68.85.243.137] 6 15 ms 16 ms 25 ms te-0-4-0-4-cr01.portland.or.ibone.comcast.net [68.86.90.241] 7 33 ms 31 ms 38 ms pos-0-6-0-0-cr01.sacramento.ca.ibone.comcast.net [68.86.85.201] 8 42 ms 30 ms 30 ms pos-0-7-0-0-cr01.sanjose.ca.ibone.comcast.net [68.86.85.78] 9 36 ms 81 ms 34 ms 68.86.88.166 10 109 ms 109 ms 133 ms ashbbbrj02-ae0.0.r2.as.cox.net [68.1.0.221] 11 108 ms 115 ms 121 ms border1.te7-1-bbnet1.wdc008.pnap.net [216.52.127.36] 12 122 ms 114 ms 131 ms te1-1.cer01.wdc01.washingtondc-datacenter.com [66.151.100.66] 13 125 ms 110 ms 108 ms te8-1.npr01.wdc01.washingtondc-datacenter.com [208.43.118.142] 14 111 ms 115 ms 109 ms te8-8.fcr01.wdc01.washingtondc-datacenter.com [208.43.118.174] 15 * * * Request timed out. 16 * * * Request timed out. 17 * * * Request timed out. 18 * * * Request timed out. 19 * * * Request timed out. 20 * * * Request timed out. 21 * * * Request timed out. 22 * * * Request timed out. 23 * * * Request timed out. 24 * * * Request timed out. 25 * * * Request timed out. 26 * * * Request timed out. 27 * * * Request timed out. 28 * * * Request timed out. 29 * * * Request timed out. 30 * * * Request timed out. Trace complete. Code (markup):
From your trace, it can reach SoftLayer (the vendor of your host). But your server blocks ICMP. You can ask them to do trace route back to your IP to see if there is any issue.
You're definitely within 1 or 2 hops of your destination. This is typically what it should look like: Tracing route to mycohost.net [208.43.82.184] over a maximum of 30 hops: 1 7 ms 8 ms 7 ms 10.85.128.1 2 7 ms 7 ms 7 ms osr01croy-v15.inet.ntl.com [62.30.112.197] 3 11 ms 10 ms 9 ms bre-bb-a-ge-300-0.inet.ntl.com [195.182.178.82] 4 18 ms 7 ms 7 ms bre-bb-b-ae0-0.inet.ntl.com [213.105.174.226] 5 12 ms 10 ms 9 ms 195.50.91.129 6 21 ms 17 ms 18 ms ae-32-56.ebr2.London2.Level3.net [4.68.117.190] 7 13 ms 28 ms 10 ms ae-1-100.ebr1.London2.Level3.net [4.69.132.121] 8 27 ms 19 ms 18 ms ae-2.ebr1.Paris1.Level3.net [4.69.133.93] 9 100 ms 17 ms 17 ms ae-1-100.ebr2.Paris1.Level3.net [4.69.133.82] 10 104 ms 93 ms 101 ms ae-44.ebr2.Washington1.Level3.net [4.69.137.62] 11 97 ms 94 ms 104 ms ae-92-92.csw4.Washington1.Level3.net [4.69.134.158] 12 97 ms 98 ms 93 ms ae-43-99.car3.Washington1.Level3.net [4.68.17.197] 13 99 ms 99 ms 97 ms unknown.Level3.net [63.210.59.238] 14 96 ms 100 ms 93 ms te1-1.cer01.wdc01.washingtondc-datacenter.com [66.151.100.66] 15 95 ms 94 ms 95 ms te1-1.cer01.wdc01.washingtondc-datacenter.com [66.151.100.66] 16 94 ms 94 ms 95 ms po1.fcr01.wdc01.washingtondc-datacenter.com [208.43.118.134] 17 94 ms 96 ms 95 ms dual.mycohost.net [208.43.64.18] 18 99 ms 96 ms 96 ms beta.mycohost.net [208.43.82.184] Trace complete. Code (markup): Contact your host, and tell them to contact SoftLayer with your IP. It might have been blocked as part of a mask or something. Jay
Still no luck. My host said everything on their end was fine. It was suggested to try resetting my IP Address. I did this and still nothing. Anything else anyone can think of? Going nuts trying to run a site I can't see (well I can use a proxy but can't really upload or edit anything easily)..
I assume so. I asked him to do it. I never got the results of the traceroute so I emailed them and asked for them this time. I guess they are in contact with their host. This is getting frustrating I will say that!
Hi, When you 'reset' your IP, did you change it or just flush the data / reboot, etc.? Also, can you try tracerouting/visiting mycohost.net to see if you can access it. If you can, it is probably your hosts server. If you can't, SoftLayer has more than likely blocked you at the router level. Jay
Yeah I can visit http://mycohost.net/. As far as my IP, I /released it and then /renew it. So you think then it maybe my host's server?
Well I am just thinking about getting new hosting. My current hosting just switched owners maybe better than waiting for the host to resolve this.