What appened to Queen Concerts' website?

Just for fun tried on my Android phone on external 3G network and it failed, again at a cogentco.com routing point. Might be interesting to see if this is a commonality specific to those of us failing or just a reflection of the fact that Cogent is a big player in global networks. Anybody who can get to a command prompt in Windows can easily run a trace. Click Start button, choose run and type cmd in the run box. Enter and you should pop up a little black box that you can type in. Type tracert www.queenconcerts.com and hit enter. It should spit back info similar to my past above. X out the box to close as normal and you'll be back to your Windows desktop.

Tried traceroute from my work computer and strangely it's not even getting out of the internal network. I'm posting this from my work computer, so my Internet is working fine, and I've visited Queen Concerts from my work computer in the past. So my company is now blocking the IP address of Queen Concerts for some reason?

Tracing route to www.queenconcerts.com [91.239.200.5]
over a maximum of 30 hops:

5 2 ms 1 ms 1 ms 192.168.218.250
6 1 ms 1 ms 1 ms 192.168.216.65
7 2 ms 1 ms 1 ms 192.168.248.81
8 2 ms 1 ms 1 ms 192.168.248.90
9 2 ms 2 ms 1 ms 192.168.230.18
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.

All this crap is endlessly complex. It could be that your company blocks ICMP traffic out or something. Maybe you could try and trace some other external site you know you can get to? Anything. Queenzone? If you still can't get past the subnets you'll know it's a broader issue. Can you use your phone on an external network?

Oh you're right. Traceroute is timing out with QZ too. So weird because I work in IT (database programming) and have used traceroute in the past (though not recently).

Traceroute from my phone on the Fido/Rogers network:

Route to queenconcerts.com (91.239.200.5), 30 hops max
 1  74.198.28.241  84 ms  109 ms  71 ms
 2  timeout timeout timeout
 --- end ---

I work in IT/Database Programming too. :) Man, this is failing so early in transit across so many different networks. It's interesting. Your last phone address still belongs to Rogers! My Bell phone got a little farther, but not much. Ditto for an Eastlink network. Mr. Skully's earlier hypothesis about having to wait for blocks/dumps to expire is probably exactly right. Terribly curious what's happened though, and the actual scope. Still possible that Mr. Skully's ISP is rejecting traceroute traffic, or any other hop along the way for that matter, and this is not that informative after all. Would love to see a successful traceroute from somebody who can reach the site. Because I'm a geek. Obviously. Hadn't fully let that on board until this thread. Thanks queenconcerts.com. :P

Double post. All this thinking has made me need salt and vinegar chips. Off to forage.

Thanks, guys. Well, I can tracert my own site without problems:

