It looks to be a router issue to me somewhere based on your trace route, probably the same router that's been causing trouble for lots lately. If you were banned from x10, you'd at least see Dallas-datacenter.com in the trace route rather than get an error like that, but wouldn't be able to access the servers.
I don't get that router on route to x10's datacenter, so here's me running a trace route to my site on Absolut. I'm up in the north-east of the US.
Tracing route to seansite.dyndns.org [74.86.133.24]
over a maximum of 30 hops:
1 3 ms 1 ms 1 ms 192.168.2.1
2 1 ms 1 ms 1 ms dsllanrouter [192.168.1.1]
3 5 ms 5 ms 6 ms [DSL Central Office]
4 18 ms 17 ms 16 ms so-1-1-0-0.CORE-RTR1.mycity.verizon-gni.net [xxx.xxx.xxx.xxx]
5 27 ms 26 ms 26 ms 130.81.20.104
6 28 ms 28 ms 29 ms 0.so-4-2-0.XT1.NYC8.ALTER.NET [152.63.10.1]
7 30 ms 30 ms 31 ms 0.so-4-0-0.XL3.DFW13.ALTER.NET [152.63.101.197]
8 34 ms 34 ms 33 ms 0.so-6-0-0.GW3.DFW13.ALTER.NET [152.63.100.73]
9 40 ms 40 ms 44 ms internapGIGE1-gw.customer.alter.net [65.208.15.2.30]
10 48 ms 46 ms 45 ms border3.tge3-1-bbnet1.ext1.dal.pnap.net [216.52.191.22]
11 48 ms 48 ms 48 ms softlayer-8.border3.ext1.dal.pnap.net [216.52.189.30]
12 50 ms 50 ms 50 ms po56.fcr03.dal01.dallas-datacenter.com [66.228.118.190]
13 55 ms 55 ms 60 ms x10hosting.com [74.86.133.24]
Trace complete.
There is no need for me to trace your site Twinkle as it does through the same routes, except the ending destination has a different IP. Otherwise, your site is loading up fast here.
