Try our new research platform with insights from 80,000+ expert users

Amazon Route 53 vs IBM NS1 Connect comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Nov 4, 2024

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

ROI

Sentiment score
6.1
Amazon Route 53 provides ROI through downtime prevention, efficiency improvements, security enhancements, and justifies its cost with quality.
Sentiment score
8.0
IBM NS1 Connect improved performance, reduced costs, and enhanced efficiency through automation, benefiting application uptime and customer experiences.
The main factors are time-saving and security, even if the cost is slightly higher.
 

Customer Service

Sentiment score
8.1
Amazon Route 53 offers effective support, but premium plans improve experiences; basic plans might limit engagement and satisfaction.
Sentiment score
9.1
IBM NS1 Connect offers exceptional customer support with expert guidance, responsiveness, and reliability, consistently exceeding customer expectations in DNS services.
Amazon services are very stable, and there are few problems.
Amazon's customer support is very good with a quick response time.
They provide a normal developer level of support, and within twenty-four hours for non-critical issues, which is acceptable for us.
 

Scalability Issues

Sentiment score
8.3
Amazon Route 53 is highly rated for its scalability, reliability, and efficient integration, though some find it costlier.
Sentiment score
8.3
IBM NS1 Connect efficiently scales to meet traffic demands with automation, low error rates, and global operational reliability.
We haven't faced any scalability issues, thanks to its integration with AWS services.
Amazon Route 53 is scalable as I use automation with YML files to handle scalability needs, and it works well.
The scalability is maintained by AKS, and Route 53's scalability part is primarily involved with load balancing.
 

Stability Issues

Sentiment score
8.2
Amazon Route 53 is highly reliable, rated 99.99% stability, with rare downtime, enhanced by advanced routing features.
Sentiment score
8.2
IBM NS1 Connect offers high stability and reliability, with minimal downtime and excellent performance even during high-demand situations.
The solution is stable.
I have not encountered any stability issues.
I have not experienced any outages or downtime.
 

Room For Improvement

Users seek improvements in handling requests, logging, UI, security, pricing, support, configuration, integration, automation, and domain support in Route 53.
IBM NS1 Connect can improve by enhancing API, bulk changes, traffic management, DNS configurations, testing, and dashboard usability.
There could be improvements in the configuration process, particularly in the options provided during setup, such as subdomain configurations and certificate management.
There is a need for technical knowledge to use Amazon Route 53 effectively.
There is room for improvement in restricting access through one website from S3 buckets.
 

Setup Cost

Amazon Route 53 offers scalable, usage-based pricing; considered reasonable for reliability but complex for high-demand sites.
IBM NS1 Connect provides competitive, value-driven pricing, satisfying enterprises with fair costs for high request volumes and advanced features.
Route 53 is more expensive.
The pricing of Route 53 is slightly higher compared to other services, however, it is justified by its high availability and reliability.
 

Valuable Features

Amazon Route 53 excels in scalable DNS management, traffic routing, AWS integration, security, cost-effectiveness, and global domain management.
IBM NS1 Connect offers geo-load balancing, automation, and real-time telemetry with integration capabilities, enhancing performance and user experience.
I find Amazon Route 53 valuable for its ability to manage DNS records and efficiently route traffic with features like failover routing and geolocation routing.
Route 53 is valued for its health check feature and reliability.
One of the best advantages is managed security.
 

Categories and Ranking

Amazon Route 53
Ranking in Managed DNS
2nd
Average Rating
8.6
Reviews Sentiment
7.3
Number of Reviews
32
Ranking in other categories
No ranking in other categories
IBM NS1 Connect
Ranking in Managed DNS
12th
Average Rating
9.6
Reviews Sentiment
8.0
Number of Reviews
11
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of January 2025, in the Managed DNS category, the mindshare of Amazon Route 53 is 20.0%, down from 24.5% compared to the previous year. The mindshare of IBM NS1 Connect is 2.6%, down from 3.4% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Managed DNS
 

Featured Reviews

