A day does not seem to pass when something out of the ordinary happens to one of our web sites.
Sunday morning, I’m checking emails and tinkering with a few pages when one of them displays firstly without it’s stylesheet (no formatting), followed shortly thereafter by this message:
Error 1001 Ray ID: 1eee0e2757501d44 • 2015-05-30 23:00:27 UTC
DNS resolution error
You’ve requested a page on a website (www.onlymelbourne.com.au) that is on the CloudFlare network. CloudFlare is currently unable to resolve your requested domain (www.onlymelbourne.com.au). There are two potential causes of this:
Most likely: if the owner just signed up for CloudFlare it can take a few minutes for the website’s information to be distributed to our global network.
Less likely: something is wrong with this site’s configuration. Usually this happens when accounts have been signed up with a partner organization (e.g., a hosting provider) and the provider’s DNS fails.
CloudFlare Ray ID: 1eee0e2757501d44 • Your IP: 220.127.116.11 • Performance & security by CloudFlare
Now, that would all be well and good but the web site is not hosted on CloudFlare. To be fair, we did try CloudFlare albeit two years ago but a dramatic drop in search engine rankings (Google) soon put a stop to it.
We terminated the service, our rankings and traffic returned and frankly, I haven’t heard of CloudFlare until today.
Of course CloudFlare and others will say it has nothing to do with a drop in rankings, but our experience shows otherwise.
As to this latest error, it may very well be our host (Uber) have partnered with CloudFlare.
Yes, we have seen this CloudFlare error message before which does make us giggle somewhat. Here is a hosting-partner service promising to deliver 100% uptime hosting yet, CloudFlare error messages like this one tell another story. CloudFlare is likely to say the error is not a cause of their service but DNS and other reasons but the reality is, a web site is only as good as it’s host.