Cloudflare Reviews

We use it for DNS load balancing and WAF. 

The solution offers the flexibility to control configuration rules. 

The product needs to improve its automation. 

I have been using the product for two and a half years. 

I would rate the product's stability a ten out of ten since it never went down for me. 

I would rate the solution's scalability a ten out of ten since I didn't encounter any issues with it. 

The tool's setup straightforward. 

We have had ROI with the tool's use since it never gave us downtime and made us lose millions. 

I will rate the product an eight out of ten. Cloudflare is better than Cloud DNS. You need to start using Terraform along with Cloudflare. It will make your life easier without the need for manual creation. People usually thing they are going to use Cloudflare less but will end up using it more. 

We are using Cloudflare for the CDN for our applications. We deployed the solution as SaaS.

Cloudflare has many features. We can control profits, block attacks, and use a Global Location CDN. Additionally, we have a single console from which we can manage multiple tasks.

In the last two years, there has been a certain amount of downtime when using the VDM. Compared to other vendors and Cloudflare, there will be more downtime. We encountered this issue last year, and there have been a few occasions when Cloudflare was not accessible in certain regions, not all global regions or speed regions, but the website went down and it took Cloudflare a long time to restore the service.

I have been using the solution for two years.

We have experienced a few periods of downtime in the last two years, but the solution is generally stable.

The solution is scalable.

The initial setup is not difficult. All the steps for deployment are documented. We followed the step-by-step instructions for configuration.

The implementation was completed in-house by three employees.

I give the price a five out of ten.

I give the solution an eight out of ten.

Maintenance is easy; we receive a notification whenever maintenance is needed, as well as if a major restoration is required and what the likelihood of the system going offline will be.

I recommend Cloudflare.

For DDOS mitigation.

Provides peace of mind. We do not have to do things over and over, or double check their work, or worry about what could have happened due to a potential DDOS attack, if we didn't have protection.

Convenient

Ease of deployment

I think the APIs are a little bit hard for us to work with. The APIs could be more open so that we could integrate better with our SolarWinds or our monitoring solution.

Also, the reporting can definitely be improved to offer a lot more explanation on something that may have happened or has actually happened.

We have not encountered any stability issues.

I can't say, since we actually just deployed it. Our organization has already grown. For now, it serves our needs and manages are our expansion.

I'm quite comfortable with them so I don't see a big issue. We get fairly good support. The earlier issues that we had, some minor issues here and there, we got them resolved. They resolve our issues in a timely manner.

I think any DDOS solution is going to be complex. But we could actually follow the process and implement the solution. So it was not that complex, in that sense. And the tech support was there to provide feedback and support.

We didn't get any training other than you reading up materials and working with tech support.

I think the pricing is competitive.

I think as far as licensing is concerned it's pretty straightforward because it's based on domain. It's just that sometimes domains could be tricky with some customers.

We did review a couple of options, Tenable and a couple of others. We settled on Cloudflare because of price, support, and of course comfort in dealing with a vendor that was supporting us.

My advice would be to review exactly what you need and talk to different people to understand the potential advantages and pitfalls of implementing these kinds of solutions. Then identify the right product to meet your requirements.

From a solution perspective and from a product perspective I would give Cloudflare an eight out of 10. It's a reasonably priced solution that meets customers' needs and it's not too difficult to deploy.

We use Cloudflare DNS for websites when our clients want to have good protection. We can filter any traffic before sending it to their web page.

The most valuable feature of Cloudflare DNS is security.

The documentation could improve for Cloudflare DNS.

I have been using Cloudflare DNS for approximately eight years.

Cloudflare DNS is stable. I have not had an issue.

The solution is scalable. It can scale approximately 10 percent, it is limited only by how much money you want to spend on the increase.

I used this solution for large-sized companies because it is expensive.

I have used the support and they could improve.

I rate the support from Cloudflare DNS a six out of seven.

Neutral

The setup of Cloudflare DNS is easy. It is important to search for recommendations for best practices.

I rate the initial setup of Cloudflare DNS an eight out of ten.

The price of the solution is expensive.

I rate the price of Cloudflare DNS five out of ten.

I always advise my client to protect their websites and do DNS filtering.

I rate Cloudflare DNS an eight out of ten.

• DNS setup: Their DNS allows you to move control over DNS from your own server to a third party. This allows you to avoid running DNS locally that might consume resources or become unavailable if something happens with your local DNS server.
• DDoS protection: DDoS protection is what CloudFlare is known for. They are known to prevent DDoS attacks from taking down your server.
• Distributed content delivery (CDN): Their content delivery network is also a nice feature which can keep a website accessible even if your webserver goes down.

The setup and configuration is also easy to perform and their support is excellent.

This product has kept the site up while under an attack.

None that I can think of at this point. Their enterprise-level DDoS mitigation plans are costly but they are cost effective compared to any on-premises/distributed solutions that can go upwards of high six figures to implement. If a company like Sony can be taken offline for a week due to an attack, then there is not much that can be done by midsized/startups to prevent these attacks. For these companies, CloudFlare is ideal.

