Cloudflare Reviews

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. 

I use the solution for DNS management. 

What I do is every domain we have has some web resources available. Instead of sending everything directly to my web server, what we do is send all the DNS requests for that domain to Cloudflare. It is DNS security enabled to defend those websites from attacks. 

The solution has benefited the company in terms of security. It keeps the public IP anonymous to the user as well. 

The security is the most important aspect. The attacker won't have details since my public IP is anonymous. It offers us good privacy. 

The setup is straightforward. 

They are very professional and really go above and beyond for their users. 

The solution is very scalable. 

The pricing is fair. 

I'm not aware of any areas in need of improvement. There might be helpful if there was some web application firewall feature. That way, I wouldn't need a third-party solution like Radware.

I've used the solution for five years. 

The solution is extremely scalable. We have five people managing it in the company. 

I'm not sure if we will increase usage. It will depend on different elements we have in the future, such as more clients. 

I've never contacted technical support in the past. 

We did not use a different solution. We might have used Open DNS, which is the Cisco Umbrella solution right now. We moved to Cloudflare as it is cost-effective. 

The implementation is very simple. You actually forward all the initial requests to the DNS main server. Once the domain is registered with them, they actually confirm that, and they have a step-by-step configuration part where you actually go and do the different elements that you have that you need to have in place. 

We had one person manage the deployment. 

I handled the implementation myself in-house. 

The ROI is hard to portray as security, while important, is hard to quantify. You would only lose money if you had an attack and you need to calculate the cost against the risks. 

The pricing is reasonable. It is cheaper than other options. There are no extra costs or fees.

I'm a customer and end-user. 

I'd advise people to really think about why they want to use Cloudflare. If it is feasible, it will depend on the level of investment they want to make into their security.

I'd rate the solution nine out of ten. 

We use Cloudflare for our DNS service. 

We previously faced so many issues with our in-house DNS servers. Cloudflare provides a backup, so if you have any issues with your environment or something goes wrong with a software hostname and IP address, you can run the backup and experience zero downtime. 

I get a lot of value from Cloudflare's API because it enables you to build a separate environment inside the solution. You can create a domain for performing test requests before you move to the production environment and connect various domains.

When you build a new server, you first need to register your hostname and IP address in the cloud first. You don't need to go through the same steps every time. If you have a script that supports the API, you can run it to update the zone code and IP address.

 Cloudflare doesn't have a reverse lookup. We can only do a DNS lookup to get the IP address from the hostname. It doesn't work if you want to look up the hostname from an IPA address. 

I have used Cloudflare DNS for three months. 

I rate Cloudflare DNS seven out of 10 for stability. We haven't had issues.

I rate Cloudflare DNS seven out of 10 for scalability.

Cloudflare support responds as quickly as possible. If you have any issues, you can get a support engineer with the best qualifications. 

The Cloudflare setup is straightforward.

I rate Cloudflare DNS seven out of 10. Cloudflare is my first choice if I have a chance to use it. The GUI looks pretty. It's easy to create area codes and DNS entries. You need to ensure that these features are required in your environment and negotiate a good price.

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.

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.

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.

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.