1 < 1 ms < 1 ms < 1 ms 192.168.0.1
2 < 1 ms < 1 ms 1 ms router-w2.pilsfree.czf [10.109.159.3
3 2 ms 1 ms 1 ms 10.77.184.105
4 3 ms 2 ms 2 ms router-skvrnany-mach3.pilsfree.czf [10]
5 2 ms 2 ms 2 ms router-nfx-2.pilsfree.net [81.201.60.2
6 4 ms 5 ms 5 ms l3sw-nfx2.nfx.cz [81.201.48.195]
7 7 ms 5 ms 4 ms nix4.vshosting.cz [91.210.16.151]
8 5 ms 5 ms 4 ms bbsw1-ttc.vshosting.cz [78.24.8.19]

(The first IP being my router, the next four IP's being my provider, the last three IP's being the route to the hosting company).

Interesting. I can successfully get to your last entry in 21 hops. But still not to queenconcerts.com. Dies in what seems to be still North America.

More info...tried the 7th hop as well because it starts with 91. - the same as the 91.239.200.5 destination that resolves to abel.thinline.cz and queenconcerts.com and fails. It failed. 6th hop was fine. So 6 and 8 good, 7 fails.

Oh whatever! :) I don't know enough to extract anything insightful from any of this. I was hoping to learn something but I just don't have enough information. Bottom line is there seems to be a few routers out there that are either confused or sulking, and at pretty fundamental junctions in the Internet. Sorry your site is caught in it Mr. S. Hopefully fixes will propagate within hours or days. I'll check periodically and let you know when it's up if that hasn't been made clear by others.

Tried from home. Still not getting past my ISP!

Tracing route to www.queenconcerts.com [91.239.200.5]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 2 ms 1 ms 1 ms cp66-203-194-1.cp.telus.net [66.203.194.1]
3 1 ms <1 ms <1 ms cp66-203-195-205.cp.telus.net [66.203.195.205]
4 1 ms 1 ms 1 ms 154.11.63.101
5 <1 ms <1 ms <1 ms 207.219.15.58
6 1 ms <1 ms <1 ms toroonxngr00.bb.telus.com [154.11.6.86]
7 11 ms 11 ms 14 ms 75.154.223.182
8 * * * Request timed out.

But QZ works:

Tracing route to www.queenzone.com [209.62.8.130]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 1 ms 1 ms 1 ms cp66-203-194-1.cp.telus.net [66.203.194.1]
3 1 ms <1 ms <1 ms cp66-203-195-201.cp.telus.net [66.203.195.201]
4 1 ms 1 ms 1 ms 154.11.42.5
5 <1 ms <1 ms <1 ms 207.219.15.58
6 1 ms <1 ms 1 ms toroonxngr00.bb.telus.com [154.11.6.23]
7 98 ms 98 ms 97 ms 154.11.12.201
8 98 ms 98 ms 102 ms eqix-ix.softlayer.com [198.32.176.207]
9 100 ms 100 ms 100 ms ae3.bbr02.eq01.sjc02.networklayer.com [173.192.1
8.242]
10 108 ms 108 ms 108 ms ae0.bbr02.cs01.lax01.networklayer.com [173.192.1
8.151]
11 108 ms 108 ms 108 ms ae7.bbr01.cs01.lax01.networklayer.com [173.192.1
8.166]
12 104 ms 88 ms 88 ms ae19.bbr01.eq01.dal03.networklayer.com [173.192.
18.140]
13 95 ms 95 ms 95 ms ae0.bbr01.sr02.hou02.networklayer.com [173.192.1
8.219]
14 96 ms 96 ms 96 ms po31.dsr02.hstntx2.networklayer.com [173.192.18.
235]
15 92 ms 92 ms 92 ms te4-1.car14.hstntx2.networklayer.com [74.55.252.
222]
16 92 ms 91 ms 91 ms ev1s-209-62-8-130.theplanet.com [209.62.8.130]

Trace complete.

Big dif is QZ is in North America. The Internet seems to be struggling with some delicate European relations as they relate to some dipshit hosting company in the Czech Republic! :P

PS I'm sure your hosting company is actually very, very nice Mr. S. :). I just feel the need to take my fruitless banging away at traceroute throughout the day out on something innocent and helpless. :P

1 * * * Request timed out.
2 13 ms 31 ms 15 ms 64.59.184.229
3 33 ms 31 ms 31 ms 66.163.78.70
4 28 ms 31 ms 27 ms rc2nr-ge15-0-0.wp.shawcable.net [66.163.73.185]

5 46 ms 47 ms 47 ms rc2so-tge0-15-5-0-1.cg.shawcable.net [66.163.77.
202]
6 57 ms 44 ms 55 ms equinix-chicago.r1.chi1.us.as5580.net [206.223.1
19.45]
7 70 ms 71 ms 84 ms tge2-3.ash01-1.us.as5580.net [78.152.34.138]
8 152 ms 149 ms 149 ms tge2-3.par02-1.fr.as5580.net [78.152.34.113]
9 157 ms 153 ms 153 ms tge1-2.fra01-1.de.as5580.net [78.152.34.61]
10 167 ms 182 ms 166 ms 78.152.44.13
11 165 ms 163 ms 180 ms kaora-gw.r1.pra1.cz.as5580.net [78.152.63.210]
12 168 ms 170 ms 167 ms tr-gts.kaora.cz [94.124.104.70]
13 173 ms 172 ms 174 ms vshgts.kaora.cz [94.124.104.90]
14 161 ms 161 ms 165 ms bbsw1-ttc.vshosting.cz [78.24.8.19]
15 163 ms 162 ms 161 ms abel.thinline.cz [91.239.200.5]

Trace complete.

I can't access at the site

I have this error:

"the server www.queenconcerts.com is taking too long to respond"

Unreachable in Australia.

Traza a la dirección www.queenconcerts.com [91.239.200.5]
sobre un máximo de 30 saltos:

1 1 ms 1 ms 1 ms NB304N.Home [192.168.1.1]
2 20 ms 17 ms 16 ms syd-sot-ken2-bras1-lo20.tpgi.com.au [10.20.20.41
]
3 16 ms 15 ms 16 ms syd-sot-ken2-csw2-tg-4-4.tpgi.com.au [202.7.214.
5]
4 16 ms 16 ms 22 ms syd-sot-ken2-crt2-ge-9-0-0.tpgi.com.au [203.29.1
35.173]
5 * * * Tiempo de espera agotado para esta solicitud.
6 * * * Tiempo de espera agotado para esta solicitud.
7 * * * Tiempo de espera agotado para esta solicitud.
8