Cloudflare Reviews

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.

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.

We monitor traffic on Cloudflare, and we have some applications that we download on Cloudflare. We have ten to twenty gigs per country.

Our customers are residential ISP customers with high traffic because of Google apps, Amazon network peering, and Direct TV, so we use Cloudflare for the customers. For example, we announce all traffic or customer traffic to the BDP station, and Cloudflare works by caching the content, and the servers send the content to our clients.

What I like best about Cloudflare is that my company can use it to trace and manage applications and monitor traffic. The solution tells you if there's a spike in traffic.

Cloudflare also sends you a link to check your equipment and deployment and track it through peering, so it's a valuable tool.

It would be good if Cloudflare could have more servers for better traffic routing or an increase in the traffic routed. This is what I'd like to improve in Cloudflare.

In the next release of Cloudflare, it would be good if it could give more information about applications, particularly which ones still need improvement.

Cloudflare is a stable solution. At first, my company had a graphics-related problem during the POC stage, but after that, my company didn't experience any issues with Cloudflare. The Cloudflare connection is stable.

Cloudflare is a scalable solution. The process to scale it is clear, and the Cloudflare team will contact you to check if you want to scale up.

The technical support for Cloudflare is good because the team is knowledgeable about the connection, standard, special configurations, etc. My team had no problems double-checking configurations with the Cloudflare technical support team.

We didn't use a different solution apart from Cloudflare.

The initial setup for Cloudflare is easy because you only have to connect it to your private cloud based on your requirements. I didn't experience any issues connecting the tool.

In my company, deploying Cloudflare required a lot of equipment, so it took four to five days to complete the deployment, but there was no problem with the process.

In terms of licensing costs, we don't pay for licensing for Cloudflare. We only establish communication, then for peering, Cloudflare takes care of the cross-connection in different data centers.

My company has different computing tools in Colombia, Miami, South America, Brazil, and Chile, such as Akamai, Cloudflare, CDN, and Google Playbook.

I have hands-on experience with Akamai, Twitch, and Cloudflare.

My company is a Cloudflare customer.

Three engineers handle the deployment and maintenance of Cloudflare within my company. The NOC team monitors the cluster, and if there's any issue, my team checks the port, and the engineers review the patch to see if it's okay. If the problem remains, my team escalates to the Operations team responsible for looking into the issue more closely. Within two hours, the Operations team contacts my team about the resolution.

I'd recommend Cloudflare to other companies because it helps monitor traffic.

My rating for Cloudflare is a ten out of ten because it's a helpful tool, and I didn't find anything wrong with it.

We are an IT consulting company, we provide solutions to our customers. We implement the solutions for our customers. Some of our customers use CloudFlare, some of them are using  Imperva and Palo Alto.

Our customers use this solution for any web traffic, mostly GCP or to AWS cloud as a backend.

I like caching and DDoS. There are key things that are used for our enterprise customers, such as Lambda and DNS.

Latencies are always a problem.

Also, one thing I would say is you have to maintain DNS through their services. I don't know if that's a requirement or not.

Latencies are the key issue. If you are not caching and just using DDoS then definitely, there are some latencies added to the traffic.

I have been working with Cloudflare for more than six years.

We work with many different versions. For new customers, we use the latest version.

I haven't had any issues with stability. We haven't heard anything from our clients.

It's a stable solution.

It is easy to scale. We haven't had any problems with scalability.

We have not used technical support.

Cloudflare is very straightforward. It is easy to set up.

There is no installation, you just go through the configuration process.

The price is reasonable.

It all depends on what the customer is looking for. These are two different areas. Basically, CloudFare is completely Cloud-based, whereas Imperva I can have a physical appliance or a virtual appliance, or a cloud-based. 

My solution is based on what customers are looking for, but Cloudflare is pretty good and getting really popular in terms of DDoS, the paid version of it.

We looked at the service. What are acceptable latencies? Is it okay to route through a different vendor, and before it reaches the backup? They have to go through multiple vendors. You also have to consider what the latencies cost and is that acceptable for the service. These are key things you need to consider when selecting a cloud-based vendor for DDoS.

