Cloudflare Reviews

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 typically use it to safeguard websites, especially web applications.

The UI is good.

Explaining the pricing structure can be quite intricate because they often segment it differently. For instance, when it comes to static content and content delivery, some providers, like Akamai, offer separate pricing for static and website content. This approach simplifies the pricing aspect.

On the other hand, Cloudflare's pricing is based on bandwidth, which makes it somewhat more complex. Additionally, the timing aspect can lead to it being considered overpriced. This is a particular concern we have with Cloudflare, as they may struggle with accurately detecting the client.

It is stable.

It is scalable.

In Thailand, we have the perception that support should ideally come through a reseller rather than directly from the software provider. This is especially true when we are dealing with larger enterprises. In such cases, it makes sense to obtain support directly from the company, even though the pricing may be more favorable. The key factor is the language in which the support is offered, which, in this case, is in Thai.

Neutral

I believe that because we reside in Thailand and primarily operate in this market, Akamai has a better understanding of the Thai market model and cost structure. Moreover, Akamai has strong partnerships with various mobile operators and mini-operators in Thailand, which adds to their advantage. However, I must admit that the user interface (UI) of Akamai is somewhat lacking compared to Cloudflare. When it comes to security, Akamai often outperforms Cloudflare. But if we consider content delivery, I find Cloudflare to be a hundred times better.

I use both of these services for video delivery, specifically customized online content delivery tasks. They facilitate the distribution of video content over the network. In this regard, Akamai is one of my top choices as it excels compared to other software options.

The initial setup is very easy.

I believe their performance has improved, but I'd like to refrain from discussing the pricing aspect related to the cloud. The pricing, in my opinion, could be simplified, and I think they should consider reevaluating the pricing for support, as it can be quite high. At times, this cost can make it challenging to choose Cloudflare or opt for the support.

When we opt for Cloudflare, it's typically because the website requires protection, and users expect an automated investigation. The company's user interface is a notable advantage in this decision. However, this is not unique to Cloudflare and is a common feature among its competitors as well.

If you don't have significant funds, our initial suggestion might be to try the free tier first. This way, you can gain a better understanding of your specific requirements before considering alternatives. However, it's worth noting that Cloudflare is relatively user-friendly and straightforward to use, making it one of the easiest options available

I would overall rate it a six out of 10.

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 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 launched the application on the WLP engine. Our website hosts various images, media files, and other external files. We use Cloudflare to ensure faster website delivery.

Google page scripts contribute to the size of web pages. Cloudflare optimizes these scripts and other page elements to improve performance. Techniques like minification and image compression reduce the size of assets, leading to better performance and faster user load times.

It can improve the central time, performance, and SEO schema. 

Cloudflare performs well with static content. However, there are some performance considerations when it comes to dynamic content that involves fetching data from databases or using APIs.

We are not currently using Cloudflare for an e-commerce website. Still, if we were to add an e-commerce site on a platform with region-specific pricing and content, Cloudflare's service might need improvements in handling these dynamic requirements.

I have been using Cloudflare for two years.

I rate the solution’s stability an eight out of ten.

I rate the solution’s scalability an eight out of ten.

The initial setup is easy.

The tool's pricing is moderate.

I rate the product’s pricing a five out of ten, where one is cheap, and ten is expensive.

I recommend the solution.

Overall, I rate the solution a six 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.

Cloudflare serves as both a Content Delivery Network and a security system. When integrated into the software, it optimizes content loading speeds, ensuring users access content swiftly. Additionally, Cloudflare safeguards websites from various cyber threats, providing security. 

DDoS attacks target unprotected machines. Cloudflare detects and stops these attacks using internal systems. It identifies incoming DDoS attacks, issuing challenges or blocking them immediately.

In Cloudflare, numerous features cater to web security needs. Conducting thorough research on your company's operations is crucial for configuring VAS. This involves determining which requests to whitelist, challenge, or block. Additionally, Cloudflare offers rate-limiting capabilities for endpoints. You can set limits to the number of requests, preventing overload situations. Another valuable feature is the ability to implement geoblocking using IDS rules.

When a user accesses the website, Cloudflare's CDN system checks for static content such as JavaScript files, CSS, and HTML. It then caches this static content on its CDN servers across approximately 140 data centers worldwide. When subsequent users request the same content, Cloudflare serves it from the nearest data center, improving performance.

Cloudflare's impact on SEO rankings and website visibility is notable. Collaborating with the business team to optimize website loading speed can benefit SEO.

We're facing challenges due to an upgrade in the machine learning model. The problem arises from some users abusing the APIs, resulting in an influx of suspicious traffic. Cloudflare's learning model mistakenly identifies this traffic as human. Consequently, it assigns it a higher trust score, akin to legitimate human traffic, causing complications in our architecture. Previously, such traffic would have been categorized as suspicious, enabling us to apply appropriate blocking rules. However, we encounter difficulties distinguishing between genuine and suspicious traffic with the new categorization. Despite these challenges, overall, Cloudflare remains the preferred solution compared to Azure, AWS CloudFront, and Google Cloud Armor.

I have been using the product for five years. 

I rate the solution's stability a ten out of ten. 

I rate the product's scalability an eight out of ten. 

The tool's support takes at least one hour to respond. 

Neutral

I rate the tool's ease of deployment a ten out of ten. It's very quick. Deployment time largely depends on how we configure it, whether done through coding or the UI. For a single-user setup, it's straightforward. However, for more complex configurations with multiple use cases, it can vary. However, setting up a single zone for production load typically takes less than an hour.

The product's pricing is cheap. 

Our clients include larger companies such as one that sells automobile parts globally, another that deals with banks and financial institutions, etc. It is mostly recommended for enterprises. 

I highly recommend Cloudflare as a superior solution compared to others in the market. It offers coverage for various use cases, including SaaS products, web application security, and Content Delivery Network systems. Additionally, Cloudflare provides features like the Magic Transit system, which helps control internal traffic.

I rate it a ten 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.