Cloudflare Reviews

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.

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.

We primarily use Cloudflare DNS as a content delivery network (CDN) and for its free DNS service. Additionally, it provides us with web application firewall (WAF) control, caching control, and security measures against bot attacks. These features are readily available, and that's why we use Cloudflare.

The best feature, in my opinion, is the caching capability. Even when there is a high load on our servers, Cloudflare is able to cache the data and serve it to users, ensuring they can still access the website. Additionally, Cloudflare only forwards requests to our servers when new information is needed, which helps offload the server's workload. That's what I find most valuable about Cloudflare.

We have noticed multiple instances where Cloudflare falsely indicates that our servers are down, even when there is no actual load on them. This makes it challenging for us to identify the exact issue. 

Another drawback we've experienced is with IP masking. When our website is accessed through a VPN, the access logs record Cloudflare IPs, which makes it difficult to determine which IPs are impacting the website's load. These are the major challenges we face.

In future releases, one thing that would be great is if Cloudflare could provide basic WAF rules and security recommendations based on website scanning. You could submit your website, and it would generate a list of security measures that should be implemented for your website and other web applications. That would be highly valuable.

We have been using it for the past year. The domains and servers are hosted on AWS cloud.

In my experience, Cloudflare has proven to be quite reliable.

We haven't fully explored the scalability aspect yet. Currently, we are using the free version and still exploring its features and functionalities. Once we've gone through everything and if we feel the need, we might consider upgrading to the pro plan or the enterprise-level functionalities.

We haven't needed to contact them so far. Managing DNS on multiple other platforms was relatively easy for me, so I didn't require support from Cloudflare. However, I did reach out to them once regarding SSL and Cloudflare certificate-related concerns, but I'm still unsure about that aspect. 

Before using Cloudflare DNS, our domains were with GoDaddy, and we were managing our DNS there. 

It was my decision to move our website to a CDN, and I chose Cloudflare because it is an open-source tool that could provide the solution we needed.

The DNS setup itself was relatively easy, but exploring and understanding the other options and features of Cloudflare was a bit challenging initially. However, after reading the documentation and doing some research, I was able to grasp how everything works, and it became much smoother to navigate and utilize those functionalities.

In my organization, I'm the one responsible for all DNS management, and most of the DNS is managed through Cloudflare.

We are using the free version.

I would definitely recommend them to use Cloudflare. If someone has basic knowledge of DNS, they would be able to use Cloudflare. However, if they want to utilize advanced functionalities like caching, bot controls, and website security, they can leverage their existing knowledge and delve into those areas. It's relatively easier, but some basic research and exploration would be beneficial.

I would give it an eight because there are a few features with unclear documentation, which makes it difficult to understand them. However, overall, the majority of features are easy to grasp and navigate, so I would give Cloudflare an eight.

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.

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. 

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. 

Generally, I am satisfied with this product.

We are a product integrator and reseller, and we would like to have a better partner relationship, similar to a channel sales relationship.

Sometimes we are on our own or get diverted by Cloudflare because they have direct sales, which competes with us and makes it difficult to build a relationship with this company since we want to be an MSP or a managed service provider for the solution. 

They are creating every week now and developing new products. They are on the right track.

I wouldn't say I want to add anything just yet. While I am attempting to become an MSP, I would like to have access to my clients who are using the product.

An MSP is essentially a corporation that resells a product and wants to provide support and first-level service to its consumers.

Access to the solution's dashboards is not intended for a service company. You are practically blind, and to validate a problem, you must view the customer's screen.

It's not like other systems where you can go into the back dashboard and see what the consumer sees and then alleviate the problem.

To provide help, you must first discover how to gain access to the information.

It is inconvenient.

According to what I hear, they are working on it and will get there gradually.

I have been working with Cloudflare for approximately four years.

Cloudflare is stable, however, its global performance could be better. 

They have a few hiccups here and there, but for a startup, that's to be expected.

Technical support is responsive.

It's a premium model. You can start at zero and work your way up to the enterprise model, which has a very high pricing level. 

There are rivals on the market who provide the same solution at a lesser cost.

We are partners with Cloudflare.

I would rate Cloudflare an eight out of ten.

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 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.

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.