Cloudflare Reviews

Cloudflare is mostly a CDN service plus DDoS protection, but they are now offering services like cloud object storage, which AWS under S3. Cloudflare provides a cheaper alternative. They also have zero trust and load-balancing services. 

Cloudflare DNS is widely used, and it's good for websites. If we use Cloudflare DNS and update one record, it updates in their office instantly.

Cloudflare's free plan is limited to 5,000 records for their free plan. They should increase that. For example, if I create a domain called abc.com and a subdomain called a.abc.com, my record count will be two. I can make a maximum of 5,000 subdomains. However, if we use our own DNS hosted on another provider, there is no limit. Their free plan also lacks name server customization. 

I've used Cloudflare DNS for one year.

Last year, the service went down, but it was only 49 minutes.  

Setting up Cloudflare DNS is easy. They have a simple web interface and also an API for advanced users. 

We use the free version of CloudFlare

I rate CloudFlare DNS nine out of 10. I would recommend it. It's the fastest DNS service. 

We use the solution for all our products hosted on Azure.

The solution is stable, and the DNS servers are simple to use.

Cloudflare should add more documentation and pricing to the cloud version.

I have been using Cloudflare DNS for nine years, since 2014.

I rate the solution’s stability a ten out of ten.

We never faced any problems with scalability. We’ve 100-200 users using the solution.

The initial setup is straightforward and takes 15-20 minutes to complete if you want to start a new one. 

Deployment is pretty straightforward when you take a domain. You need to set the DNS to Cloudflare. Once that is done, it hardly takes one or two minutes to take effect. We first pointed to Cloudflare as our DNS. From there, it took a pretty simple configuration for our web browser.

We deployed the solution by ourselves.

We are using the free tier of the solution.

When we started, Cloudflare was the best solution for us. We were using the free service, and it was working well. We never considered switching to Azure DNS because Cloudflare met our needs. Azure DNS has improved recently, and they now offer free SSL domain registration on App Services.

Overall, I rate the solution a ten out of ten.

We use Cloudflare for security and delivery.

Cloudflare is a security SaaS provider that provides security and protects us from any application layer attack. Feature-wise, Cloudflare is fairly good.

Cloudflare's console should be made more user-friendly.

I have been using Cloudflare for about two to three years.

Cloudflare's stability is fair enough, and I haven't encountered any problems with the platform's stability.

Akamai is more user-friendly and easy to configure on the UI for a new person. Imperva is also a good solution that provides most of the features Akamai provides.

Cloudflare's pricing is not much higher and is good for middle-level organizations.

I have experience with the cloud version of Cloudflare.

I would advise users to explore Cloudflare and Imperva parallelly because they both stand on the same ground regarding security. In Imperva, there is no version control on their console, which was concerning for me.

Overall, I rate Cloudflare a seven out of ten.

I use Cloudflare to secure my own websites and servers since I use the proxy functionality to hide my website/server IP. Also, I like to use Cloudflare DNS manager. I think it's simple and easy to use.

I did use Cloudflare as a freelancer or for my personal projects. So I made some websites, and I recommended my freelance customers to use Cloudflare for their DNS management. Also, I did use it in one organization. It was a startup, and it was me and my friend working there, so I did recommend the startup owner to use Cloudflare because of caching functionalities that could speed up your websites and so on.

The most valuable feature of the solution is the proxy, so I can hide my servers. So no one can scan them, especially for port scanning, since we were hacked once. I did buy a VPS server, and I was just getting started. So I started MongoDB and left the port open. Someone scanned the website and saw the open port, and since I was just starting, I didn't set a password. He managed to get in, and he locked the database and locked all the data (ransomware). When using Cloudflare, I was sure that no one knew my real server IP address.

I couldn't think of buying it since I am from Tunisia. We have really strict limitations to buying internationally. So our bank cards are available only in Tunisia. When you own a company, the bank allows you to buy things from outside of Tunisia. Even if I wanted to, I wouldn't be able to buy Cloudflare in my country. The aforementioned details can be considered for improvement.

I have been using Cloudflare for two or three years. Also, I am using the free plan version.

I rate its stability a ten out of ten.

I rate its scalability a ten out of ten because I had no issues with it. Also, it was fast when updating my DNS records. So, that's why I always recommend it to my friends and organizations I deal with.

I have plans to increase the usage of the solution.

I have never contacted Cloudflare's support team.

Positive

The initial setup was really simple and user friendly.

I did not evaluate other options. I found Cloudflare on a YouTube tutorial. So I tried it and liked it, and I never even thought about looking for something else.

I was using the free plan, and mainly, I was using it for DNS management as it was simple. When I buy a new domain, I don't use the main DNS management system. Also, I use it for IP protection. I didn't have the time to really use much of the solution. As far as I know, it's all good. I did see a new feature, but I didn't really manage to get it. I didn't use it.

