Bhboyle Posted July 14, 2014 Report Posted July 14, 2014 Good morning folks. I am having troubles getting to the site from my home. I am in Toronto and my home provider is Teksavvy. I can get to the sites hositing provider (rackspace). My works web site is on Rackspace and I can get to it from home but not the wood whisperer site from home. I can ping the site from both work and home but when i open a connection in a browser at home the connection fails. It works fine from work using a different provider. Is anyone else having this issue? Based on the port 80 traceroutes, I am being blocked by Rackspace. This is a shame because I really enjoy the video segments but I cant watch them at home except on youtube and this does not have all the surrounding community. it looks like a routing problem to me... for what that's worth. Here is the port 80 traceroute from home... *******HOME********* traceroute to www.thewoodwhisperer.com (108.166.27.245), 30 hops max, 60 byte packets 1 unknown (172.16.0.1) 0.499 ms 0.655 ms 0.854 ms 2 10.125.228.129 (10.125.228.129) 5.422 ms 7.390 ms * 3 * * * 4 * * * 5 * * * 6 * * * 7 * if-5-0-0-5.core4.TNK-Toronto.as6453.net (63.243.172.25) 49.399 ms 49.317 ms 8 if-0-3-2-0.tcore1.CT8-Chicago.as6453.net (63.243.172.34) 23.697 ms 23.683 ms 25.588 ms 9 if-22-2.tcore2.CT8-Chicago.as6453.net (64.86.79.1) 27.214 ms 27.433 ms 27.250 ms 10 64.86.79.38 (64.86.79.38) 27.994 ms 27.971 ms 27.958 ms 11 coreb.ord1.rackspace.net (184.106.126.168) 31.457 ms 30.191 ms corea.ord1.rackspace.net (184.106.126.166) 31.140 ms 12 core2-CoreA.ord1.rackspace.net (184.106.126.127) 30.362 ms core2-CoreB.ord1.rackspace.net (184.106.126.131) 30.782 ms 27.347 ms 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * Port 80 traceroute from work... ******WORK ******* traceroute to www.thewoodwhisperer.com (108.166.27.245), 30 hops max, 60 byte packets 1 10.11.12.1 (10.11.12.1) 0.811 ms 0.789 ms 0.755 ms 2 * * * 3 * * * 4 * * * 5 * * * 6 * * ae4-597.cr2.ord1.us.nlayer.net (69.22.142.53) 22.906 ms 7 mpr1.ord7.us (206.223.119.86) 23.531 ms 23.899 ms 23.883 ms 8 ae4.cr1.ord2.us.above.net (64.125.28.49) 24.181 ms 24.068 ms 24.547 ms 9 ae9.mpr1.ord11.us.above.net (64.125.24.106) 24.718 ms 24.926 ms 24.696 ms 10 ae4.mpr1.ord5.us.above.net (64.125.24.94) 24.895 ms 24.356 ms 24.657 ms 11 208.185.125.6.IPYX-076520-ZYO.above.net (208.185.125.6) 26.243 ms 26.222 ms 26.214 ms 12 coreb.ord1.rackspace.net (184.106.126.138) 13.146 ms 13.405 ms 13.935 ms 13 core2-CoreA.ord1.rackspace.net (184.106.126.127) 14.258 ms core2-CoreB.ord1.rackspace.net (184.106.126.131) 14.003 ms core2-corea.ord1.rackspace.net (184.106.126.127) 13.954 ms 14 aggr101a-2-core2.ord1.rackspace.net (23.253.15.27) 13.925 ms 13.850 ms 13.648 ms 15 412061-web1.thewoodwhisperer.com (108.166.27.245) 14.533 ms 14.474 ms 15.541 ms Quote
Tpt life Posted July 14, 2014 Report Posted July 14, 2014 This happened with me and G S Haydon's blog. It turns out my ISP had recieved a blacklist request because someone used his IP to spam some people. All it took was a call to my ISP asking for a reevaluation. They pulled up his site from their location to verify it was a legit site and cleared it up right away. Quote
Bhboyle Posted July 16, 2014 Author Report Posted July 16, 2014 I will give that a try tonight. Thanks for the idea! Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.