Jithin Scaria - PeerSpot reviewer
Provides clear documentation, easy to understand, simplifies management and efficiently handles our domain-related configurations and DNS records
For initial setup, we generally use provisioning tools for these kinds of DNS records. The choice often depends on the cloud provider and the Infrastructure as Code (IAC) tools the client prefers. We adapt our approach accordingly rather than focusing on a single method within Route 53. The documentation is very user-friendly. Even someone with no prior experience can easily understand it. It provides step-by-step instructions and explains things in a clear and concise way. You can find everything you need to know about Route 53 and its features in the documentation, including white papers. In addition to manual configuration, you can also use third-party tools like Terraform, Pulumi, or AWS CloudFormation templates to manage your Route 53 configurations.
Adam Surak - PeerSpot reviewer
Handles customer-facing records and upstream selection logic with good efficiency
We leverage two things from Managed DNS that we couldn't do with any other solution. One is their filter chain technology, which allows us to shift some of the intelligence we need for the traffic steering to the DNS. The second one is data sources, which enables us to manipulate multiple records simultaneously using NS1's internal message DOS. In our case, we are trying to direct the traffic in over 150,000 different NS1 records to an arbitrary set of repeating responses. If we have about 1,000 endpoints, that translates to around 150,000 records. Assuming there's an even distribution, so every time a server fails or an endpoint goes on a level, we would have 150 updates. With NS1, we have one, so this had an even more significant effect. There are situations where we have thousands of specific records sharing the same responses. In that case, there is one update instead of thousands and thousands. When we chose Managed DNS in 2014, it was the only solution that could do what we wanted, but I'm not sure about the current state of the market. The NS1 API is an API on top of a managed DNS. It's not an afterthought. It's not like the solution existed. Someone was sending updates by email. Then a product manager came along and said, "Hey, there is this cool thing. It's called an API. Maybe we should do it?" And they are like, "Okay. Let's do it." In the case of NS1, they thought about how to use an API to manipulate and retrieve the stuff. It's supposed to be API-driven. Also, NS1 doesn't have hidden features that would not be available over the API. Even their dashboard is built on top of the API. You can leverage all the functionality programmatically. That's what we do. We don't use their native integrations because we have been customers before these integrations and real-time telemetry existed. Our solution isn't leveraging either of those. Instead, we leveraged their API integration, which was the first thing that existed. Indeed, the API is at the core of how we use Managed DNS. No one goes to the dashboard or manually clicks anything. Everything goes via the API, and we perform hundreds of changes every minute. The API automatically drives everything, so that's the integration we leverage. We don't use the Pulsar Active Steering feature because we don't have a website. Our solution is being used as an API for other solutions. You can put the Pulsar agent on the website and feed NS1 the information. In our case, we are integrating into third-party sites. We cannot put our JavaScript on their websites for NS1 to provide the data, so we don't.
report
Use our free recommendation engine to learn which Managed DNS solutions are best for your needs.
831,265 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Educational Organization
22%
Computer Software Company
15%
Financial Services Firm
8%
Manufacturing Company
6%
Computer Software Company
15%
Financial Services Firm
11%
Comms Service Provider
10%
University
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

Azure DNS or Amazon Route 53?
Azure DNS is a hosting service of DNS domains. It has excellent operating time and performance, resulting in fast resolution. We like the ability to view everything in the Azure portal - this makes...
What do you like most about Amazon Route 53?
The most valuable features of the solution are the DNS, routing, and traffic features.
What needs improvement with Amazon Route 53?
There is a need for technical knowledge to use Amazon Route 53 effectively. If a person without much technical background could use it, I would have rated it a ten out of ten.
Ask a question
Earn 20 points
 

Also Known As

Route 53
NS1 Managed DNS, NS1
 

Overview

 

Sample Customers

Hess, Expedia, Kelloggs, Philips, HyperTrack
Avast Software, Bloomberg L.P., BBC, Carfax, CNBC LLC, Deloitte Consulting LLP, Disney Streaming, Dropbox, EBAY Inc, Gannett Media Corp, Salesforce, Wayfair, Workday
Find out what your peers are saying about Amazon Route 53 vs. IBM NS1 Connect and other solutions. Updated: January 2025.
831,265 professionals have used our research since 2012.