Fernier - let me address some things in your latest posts. First, we use Amazon S3, not EC2 - pretty big difference there.

Secondly, we have multiple access points that we test internally and externally. Yes we have a direct line that is supplied by a carrier within in our data center, but we also have connectivity through Comcast business that we test on also. Ironically, we have no issues with that line as residential users are having with Comcast.

Personally, I have Charter internet, a Verizon wifi card and AT&T wireless that I'm able to test on from home. I don't share any of the issues from any of these connections that you all are reporting in this forum. But as you pointed out, location and the route from your location to the destination that your ISP takes is a critical difference. Also, the trace route request timeout doesn't necessarily indicate a problem since it is based upon ICMP settings in the firewall. Our direct line (internal connection as you put it) resolves all of those requests just fine. You should be able to ping renderosity.com without any problems.

I'm able to ping from all of my connection options without issue. But when I test ping from dnsreport.com tools it doesn't resolve. Below is a link (only good for 48 hrs) to a trace route I performed with dnsreport.com which shows 2 different routes, from Denver and from Austin. Both resolve completely without any request timeouts just as I am able to do with the 3 options I have access to, which indicates to me that the issues are ISP and/or route specific in some way.

http://bit.ly/17Zwkd3