Cloudflare Reviews

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.

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

Our company provides the solution to customers who need website load balancing or DDoS protection. Customers with minimal traffic use the Business Plan and customers with a huge amount of traffic use the Enterprise Plan. 

We currently have thirty customers on the Business Plan and three customers on the Enterprise Plan. 

The solution provides good load balancing and protection against DDoS attacks. 

The solution should expand its learning portal for partners to include a few demo accounts for learning the product and developing knowledge or technical expertise. 

Support response time could be improved. 

I have been using the solution for one year. 

The solution is stable, has curbing centers in Pakistan, and is widely used. 

The solution is scalable to each customer's needs. For example, you can scale up if you have two domains and want to add a third. It is easy to incorporate scaling. 

The technical support response time for Business Plan customers could be reduced. Most companies opt for this cost-effective plan but they should receive the same service as the Enterprise Plan. Currently, response time for Business Plan customers is six to eight hours and that should be minimized. 

I rate support an eight out of ten. 

Positive

The solution is easy to setup and share with customers. We categorize a customer's needs and recommend the best plan based on traffic and whether they need load balancing, bot management, routing, and unlimited bandwidth.  

We implement the solution for our customers. Deployment includes one project manager and one support technician. 

The solution is expensive when compared to other products but offers unlimited bandwidth. 

I rate the licensing options an eight out of ten. 

The solution is a great fit for customers who want unlimited bandwidth. 

Competitors such as Akamai have strict options for bandwidth so might not be a good fit. 

I recommend the solution for customers who don't yet have an idea how much bandwidth they need or who anticipate upscaling in a few months. 

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