If it helps here's my trace route, my hub site is Hayes in the western outskirts of London.
Tracing route to evanscycles.com [188.8.131.52]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 17 ms 10 ms 16 ms haye-core-2a-xe-233-0.network.virginmedia.net [184.108.40.206]
4 * * * Request timed out.
5 11 ms 10 ms 8 ms m686-mp2.cvx1-b.lis.dial.ntli.net [220.127.116.11]
6 19 ms 9 ms 16 ms 18.104.22.168
7 114 ms 114 ms 113 ms ldn-bb4-link.telia.net [22.214.171.124]
8 95 ms 98 ms 101 ms nyk-bb3-link.telia.net [126.96.36.199]
9 114 ms 121 ms 113 ms chi-b21-link.telia.net [188.8.131.52]
10 115 ms 113 ms 115 ms rackspace-ic-134354-chi-b21.c.telia.net [184.108.40.206]
11 * * * Request timed out.
12 97 ms 96 ms 93 ms be42-corea.ord1.rackspace.net [220.127.116.11]
13 115 ms 114 ms 115 ms corea-core6.ord1.rackspace.net [18.104.22.168]
14 93 ms 102 ms 95 ms core6-aggr1501a-6.ord1.rackspace.net [22.214.171.124]
15 123 ms 115 ms 113 ms 126.96.36.199
Oh for crying out loud, I've just spent 40 minutes typing up a reply explaining in some detail that what gets returned if you lookup evanscycles.com (or .co.uk) is the domain literal address and always responds to pings and traceroute (it's one of Rackspace's hosting platforms BTW), but that isn't the same as www.evanscycles.com which a DNS lookup of returns a cname address of sni.ssl.evanscycles.com.c.footprint.net which itself resolves to 188.8.131.52 (at least for me at the moment) and footprint.net is Level 3 Internet's content delivery network.
Never mind though, my fault for being too long-winded with my replies!
I doubt anyone will be able to traceroute to it though, the address(es) wont respond to ICMP or UDP packets, anyone with a linux (probably any unix distro) can use tracetcp which works by SYN and SYN/ACK packets and a webserver has to respond to these or it can't serve webpages or anything else really.
Not that this helps get people connected in any way, shape or form, the website always works for me (south-east London / Kent border), it could be a VM routing issue or Level 3 have a couple of dodgy nodes in the CDN which don't have a copy of the site and if you get connected to one of those then bad luck!