We performed a comparison between Amazon Route 53 and Cloudflare DNS based on real PeerSpot user reviews.
Find out in this report how the two Managed DNS solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."The most valuable features of the solution are the DNS, routing, and traffic features."
"Technical support from Amazon is very good...Overall, the product is stable."
"Amazon Route 53 is a DNS resolution service that helps you to map your hostname to another hostname."
"The feature for health check efficiently impacts the uptime and reliability of AWS servers including EC2 and EKS."
"We use Amazon Route 53 for dynamic naming and routing policy."
"It stands out for its user-friendly interface, seamless integration with other AWS services, and ability to efficiently manage DNS, making it a valuable tool for various deployment scenarios, including those involving Kubernetes on AWS."
"You can host your zone and name servers here, and keeping track of records is easy."
"We haven't faced any outages or issues directly related to Route 53. It has been 100% stable for me."
"Cloudflare DNS is widely used, and it's good for websites. If we use Cloudflare DNS and update one record, it updates in their office instantly."
"The most valuable feature of Cloudflare DNS is security."
"The solution is stable, and the DNS servers are simple to use."
"The most valuable feature of the solution is external DNS. It is also very secure. They have their own main server and once you configure it, the product takes care of everything. There are no issues in resolving IPs and low latency is also present."
"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."
"It is a stable solution. I rate the stability a ten out of ten...I rate the scalability a ten out of ten."
"Its most significant benefit to date is the speed with which it refreshes DNS records on the internet once you change it. If you are changing a website or registering a new record, it is very quick."
"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."
"The cost calculator for determining the cost of Route 53 is a little bit obscure."
"When we are looking at the model registry, it may be not clear sometimes. For example, if you use a single grid model and group or registry, it has a different SDK in the pilot. And it may be not so comfortable to use both of them because it is two different places for keeping things in order."
"There are no detailed logs, and they should implement that in the solution."
"The solution should include more robust and secure services for hardening sites."
"It may not always be easy to integrate with on-premise infrastructure, especially with the complexity of the resolver and other factors involved. Improvements could be made to enhance the ability to integrate seamlessly."
"The platform is more complicated to learn than one of its competitors."
"The product could improve its price."
"Route 53 would be better if it had the ability to handle multiple requests at the same time because we have a lot of users. I would like that to be optimized in the next version."
"I believe they currently have this feature, but there will most likely be integration with APIs so we can control some features through API."
"The analytics, basically the dashboard, doesn't have much to it."
"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."
"Cloudflare's free plan is limited to 5,000 records for their free plan. They should increase that. For example, if I create a domain called abc.com and a subdomain called a.abc.com, my record count will be two. I can make a maximum of 5,000 subdomains. However, if we use our own DNS hosted on another provider, there is no limit. Their free plan also lacks name server customization."
"The tool needs to improve caching of servers. The product needs to include PFX certificate as well."
"The solution could be more user-friendly."
"Cloudflare should add more documentation and pricing to the cloud version."
"The documentation could improve for Cloudflare DNS."
Amazon Route 53 is ranked 3rd in Managed DNS with 19 reviews while Cloudflare DNS is ranked 1st in Managed DNS with 13 reviews. Amazon Route 53 is rated 8.6, while Cloudflare DNS is rated 8.6. The top reviewer of Amazon Route 53 writes "Provides clear documentation, easy to understand, simplifies management and efficiently handles our domain-related configurations and DNS records". On the other hand, the top reviewer of Cloudflare DNS writes "A tool that offers good performance that needs to improve in areas like assessment and payload". Amazon Route 53 is most compared with Azure DNS, Google Cloud DNS, Cisco Umbrella, Akamai Edge DNS and Neustar UltraDNS, whereas Cloudflare DNS is most compared with Quad9, Azure DNS, Google Cloud DNS, Cisco Umbrella and Hurricane Electric Free DNS. See our Amazon Route 53 vs. Cloudflare DNS report.
See our list of best Managed DNS vendors.
We monitor all Managed DNS 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.