I would rate Cloudflare a nine out of ten.

Cloudflare is easy to use. It's very intuitive. Although I think it's quite good, it doesn't provide me with all the features I would expect to have if I were using Imperva. I think Imperva is far richer in features from what I can see, but I think that can bring its own pains to be honest. For this reason, I think Cloudflare is a simpler version. 

With Imperva, you can drill down to packet-level very easily. It's very, very good at drilling down deeper and deeper into the packet. I think that is available with Cloudflare, but it's not as good. It doesn't seem to provide us with the same kind of search capability as Imperva. Having said that, I think that's one of the advantages of Cloudflare because you just have to click a button and drill down via clicking. I actually like Cloudflare to be honest. Imperva is almost too difficult for normal businesses — it's too complex. There's almost too much information there. Whereas with Cloudflare, it's easier to drill down and it's more intuitive.

I've only been using Cloudflare for a week.

I wasn't involved in the implementation, so I have no idea how much it costs. 

I think this solution is quite intuitive. For businesses that don't have a dedicated security team, I think it's a better product; it's more intuitive for people like us. I'm a network security engineer, but I'm not a dedicated security official. I've too many other things going on to have the time to do the rule sets that you need if you're working with Imperva — I think a lot of that is down to you as the customer. With Cloudflare, I think a lot of that happens in the background. 

I've been working with it for a week and a half so I'm not the best person to say if it's better or worse than Imperva. My only reaction is that maybe it's not as feature-rich for the end-user. Whether that's an advantage, well, that's questionable. Maybe we don't need all of those features sometimes — it depends on the business. The business I'm working in now is a very different business with a different kind of security model. The business I was working with when I used Imperva probably needed that feature-rich capability.

Overall, on a scale from one to ten, I would give Cloudflare a rating of eight. It's quite intuitive. I like it. From what I've seen so far, there are no negatives to report as of yet.

We are a reseller of CDN solutions and this is one of the products that we implement for our customers.

I also use Cloudflare for various websites. It is a content delivery platform.

The most valuable feature is the web application firewall.

The dashboard is very easy to use. It is simple to explain and a layperson can achieve good results.

The performance is good.

There should be a specific price list for enterprise-level customers.

Another problem with this product, as a reseller, is that your customer needs to give you access to all of the features before you can help them. This is different than with other vendors, where you have insight into the customer's contract. Unless the customer gives me access to their dashboard, I am totally blind and cannot really support them. The problem is that it makes it difficult to give them support. There should at least be a read-only view of the data so that resellers can properly support the clients.

Essentially, the dashboard is not well set up for resellers. Resellers need to have a dashboard view of all of their accounts.

I have been working with Cloudflare for about two years.

It has had some flaws in the past. For example, I think that they had two outages last year and they had a dashboard outage this year, but apart from these instances, it's quite stable.

The scalability is great. They're expanding and have enough resources worldwide.

Our customers are typically enterprise-level organizations.

The technical support team is very good and they know what they're doing.

I am also familiar with Akamai and Fastly. Cloudflare is easier to manage than the solutions provided by these vendors. The user experience is much more straightforward and appeals to a lot of developers.

Akamai, however, is the largest and most popular CDN. It's a very sturdy solution. They basically made this industry, 20 years ago, paving the way for newest vendors such as Cloudflare.

The initial setup is very straightforward. You need to know something about DNS domains and so forth, but if you're familiar with setting up a website then it's straightforward. The deployment takes about 15 minutes.

My customers generally have three or four in-house people to handle the deployment.

There seems to be no official pricelist for enterprise-level customers and it is more of a trial-and-error estimation. The cost primarily depends on the size of the organization. 

We have some customers who cannot afford to have a downtime of an hour, so the customer has to choose. We give them other options, such as Akamai CDN, who provide a 100% SLA and they haven't failed in 17 years. That's a different clientele. Younger startups sometimes break things by pushing out new applications and they're used to having a more fragile environment.

This product is well-developed and they are expanding into other spaces.

I would rate this solution 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.

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.