Cloudflare Reviews

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.

I use Cloudflare primarily for protecting a web application firewall.

The most valuable feature is its usability. Additionally, the built-in rules are great because they protect the applications without the need for large customizations. The CDN performance is also a great benefit, especially since the server was in Canada and users accessed it from Brazil, which improved content delivery significantly. During high traffic periods, such as when the site received increased traffic, Cloudflare effectively provided users with access to the site.

Cloudflare could be improved by introducing a mid-tier pricing option. While they have a free basic tier and an enterprise tier, a mid-priced option would be great for small projects. The number of rules in the web application firewall could also cater more to small projects.

The stability is great. I would rate the stability as ten out of ten.

The scalability is good, and I would rate it as ten out of ten.

I did not deal with their support or customer service as there was no need. The online documentation was sufficient.

Positive

The initial setup was straightforward.

For the small project I was working on, using the basic tier provided a huge improvement at zero cost.

For large enterprises, the pricing is okay. However, the enterprise price for small projects is a bit high. A mid-tier pricing option would be beneficial.

Overall, I would rate Cloudflare a 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.

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.

We subscribed to Cloudflare for cloud-based services, and we are planning to explore its additional features as it aligns with our organizational needs.

The features of Cloudflare were found to be more beneficial and led to the decision to utilize it over other options. However, I am not completely aware of all the specific features, but Cloudflare was chosen for its feature advantage.

Integration involving API with other products could be more user-friendly. Exploring it is interesting, and it would be helpful if those integrations were improved.

We just started using it recently.

We have not encountered any stability issues with Cloudflare.

I am satisfied with Cloudflare's customer service.

Positive

I am not involved directly in the setup as my technical team handles it, however, it was completed very quickly, in less than a day.

We are satisfied with the pricing we received for Cloudflare compared with other commercial options.

We were considering firewall solutions like Citrix and NetGate PFSense before eventually choosing Cloudflare.

The overall experience with Cloudflare is positive, with a rating of eight out of ten.

So primarily, we use Cloudflare DNS for DDoS protection.

We can patch other requests to a particular page to a certain extent. Performance-wise, there isn't a big issue with using it. So it has excellent feedback, and it's used in our public meetings. Also, we're able to manage all SIP platforms with Cloudflare DNS.

For me, the valuable feature is DDoS protection.

Some people want more checkboxes as a feature when using Cloudflare. So, it can dictate your price.

The price is not customized for a user but depends on your usage.

The analytics, basically the dashboard, doesn't have much to it. They need to launch or see something better. So, it's on the relative side.

I have been using Cloudflare DNS for eight months.

It is a stable solution. I rate the stability a ten out of ten.

It is a scalable solution. Almost 30 people are using the solution. I rate the scalability a ten out of ten.

Based on our usage and experience, the support is good, but we do not know about the client's experience.

The initial setup is easy. It takes a couple of hours.

The pricing depends on the usage, but the cheapest would be around 5,000 USD a month.

I definitely recommend others to use the solution. I rate the overall solution an eight 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.

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.