We performed a comparison between Amazon Route 53 and IBM NS1 Connect 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 solution effectively monitors the health of resources and provides good identity access management."
"The most valuable feature is that it works very well."
"The solution is cost-effective."
"The initial setup is good and straightforward."
"We use Amazon Route 53 for dynamic naming and routing policy."
"We haven't faced any outages or issues directly related to Route 53. It has been 100% stable for me."
"Amazon Route 53 is a DNS resolution service that helps you to map your hostname to another hostname."
"The scalability is the most valuable feature."
"Their Pulsar filters allow us to collect RUM metrics from our users so that we can determine the best paths for our users to take. That has been very useful in providing the best user experience, and for responding to and recovering from downtime of our multiple CDNs."
"Monitoring is really important for us. We really care about reliability, and we want to make sure that we can remove some points of presence in our sector and in our edge network really fast when we experience any problems. So, monitoring that NS1 provides for DNS is really important for us."
"The fact that it's an API-first platform for DNS and application traffic management is one of the reasons we looked into NS1. We use it for a lot of automation and metrics gathering and it's been great."
"Everything we download into our observability platform so that we can also track any changes in traffic behavior or things like that is also something that we use quite a lot. I'd say traffic management, the speed of updates, and observability are the top three things that we use."
"For starters, it integrates with Terraform and a lot of our infrastructure is effectively built out using Terraform. That makes all this stuff extremely easy... when we deploy, all the entries are created and configuration is done."
"The provisioning is great. They have an API service that is simple to use and very quick. The changes that we make are replicated worldwide in a matter of usually milliseconds, sometimes seconds. They are done very rapidly. That's something that's obviously priceless when we're dealing with things like DNS."
"The Filter Chain is one of the most valuable features, for geo-load balancing and geo-fencing. The Filter Chain is the most useful because it allows us to do several things. With geo-fencing we can redirect a particular user to a particular answer. That's very valuable for us. Filter Chains with monitoring is our strategy to provide redundancy."
"We find that the low latency access to DNS queries has a direct effect on the customer experience. Visiting a site, whether it's an AdTech-based solution or marketing tech, the fact that whatever we're rendering on a page can be rendered better than the industry standard, in terms of time, ensures a better user experience."
"The solution’s pricing and technical support could be improved."
"The product could improve its price."
"There are no detailed logs, and they should implement that in the solution."
"The product should improve its automation."
"When you add a new DNS record instructing the solution to map one thing to another, it has to propagate to all the networks, which takes some time."
"The solution’s pricing could be reduced."
"It is difficult to manage the product if the person involved in the setup process doesn't know much about the solution."
"The product’s security and disaster recovery features need enhancement."
"We would really like them to become a DNS registrar."
"We care about monitoring and telemetry work, and NS1 provides a pretty good system for monitoring. We can monitor our endpoints and points of presence around the world. If there are any issues, we can easily remove them from our network, but this area needs some improvement because it is not always reliable in NS1. In the past, we had a number of false-positive cases when the monitoring system told us about some problems in our infrastructure that were not true. NS1 is improving the system, and we are constantly talking about this with them. I know that they are releasing a new version of their monitoring system, which is really important for us, but this is a different area where we would expect them to improve."
"I would love to see improvement in the testing capabilities they provide. They have a simulate-filter feature so that you can simulate how your traffic would flow, based on their Filter Chains. I believe that was shut off for quite some time. Having that as a way to test our load-balanced CDN structure would be fantastic."
"The Filter Chain simulation is really good in the UI, but it would be nice to have something similar in the API so that we could simulate and test things before we deploy them."
"We use the geo load balancing functionality and there are a couple of things that are helpful there. But the language itself is something we had to get used to a little bit. Some of my folks made a few mistakes in rolling out the Filter Chain...The Filter Chain setup is a bit hard to grasp at first. It would also be nice to have a way to simulate changes in addition to staging."
"The reporting metrics are great from an API standpoint, but it would be a little bit nicer if there was some type of dashboard around that. There should also be some type of reporting that's more executive-level focused."
"We use our client in our infrastructure to communicate with NS1. This client is a bit complex in the way that it is set up. NS1 has their own client solution that you can deploy into your platform to do this, but even that is a bit complex. So, I would like a very simple, thin, light API agent that we can deploy into our platform to communicate with NS1. That would be welcome."
"There could maybe be additional ways to manage traffic. There are no major improvements we're looking for. It's a very complete solution."
Amazon Route 53 is ranked 3rd in Managed DNS with 19 reviews while IBM NS1 Connect is ranked 7th in Managed DNS with 11 reviews. Amazon Route 53 is rated 8.6, while IBM NS1 Connect is rated 9.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 IBM NS1 Connect writes "Balances cost and functionality, speeds up provisioning, and reduces the DNS maintenance work drastically". Amazon Route 53 is most compared with Azure DNS, Cloudflare DNS, Google Cloud DNS, Cisco Umbrella and Neustar UltraDNS, whereas IBM NS1 Connect is most compared with Cloudflare DNS, Akamai Edge DNS, Neustar UltraDNS, Hurricane Electric Free DNS and Cisco Umbrella. See our Amazon Route 53 vs. IBM NS1 Connect 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.