I would definitely recommend it to those planning to use it.

I rate the overall solution a ten out of ten.

The first use case was to administer the main domain of the organization where I worked.

We have the entire registration process for the main domain and its subdomains, and we create web application firewall (WAF) and load balancer rules.

We did a major MX migration from Google to Microsoft, and doing that with Cloudflare has given us immense security.

This domain also started to visualize improper accesses from other countries and monitor where the main accesses came from.

We made some blocks of administrator sites that only be accessed by a specific IP.

Cloudflare's solution brought us more agility, security, and confidence in managing the environment.

We have seen that there are very few failures or almost none that occur on the Cloudflare servers, and if they occur, the accesses are distributed to another region.

We like that we have a view of where the main accesses came from, such as the main countries, and also what was being blocked by the web application firewall (WAF)

Creating a rule to limit some admin access also improved the security and integrity of our environment.

The features we used the most were the web application firewall and the load balancer. These two services were essential for our structure.

The web application firewall brought us good security and a view of the accesses/blocks of the entire domain and subdomain that were accessed both by region (country) and IPs.

As for the load balancer, it did its job perfectly. Our scenario consisted of two web servers in different allocations to control access demands, and the load balancer did the job as expected, bringing security and stability to access points.

Cloudflare could offer a better view or maybe dashboards of the main resources used in the client.

For example, it could be possible to create dashboards and reports of the main accesses allowed or blocked by the web application firewall. It would also be nice to bring information on the client's screen about the status of the services according to the hosted region.

Of the services that I use, this is the part that I miss. Other services are in agreement and serving me perfectly as they should be.

I've been using Cloudflare for about three or four years.

I use it for my private work network and Office 365 network for both DNS and access through Cloudflare.

Its ease of integration with Office 365 and the fact that it's a good product compared to what I had before.

An integrated SSO would be nice, as well as the ability to integrate with the on-site active directory instead of just AD through Azure AD.

I have been using Cloudflare DNS for two years. 

Their documentation is awesome, so I haven't had to deal with their tech support before. I would rate my experience with customer service as excellent, maybe an eight or nine out of ten.

Positive

I would say try it out, and if you like it, use it. I would rate it very good, a ten out of ten. 

Cloudflare DNS is the primary DNS resolver for our domains. We are using it for CD.

The most valuable feature of Cloudflare DNS is its global reach and it is always evolving.

It would be helpful if the solution could continue evolving to compete with the other solutions on the market.

I have used Cloudflare DNS for approximately two months.

I rate the stability of Cloudflare DNS a ten out of ten.

Cloudflare DNS is highly scalable.

We using the solution to its fullest.

I rate the scalability of Cloudflare DNS a ten out of ten.

I rate the support of Cloudflare DNS a ten out of ten.

Positive

The initial setup of Cloudflare DNS was a quick process using the documentation. It took us approximately two weeks to complete the implementation. The documents that were provided were helpful.

When you compare Cloudflare DNS to other solutions, such as Akamai, the price is reasonable.

There are four people who manage this solution. However, they have other tasks other than only managing this specific solution. Cloudflare DNS is a critical solution and the network team covers it well.

Cloudflare DNS has had a highly stable performance with good reliability. It's working better than our own distribution. We're happy with the solution.

I rate Cloudflare DNS a nine out of ten.

Cloudflare is used for service protection. We use this solution as a managed service for our end user customers, such as banking users for protection.

The most valuable feature of Cloudflare is the GUI. You are able to control the solution very well through the interface. There is a lot of functionality that is embedded in the service.

Cloudflare does not have an on-premise solution. If they had different approaches they could be better suited to accommodate more customers, such as on-premise and hybrid deployments. For example, hybrid deployments would be useful where you could move the traffic from the enterprise to the cloud.

I have been using Cloudflare for approximately five months.

There were a few months when we were doing some updates and there were some issues with the stability. However, the one or two times we had problems it is not enough to say that it is not a stable solution in general.

I rate the stability of Cloudflare an eight out of ten.

The solution can scale well.

I rate the scalability of Cloudflare an eight out of ten.

The technical support from the vendor could be better.

The support is provided online and most of the technical advice is provided by an open community. The level of support is not enough. For example, if you start using this solution and do not have a lab there needs to be someone that can speed up your process. In this case, the community is not enough, it could be better.

I rate the support from Cloudflare a six out of ten.

Neutral

The initial setup was stressful. You have to tune the configuration for the integration which is important to have it done correctly.

The solution has many features but there are ones that you need to pay for. Sometimes you have to find out which is available for free and which you have to pay for.

Most of the vendors are building new functionality and are moving in the same direction.

I rate Cloudflare an eight out of ten.