We performed a comparison between Cloudflare and Reblaze based on real PeerSpot user reviews.
Find out in this report how the two Distributed Denial of Service (DDOS) Protection solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."There are key things that are used for our enterprise customers, such as Lambda and DNS."
"Smaller businesses have seen great ROI due to the low investment and strong performance."
"I like Cloudflare's application gateway and DDoS protection."
"The solution is very good at mitigating threats."
"Cloudflare is a security SaaS provider that provides security and protects us from any application layer attack."
"When using services like Heroku, Cloudflare is very useful for CNAME flattening. I also use it for their end-to-end SSL with TLS authentication on nginx for securing servers."
"The solution provides good load balancing and protection against DDoS attacks."
"Generally, I am satisfied with this product."
"I very much like the elastic search and reports, allowing us to have a 360-degree view of the customer's activities and enabling us to track down any suspicious bots."
"Reblaze knows how to manage security. For me as, someone who knows little about security, it's good that I have a firm that optimizes everything according to their standards. It's their responsibility and they are fully hands-on."
"The best thing about Reblaze, for us, is that it has been a game changer because previously, we were using Google's Web Application Firewall, but it wasn't up to the mark."
"The feature I find most valuable is the user-friendly dashboard. It is easy to understand how everything works and it allows you to make decisions quickly and efficiently."
"The real-time monitoring and reporting are very good. There are information updates in their portal every two minutes. They also have the ability to spill it into Sumo Logic, for example. It's very easy to use."
"It is a highly resilient product that can handle significantly larger workloads and high volumes of traffic with ease."
"We like the website protection. It's really good. The dashboard is really simple to use."
"The main feature is using the rules and being able to see the traffic. It helps us find malicious traffic."
"The solution could use more analytics on the backend to give us more insights into everything. More reports would be helpful."
"Cloudflare could offer a better view or maybe dashboards of the main resources used in the client."
"If they improve on the placement of their data centers, it would be better. I'm living in a remote area. I would like to connect to them without any kind of lag."
"They lack a good way to manage DNS as a company, since everything is relegated to single account logins until you get to the higher levels. They have come out with a paid feature to remedy this, but I have not had a chance to fully review it yet to know if it fixes the access problem."
"One area of improvement is in the Access Rules. Hypothetically, if we wanted to block or challenge traffic outside of the United States, the only way to currently do that (as far as I know) is to enter every single country outside of the United States. That could be a labor intensive job. A solution could be to enable users to create a rule where traffic is only allowed within a certain country."
"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 would like Cloudflare to offer a dedicated account manager for large enterprise clients like us."
"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."
"Some of the settings on the dashboard are confusing."
"They have an interface that you have to adjust to. That is a bit of a downfall because I expect an interface to be very intuitive for someone who knows little about security. But if you know about security, the interface is wonderful."
"Up to now the only cons I could find is sometimes getting change management back on track, because it's a company that evolves, and sometimes I don't have the same needs that they have. But besides that, up until now, I am really pleased with their service and I've also recommended them to some of my clients."
"There is room for improvement in helping us understanding session management... We want Reblaze to catch and identify everything. We want to see the various devices doing one activity and to see, in a timeline, what's happened. We would like to see a more human-readable display to understand what's happening in the web app."
"The WAF features are not as granular as we would expect from a WAF system. There should be more granularity and in-depth rules, out-of-the-box."
"It would be beneficial if it had a workflow or a feature that could fine-tune settings based on high-level requirements."
"I would like to have seen more automated reports. Maybe it has been improved in the last year and I'm just not aware of it. But from a managerial point of view, you want a summary report, a weekly report: How many attacks were blocked? How much bandwidth was saved due to the caching mechanism? What were the top-ten attacks that were tested on the network, etc? I could most likely have found all that data if I logged in to the system and ran different reports. It would be very helpful to get a management report on a weekly basis."
"The next release should have next-generation automation."
Cloudflare is ranked 1st in Distributed Denial of Service (DDOS) Protection with 57 reviews while Reblaze is ranked 20th in Distributed Denial of Service (DDOS) Protection with 10 reviews. Cloudflare is rated 8.4, while Reblaze is rated 8.8. The top reviewer of Cloudflare writes "It's easy to set up because you point the DNS to it, and it's working in under 15 minutes". On the other hand, the top reviewer of Reblaze writes "Offers flexibility with a kill switch for bypassing Reblaze if needed and provides a reliable Layer 7 defense against attacks". Cloudflare is most compared with Akamai, Azure Front Door, Imperva DDoS, AWS Shield and Microsoft Azure Application Gateway, whereas Reblaze is most compared with Imperva DDoS, F5 Advanced WAF, Radware Alteon and AWS WAF. See our Cloudflare vs. Reblaze report.
See our list of best Distributed Denial of Service (DDOS) Protection vendors.
We monitor all Distributed Denial of Service (DDOS) Protection reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.