I have used it for five years.

I have not encountered any stability issues.

I have not encountered any scalability issues. You can move up to bigger packages if you are under a heavy DDoS attack.

Technical support is excellent.

I did not previously use a different solution. This was the first CDN company I have used.

Initial setup was simple enough for novices. They have plenty of documentation on their site.

Start off with their free plan. However, major DDoS protection is only provided with their paid plans. I would start with the free plan to test or to simply move DNS off your local server to them to free up resources.

Before choosing this product, I did not evaluate other options. They are an industry leader in CDN.

If you need your website accessible at all times, consider going with them.

I use this for DNS for many of my former clients and personal sites. When using services like Heroku, Cloudflare is very useful for CNAME flattening. I also use it for their end-to-end SSL with TLS authentication on nginx for securing servers. 

The second major use case is as a CDN where I will push logic to the edge for caching and redirects.

I have not used it at my current organization, but in the past I have used it to bring enterprise-grade features to my small business clients at low or no cost.

Centralized, full-featured DNS.

Sometimes their more advanced caching tools can cause higher first-byte times and problems with JavaScript.

They also lack a good way to manage DNS as a company, since everything is relegated to single account logins until you get to the higher levels. They have come out with a paid feature to remedy this, but I have not had a chance to fully review it yet to know if it fixes the access problem.

There has been some downtime over the years, but it was usually handled well.

I have only scaled this to a few million viewers with a couple TB of traffic, but I didn’t see any issues.

I have mainly been on their lower accounts which don’t really come with support.

I have used a couple of different solutions like Incapsula, CloudFront, and Akamai, but for different projects, not before or after.

It is very easy for someone who knows DNS. It is somewhat opinionated and pushes you into higher tiers, but overall it is easy.

You can get a lot out of the lower accounts. 

I have used several in the space and I still use, Route 53, DynDNS, etc.

This product is good for simple things, but you may need other tools for more fine-grained control of specific portions.

I have used the cache feature of CloudFlare CDN.

CloudFlare is very easy to set up for my site domain.

It is very easy to maintain.

CloudFlare flushes the cache immediately, which is not supported by some of the other CDN networks such as Akamai and Amazon CloudFront. These CDNs take some time that can vary between 5-15 minutes (minimum).

No comments, because I am using it only for creating a cache flushing tool that will work on Adobe Experience Manger (AEM).

There are some features missing or might not be visible to me as I am using its free website plan. These features are:

• CloudFlare doesn't provide the cache flush history. I.e., I am not able to find out the URL information of those I have recently flushed. It makes me uncomfortable when I work in a multiple-author environment and they all have cache-flushing rights.
• It doesn't support a wildcard (*) as some of its competitors support; for example, Amazon CloudFront supports (*) annotation for flushing the complete content tree.
• CloudFlare also does not have any API as some of its rivals provide, such as Amazon CloudFront.

I have used it for the last 10 months.

I have not encountered any stability issues.

I have not encountered any scalability issues.

I don't need any technical supports because there are a number of blogs with solutions for most of the problems. Because of these blogs, I haven’t used this feature until now, so I’m not able to rate this feature.

Before using CloudFlare, I used Amazon CloudFront and Akamai.

I used CloudFlare because I was creating a cache flushing tool for Adobe Experience Manager (AEM). This tool will be responsible for flushing the cache from different CDN networks, such as Akamai, CloudFront, and CloudFlare.

Initial setup is straightforward and easily configurable, even if a person doesn't have any knowledge of CloudFlare. He/she can easily set up CloudFlare.

I’m not able to comment on this because I am using the free website plan.

Before choosing this product, I did not evaluate other options.

In my opinion, CloudFlare is one of the best CDN networks I have ever used. It provides a quick flushing feature that is not supported in some of other popular CDN networks such as Akamai and CloudFront. CloudFlare is a very easy-to-use CDN as compared to others.

The aggressive caching and DDOS mitigation are the most valuable features offered by Cloudflare. Website traffic analytics and threat insights are also very useful.

Utilizing Cloudflare allows us to deploy websites using less hardware due to their caching and helps us serve pages to our customers more quickly and efficiently.

More insight into analytics and threats would be a good place to start improving cloudflare. Also less 501 and 504 errors would be good too.

I've used Cloudflare since 2012 and am currently using the latest version. I've utilized it with several different websites successfully.

No issues encountered.

Only the occasional network issues, some in 2013, where all Cloudflare customers were affected, but much less lately.

No issues encountered.

Good, as the few times I've required customer service, it was more technical but they were always helpful in directing me to the people I needed to speak to.

Excellent. The representatives are knowledgeable and online documentation is great.

Cloudflare was the first service of this type I've used.

It was very easy to get setup on Cloudflare. They have made it even easier recently, and all that needs to be done is to enter your DNS records into their interface and the configuration is done.

We implemented it in-house.

Setup cost was zero and currently we are using the $20 a month plan. I've used the business tier in the past which costs $200 a month.

I don't know of other vendors who offer a comparable service.

I would recommend that you use it. It has been very useful and well worth the cost to me over the last three years.