What appened to Queen Concerts' website?

It works fine for me!

Can anybody show me the screenshot, what error it exactly is? 404 Not Found or something else? Is it displayed directly or after some time? I'm not aware of any problems and the site works for me. Server error could be caused by incorrect htaccess but then it wouldn't work for anybody. Strange...

Could be that the routing is fooked?

If anyone knows how to do a tracert and copy-paste the results, I'd suggest they PM it to Mr. Scully

Barbara just emailed me. Apparently it's not the typical "404 Not Found" message but it says "Page cannot be displayed". Could be htaccess... or something else.

OK, the only reason we can think of is that there has been a huge attack on some webservers (incl. the one with QueenConcerts) about five days ago and as a result some "transit" internet operators are probably blocking this particular path/area. Apparently we have to wait until the block expires - which can take days or even more (and there's nothing we can do about it).

Not working for me.

Had a chance to try three different networks this morning using trace route on the domain and all get out of North America and end at an address in the Ukraine: 91.239.200.5 (able.thinline.cz). If that helps. :)

.cz is actually a czech domain, not Ukraine :-)

Multiple traces are reporting 91.239.200.5 as being in Ukraine, and resolving to able.thinline.cz. I don't think that kind of thing is particularly unusual. But definitely not a global network expert! :)

I can't ping 91.239.200.5 so they may simply be blocking ICMP traffic, or some subset of it. So those traces may not be that helpful.

when in doubt, try http://www.downforeveryoneorjustme.com/

I tried downforeveryoneorjustme.com and it said Queen Concerts is up. But I'm still not getting anything.

GratefulFan - and does it work for you or not? :-) thinline.cz is indeed my hosting company so the address is correct (and it's Czech Republic, not Ukraine)

LOL @ me. Yes, that would have been helpful information! No, it doesn't work for me. The imprecision on that 'Ukaraine' location may in fact mean that hop is in fact failing and it is instead relying on lookup information. Graphically it lands in the geographic centre of Ukraine, which often means "I dunnno, somewhere around there". Some traces I do credit a major routing system right in the geographic middle of Canada, likely at some polar bear's house. I don't think so! Anyway, let me try it via command line on my Windows PC...that might give a better view of things. I have a quick meeting but will get back to the thread shortly.

Okay...indeed a better view of things.  Clipped out the first few local hops so I'm not inviting the world to hack my work servers (Ha ha) and this is what remains.  Local major route followed by an address in Washington DC (purportedly) and then...nothing.   Onthe iOS device the 'Ukraine' location follows immediately after the DC location with the precise number of ms in hop time echoed for both, so 'Ukraine' now seems almost certainly to be a failed, partial or rejected communication only.  Again, your ISP could simply be blocking this kind of traffic as it can be used in crude DOS attacks, so it all may mean nothing.  But if they aren't, you might show this trace to them as evidence that something is going wrong for some users trying to access your site.  Again, tried it on three distinct and unrelated networks with no positive result.

tracert www.queenconcerts.com

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

   5    24 ms   210 ms     7 ms  10.10.10.54
  6     8 ms     *        *     gi1-19.mag02.yyz02.atlas.cogentco.com [38.112.1.121]
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.