After a lot of digging, it seems there was a little misconfiguration with some DNS settings that were changed after the whole CloudFlare debacle and have caused googlebot to have problems connecting to our site and, thus, indexing it.

I've made some adjustments to hopefully get things back in working order. It will take a little bit before the changes can have any effect, so we soon shall see.

Thank you.

Hi,

Sorry about the bad experience. I did want to advise that the attacks are generally not against CloudFlare proper, but are generally attacks directed against client sites, and we are working on some network solutions to greatly reduce this problem in the very near future (testing and building out solutions now). While you are indeed correct in stating that the rest of the network is up when one datacenter is having an issue, we most certainly do realize that it is little consolation when any of your visitors hitting that datacenter are having a problem accessing your site.

Comment hidden because you are ignoring dag. (show it anyway)

We definitely lost some traffic during that failed experiment, but not permanently. Alexa is a bit delayed and kind of inaccurate IMHO. We seem to be firing on all cylinders again now though. CloudFlare is definitely on my shit list. Reminds me I must go tweet about this. >> ^eric3579:

It seems site traffic has been down quite a bit this week. Was curious if the CloudFare was responsible and if you think we will be getting it back. From the one month traffic chart on Alexa, it looks like we have lost 40% to 50% of our avg. monthly traffic this week. Just very curious. @lucky760 @dag

Comment hidden because you are ignoring dag. (show it anyway)

Guys - although we are moving off of CloudFlare immediately - it may take a day or more for all the changes to be propagated out through the net.