| mirkoking96 10.09.2012 06:41 |
I just like to ask why link doesn't work: there's the page loading but it goes on and on and on... but the site doesn't arrive... It's just my PC or it's, maybe, a technical problem of the website?? D: |
| pittrek 10.09.2012 06:48 |
Works here perfectly |
| tomchristie22 10.09.2012 08:08 |
Server Error for me.. |
| pittrek 10.09.2012 08:40 |
Still works for me, even after CTRL-F5 |
| Micrówave 10.09.2012 09:31 |
Doesn't work here either. |
| The Real Wizard 10.09.2012 10:48 |
Hasn't worked for me for a week, at least. |
| Gaabiizz 10.09.2012 11:17 |
not work for me , until a few days ago worked fine |
| pittrek 10.09.2012 11:27 |
Strange, that looks like a server config problem, I am now in a different town and a different computer and still have full access. Did somebody email Martin ? |
| Marknow 10.09.2012 12:01 |
Working fine for me here in Ireland. |
| Ale Solan 10.09.2012 12:14 |
I can only enter the site using an online proxy like link |
| 1sharppencil 10.09.2012 13:36 |
no problem here |
| Lord Fickle 10.09.2012 15:38 |
Works fine for me in UK. |
| The Real Wizard 10.09.2012 16:15 |
Maybe he's using Godaddy.com ? They've been hacked and millions of sites are down. edit: just checked whois.com, and that's not the issue. Hope he works it out. |
| A Word In Your Ear 10.09.2012 17:24 |
Just tried it. I'm using "Mozilla Firefox" & it did not work. Just gone upstairs & used my daughters PC, she uses "IE8" works fine on hers. Just tried my Phone, works fine on my phone too. Gonna look at my settings on my PC. |
| AdamMethos 10.09.2012 18:47 |
I'm in Canada and it doesn't work with Firefox on my PC or Safari on my phone. I have visited Queen Concerts in the past on both my PC and phone so I don't think it's a browser setting issue. |
| inu-liger 10.09.2012 22:18 |
It works fine for me! |
| Mr. Scully 11.09.2012 01:46 |
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... |
| inu-liger 11.09.2012 02:26 |
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 |
| Mr. Scully 11.09.2012 02:48 |
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. |
| Mr. Scully 11.09.2012 03:52 |
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). |
| beautifulsoup 11.09.2012 07:00 |
Not working for me. |
| GratefulFan 11.09.2012 07:38 |
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. :) |
| pittrek 11.09.2012 07:50 |
.cz is actually a czech domain, not Ukraine :-) |
| GratefulFan 11.09.2012 07:58 |
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! :) |
| GratefulFan 11.09.2012 08:13 |
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. |
| Marcos Napier 11.09.2012 18:39 |
when in doubt, try link |
| AdamMethos 11.09.2012 20:21 |
I tried downforeveryoneorjustme.com and it said Queen Concerts is up. But I'm still not getting anything. |
| Mr. Scully 12.09.2012 05:50 |
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) |
| GratefulFan 12.09.2012 07:31 |
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. |
| GratefulFan 12.09.2012 08:04 |
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 link Tracing route to link [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. |
| GratefulFan 12.09.2012 09:08 |
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 link 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. |
| AdamMethos 12.09.2012 11:41 |
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 link [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. |
| GratefulFan 12.09.2012 11:48 |
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? |
| AdamMethos 12.09.2012 12:08 |
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 --- |
| GratefulFan 12.09.2012 12:26 |
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 |
| GratefulFan 12.09.2012 12:26 |
Double post. All this thinking has made me need salt and vinegar chips. Off to forage. |
| Mr. Scully 12.09.2012 16:38 |
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). |
| GratefulFan 12.09.2012 16:53 |
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. |
| GratefulFan 12.09.2012 17:01 |
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. |
| GratefulFan 12.09.2012 17:49 |
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. |
| AdamMethos 12.09.2012 17:56 |
Tried from home. Still not getting past my ISP! Tracing route to link [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 link [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. |
| GratefulFan 12.09.2012 18:05 |
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 |
| inu-liger 12.09.2012 23:19 |
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. |
| bootLuca 13.09.2012 03:59 |
I can't access at the site I have this error: "the server link is taking too long to respond" |
| Ozz 13.09.2012 06:54 |
Unreachable in Australia. Traza a la dirección link [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 |
| Mr. Scully 13.09.2012 15:41 |
The hosting is actually not bad ;-) We may have expensive phone calls but when it comes to Internet, I had a 50 Mbit connection when tons of people in the western world were still on modems ;-) I think all this just confirms that there are a couple of important junctions that block these servers and as a result the site might be unavailable for half of the planet (maybe more, maybe less). I think we just have to wait... |
| The Real Wizard 14.09.2012 13:58 |
But what has changed in the last few weeks? Am I missing something? |
| GratefulFan 14.09.2012 15:07 |
The whole thing completely fascinates me. What has happened? From a technical standpoint, what is going on? In Canada, why is Bell/Eastlink/Rogers routing killing this right out of the gate and Shaw letting it out just fine? What's Telus doing? Is this like an optional blacklist? Or has something broken and the propagation of the fixed routes is just taking longer for some services than others? What is the scope of this? I'm hoping everybody who has posted failed traceroutes will post them again once things are back up. I'm just terribly curious about the technical details behind this, and what the point of failure(?) was. The interwebs are supposed to be drunk with redundancy and yet this is impacting at least 5 or 6 countries based on this little QZ sampling alone. Weird and interesting. |
| cjpew 14.09.2012 16:08 |
To answer above question about Telus - my ISP is Telus - I haven't been able to get to the site for days. |
| Mr. Scully 14.09.2012 16:28 |
I believe it's some kind of blacklist that is shared among a lof of providers... but I have never experienced anything like that before. It's like if some routes were dead ends while some kept working normally. Even the redundancy doesn't help for some reason. Weird situation... please let me know if things return back to normal. |
| Mr. Scully 15.09.2012 02:42 |
Btw. the stats show a decrease in the amount of visitors by about 20%. |
| thomasquinn 32989 15.09.2012 03:58 |
Mr. Scully wrote: Btw. the stats show a decrease in the amount of visitors by about 20%.Interesting. That means some people can still log on. Any similarities between their IP-addresses, e.g. distinct geographic regions? |
| Marcos Napier 15.09.2012 15:22 |
The fact that downforeveryone reports it as being available shows that the connection is being cut somewhere. It might be a DNS caching/propagation issue in the middle of the way. It's not uncommon to have connection issues to a specific backbone either. The IP used by the site might be in a blacklist too, considering a lot of IPs are shared by a lot of different domains it could be sharing the IP with a spam site, for example, and it's being blocked somewhere. I remember this page that used to list all the sites/domains hosted in the same IP/server, and it was very useful to find problems: link You just have to try some of these sites in the list, and if they work, the problem maybe is in the configuration of your own domain, not the server. In a similar situation, when you register and start a domain name hosting, sometimes it takes up to 72 hours for it to appear in certain places (depending on how often they update their DNS list) while in others it appears nearly immediately, but the IP responds to ping and tracert, just the page isn't displayed. |
| Marknow 15.09.2012 15:26 |
Clear your cache and cookies folks, might help. |
| Marcos Napier 15.09.2012 15:43 |
Just tested a bunch of these domains hosted in the same IP, all have the same problem. It's more serious than cache and cookies. |
| pittrek 16.09.2012 04:15 |
thomasquinn 32989 wrote:As I wrote I could access the site from both Slovakia and Austria (Vienna)Mr. Scully wrote: Btw. the stats show a decrease in the amount of visitors by about 20%.Interesting. That means some people can still log on. Any similarities between their IP-addresses, e.g. distinct geographic regions? |
| GratefulFan 16.09.2012 09:10 |
Mr. Scully wrote: Btw. the stats show a decrease in the amount of visitors by about 20%.Interestingly, when I ran thinline.cz through dns.squish.net just now 20% of the traffic is the figure that was noted to have failed. All through one of five top level .cz DNS resolvers: d.ns.nic.cz. Other DNS traversal tools also report failures there. The timeouts we're experiencing would make sense if some cached DNS records were still trying to refer to a failing resolver. And it would happen early in the process as the the top level domains are the next step after the local and root servers. This is where one expects that some of the redundancy would automatically kick in though? And would the local servers be caching records for full hostnames, or just the next step top level domains? If the latter all .cz domains should fail, which they're not. However when I put in the URL of another Czech web hosting company, the report was not the same, suggesting there is some granularity in the records, though it also had a 20% failure through the aforementioned d.ns.nic.cz as well. Don't know enough about DNS to know for sure but the consistent failure of that one .cz resolver across multiple dns traversal tools, the early failure of the traces, and the 'matching' figures of about 20% are interesting. |
| GratefulFan 16.09.2012 09:35 |
Also forgot to mention that 91.239.200.5 does not show up on any of the blacklist checker tools I tried, which was several. |
| Gregsynth 22.09.2012 14:09 |
link Here's how to get to the site! |
| Mr. Scully 23.09.2012 16:07 |
It's easy to get to the site via proxy servers. But that's not a solution :-) Still no improvement? |
| GratefulFan 23.09.2012 23:04 |
I've been able to get to it from my mobile service since the middle of last week. Still no luck from my home/work network. So things may be resolving, if surprisingly slowly. :) |
| The Real Wizard 23.09.2012 23:28 |
Still not working here, neither PC nor Android. |
| Missreclusive 23.09.2012 23:35 |
Same here, can't get it on laptop or Android |
| Mr. Scully 24.09.2012 17:47 |
Don't know if it's related but IP address 37.0.52.38 is causing me hundreds of thousands of hits (+ traffic). Could be one of the reasons for the blacklisting? |
| 99jaystang 24.09.2012 18:55 |
Working now for me here in Cambridge Ontario Canada (with Bell Internet) working with Chrome,firefox,safari, with a mac laptop. All good :) |
| GratefulFan 25.09.2012 11:39 |
99jaystang wrote: Working now for me here in Cambridge Ontario Canada (with Bell Internet) working with Chrome,firefox,safari, with a mac laptop. All good :)The service I now have it working on is Bell Mobility. Initially it was only a Shaw user as far as Canadians reporting here that could get through and now us with both the mobile and home arms of Bell. I think this will come back up by carrier and as far as Canada goes it's hard to imagine Telus and Rogers can be too far behind. With Bell that will be the big three that will cover most of us. |
| GratefulFan 25.09.2012 13:06 |
Now up on an Eastlink connection at work, which is also my home conduit to the internet due to the need for me to support work systems from home combined with the lack of a VPN for the moment. So I'm good everywhere now. :) |
| PiotreQ 25.09.2012 13:28 |
Working fine now, finally (Poland) :-) |
| cjpew 25.09.2012 14:12 |
Telus in Canada now working :) |
| The Real Wizard 25.09.2012 14:25 |
Mr. Scully wrote: Don't know if it's related but IP address 37.0.52.38 is causing me hundreds of thousands of hits (+ traffic). Could be one of the reasons for the blacklisting?Looks like you figured it out ! Good job. |
| Mr. Scully 26.09.2012 02:48 |
Actually the IP address I mentioned was just an ordinary attack, nothing special. The reason why it probably works now is that I complained at my hosting company repeatedly and they forwarded my complaints to the international transit operators who probably blacklisted our server. So it looks like the blacklist has been removed, at least for a majority of internet traffic. |
| bootLuca 26.09.2012 03:52 |
yes, it works! :) |
| pittrek 26.09.2012 06:12 |
Mr. Scully wrote: just an ordinary attack, nothing specialLOL, I love your optimistic approach :-) |
| The Real Wizard 26.09.2012 09:45 |
^ what he said. |