Looks like we’re too popular…
Well, folks, it seems that you have made the new ScaleDown.ca so popular that we have been experiencing some technical difficulties since the launch. I haven’t been able to log on yet and I know many others are experiencing the same problems.
Stay with us. We’ll iron this out. And if you know of someone who is having problems (obviously, you’re not - you’re here!) please comfort them in the knowledge that we have the world’s leading experts working out the bugs as we speak.
All will be OK shortly.
Post Feedback
This could be some of the problem: On you last blog before the transformation you gave the link as http://www.scaledown.ca
Whereas if you look up to the correct URL it is http://scaledown.ca/
Urbanrat
We can rule this out. The site is still accessible no matter which way you type in the domain address, www or not.
The majority of websites do not require the WWW in front.
If anyone’s wondering why the four Scaledown founders haven’t said anything in two days it’s because their access has been “blocked” for some reason no one has been able to ascertain yet. Chris asked me to pass this along in the comments section on this post.
It appears some are able to access this site, others not. The possible explanation I was given by someone in-the-know is that the DNS changes probably haven’t propagated to all caching DNS servers yet. At this point I am able to get through obviously, but this was not the case for the previous 24 hours. Other Cogeco subscribers - including the Fab Four - still cannot get on. It appears some MNSi subscribers are getting through as well, while others are not. Hopefully by this evening all the DNS servers will be updated and we can return to normal operation.
I’m baaaack! It appears that some techincal magic from our hosting company followed up with an angry phone call or two with my ISP has get me back online.
For those who know someone who is still blocked, have them clear their cache in Internet Explorer, Safari, Mozilla or whatever other browser they are using. Clear everything except the passwords (if you are using IE7) then close out IE and relaunch. This should help, or at least clean everything out in preparation for getting the DNS updates that are slowly propagating through the net.
Thanks for everyone’s patience — the timing of this techno-blooper could not have been worse, but we’re hopeful that this will be the last of our problems.
Josh
So is your blog clock set for GMT or something? I notice the time stamps for posts now are several hours ahead. Or has it been that way all along? For example, I’m submitting this post at 9:38 pm