|
|
|
|
|
by regal
4718 days ago
|
|
Had the opposite experience - no change in loading speeds when our ~600K visitor / month site switched to CloudFlare in March of this year, but we soon started experiencing long website downtimes where our server was running fine but CloudFlare was not serving our site, despite paying $200 a month for "always online", which the site clearly was not. All IPs were whitelisted with our host and everything else CloudFlare recommended; all CloudFlare would do was examine the site after it had come back online (following hours of downtime) and say, "Everything looks fine to us!" We finally left, after months of this, and have had no problems with downtime since. I really wanted CloudFlare to work - I was really excited about it when I signed us up. But at least for a bigger site with heavier traffic that relies on being up as much as possible, I can't say I'd recommend it until it straightens out its downtime issues (especially when paying for "always online"). |
|
Particularly for relatively low volume sites which have a short burst in traffic on occasion, CloudFlare can keep those sites running during the peaks.
I think the most important thing is transparency and correct expectations. If they set clear expectations, and they are transparent about how well they are meeting them, then it just comes down to delivery.
I found their status dashboard here: https://www.cloudflare.com/system-status. Unfortunately it doesn't show much long-term historical performance, it would be nice to see 30 days even 180 days of performance history to really evaluate them.
regal, did you find that when you had downtime on your site that it was reported in their status dashboard, and that was an accurate depiction of the service they provided? I think the worst-case scenario is getting hit with unreported downtime, because that brings up all sorts of questions.