IBM NS1 Connect Managed DNS and Traffic Steering for AWS Workloads
Intelligent traffic steering has boosted cloud performance and simplifies policy management
What is our primary use case?
I have worked on both deployment models of IBM NS1 Connect in the company's environment and in the clouds. I utilize IBM NS1 Connect's Intelligent Traffic Steering feature.
What is most valuable?
The best benefits of using IBM NS1 Connect are the performance and availability of the product towards the cloud. When comparing the performance with other products, I believe it is above par. It is really helpful and gives me at least a 20 to 30% improvement in functionality.
We were able to increase the traffic with the help of the analytical tools, but they should be more user-friendly. That portion is a little bit complicated as of now, which comes as part of the product's default feature.
It is very easy to assess the impact of IBM NS1 Connect's policy management on my network operations. It is just a matter of configuring the normal network policies, so the configuration of the policies is very straightforward.
What needs improvement?
The aspect that needs improvement about IBM NS1 Connect is that the integration with AI is not seamless at this moment. That particular portion needs to be re-evaluated.
We were able to increase the traffic with the help of the analytical tools, but they should be more user-friendly. That portion is a little bit complicated as of now, which comes as part of the product's default feature.
For how long have I used the solution?
I have been working with the product for more than 15 years.
What do I think about the stability of the solution?
I do not have that much exposure to this particular area, but I did not face any challenges regarding the platform's capability to manage DNS traffic and handle demand spikes.
How are customer service and support?
The technical support is slow. You raise a PR, and then it takes several weeks for them to respond. It is a little bit slow.
How was the initial setup?
Implementation was seamless and I faced no challenges with it. It is easy.
It did not take much time to implement IBM NS1 Connect. It was a straightforward process for me and did not take too much time. It was very easy.
I would say the implementation takes about one day of actual work. The work spans months or several months, but the actual work is very easy. It is an organized product, so it is a straightforward process.
What about the implementation team?
I was part of the implementation process. It was done by me along with my team.
We were a team of 12 people who were involved in all of these activities.
We had a combination of engineers, administrators, and developers in the team.
What's my experience with pricing, setup cost, and licensing?
The licensing cost is reasonable. When I compare it to other products, it is reasonable.
What other advice do I have?
I purchased IBM NS1 Connect through AWS Marketplace. We do use analytical tools built into the product. I rate this product 9 out of 10.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Intelligent traffic steering has improved integration and customization but still needs faster updates
What is our primary use case?
My customers use IBM NS1 Connect's intelligent traffic steering. Intelligent traffic steering helps optimize application performance as a client directly interacts with the IBM counterpart to integrate all components, and it is quite easy and user-friendly.
What is most valuable?
The best features in IBM NS1 Connect for me are basically the easy integration with other endpoint solutions.
I assess policy customization in IBM NS1 Connect as the greatest advantage that we observe in QRadar impacting our customer's network operations.
IBM NS1 Connect's API-driven architecture has helped my organization with digital transformation as it is an open standard. Architecture-wise, I can say it is a good integration, but few OEMs or solutions do not provide that capability of an API interface. For that, we need to build a custom connector, and there we are facing a problem.
What needs improvement?
I believe every product has room for improvement, and I found some weak sides in IBM NS1 Connect.
I think the support for upcoming technical updates in IBM NS1 Connect could be improved as they are not up to the mark, and their development or new enhancements are very slow.
We have found that the API interface is another area of improvement. We found a couple of scenarios where API was not supported by their point product, and we got stuck there. For that, we need some additional custom-built connector, and we found that there is a delay from IBM.
For how long have I used the solution?
I have been familiar with IBM NS1 Connect for almost seven years.
How are customer service and support?
If I had to give a rating of technical support from IBM on a scale from one to ten, I would rate it seven to eight, so you can mention eight.
Which solution did I use previously and why did I switch?
I have not worked with DataStax Enterprise from IBM as it is a NoSQL solution.
How was the initial setup?
The deployment of IBM NS1 Connect is actually quite easy to install.
I participate in the deployment process and was a part of the deployment team, and I led the team.
It actually takes three to four weeks to deploy, based on their environment.
What about the implementation team?
Overall, almost ten plus people were involved in the deployment and the implementation.
Those people involved in the deployment are technical support members; they are not developers as such, and they are implementers only, system integrators.
My company stands more like a system integrator. We are in partnership with IBM as a distributor and preferred integrator.
What's my experience with pricing, setup cost, and licensing?
I am not overall satisfied with the license and cost for IBM NS1 Connect because my pre-sales team interacts on that part regarding pricing. My role is just to integrate and design solutions, so I am not looking into the commercial part.
I would rate IBM NS1 Connect in general at six to seven because all of the features are there, but the cost is quite high. Other competitors have offered a very low price compared to IBM, and that aspect is very tough for us to convince clients.
It is beneficial when I already implement the product, but that is after the fact. Before convincing a client, before implementation, or at the initial POC stage, it becomes a challenge because every time a cost factor comes into the picture. The customer or client always figures out that another OEM is providing this competitive cost and questions why not IBM.
What other advice do I have?
I am familiar with the IBM product line.
I actually know products such as IBM NS1 Connect or perhaps IBM Planning Analytics, but I am just working on QRadar only.
I also work with IBM NS1 Connect from time to time; earlier I used to work on that.
IBM NS1 Connect was purchased directly from the vendor, not through some other stores or AWS Marketplace.
Managing DNS traffic using IBM NS1 Connect has required some additional efforts from a development perspective to build new rules and correlation rules, but their rule engine and development support is quite good.
I have not used IBM NS1 Connect Analytics. My overall rating for this product is six out of ten.
Powerful Dynamic DNS Routing, But a Learning Curve for Complex Policies
One situation where it became especially valuable for us was during high-traffic fintech onboarding campaigns and transaction-heavy operational windows where traffic spikes could impact application responsiveness across regions. Instead of relying on static DNS behavior, NS1 Connect allowed us to route traffic dynamically based on latency, health checks, and infrastructure availability. That flexibility helped maintain much more stable user experiences during peak usage periods.
What stood out immediately was the speed and responsiveness of DNS changes. During infrastructure incidents or deployment rollouts, traffic policies could be adjusted very quickly without waiting through slower propagation cycles that we had experienced with older DNS setups. For customer-facing systems where uptime and response consistency directly affect onboarding and transaction completion rates, that operational agility made a real difference.
From a usability perspective, the platform balanced enterprise-grade functionality with a relatively clean operational experience, which helped engineering and infrastructure teams collaborate more effectively during incident handling and rollout planning.
Overall, IBM NS1 Connect delivered strong value by improving traffic reliability, operational flexibility, and infrastructure responsiveness across critical production systems.
Another challenge we experienced was around operational visibility during highly customized routing scenarios. The monitoring and analytics capabilities are strong overall, but when troubleshooting complex traffic behavior across multiple providers, regions, and failover policies, identifying the exact cause of routing anomalies occasionally required deeper manual analysis than expected.
From a UI/UX perspective, the platform is functional and infrastructure-focused, but some administrative workflows still feel more engineered toward experienced network teams than broader operational users. Teams unfamiliar with DNS operations faced a noticeable learning curve during onboarding, especially around advanced policy configuration and automation workflows.
The integrations with cloud and infrastructure ecosystems were valuable, but maintaining consistency across evolving deployment environments and automation pipelines required ongoing operational governance.
In one healthtech workflow, we were managing patient-facing appointment scheduling and teleconsultation systems that experienced highly uneven traffic spikes during specific hours and seasonal campaigns. Before implementing NS1 Connect, traffic routing was relatively static, so when one region or infrastructure cluster became overloaded, users started experiencing slower response times and intermittent service instability. IBM NS1 Connect helped us introduce dynamic traffic steering based on endpoint health and latency conditions, which improved platform responsiveness significantly during peak usage periods.
Another operational benefit came during infrastructure maintenance and unexpected outages. Previously, rerouting traffic during incidents required more manual intervention and slower DNS propagation handling. With NS1 Connect, failover decisions became much more automated and responsive, reducing disruption for end users accessing critical healthcare services.
We also used the platform in fintech-related environments supporting onboarding systems and transaction-heavy customer workflows across multiple cloud regions. During high-volume onboarding campaigns, traffic loads shifted unpredictably between regions, and maintaining low latency became important for customer conversion and operational reliability. NS1 Connect helped distribute traffic more intelligently across infrastructure endpoints instead of relying on rigid DNS policies.
A major advantage operationally was improved visibility into traffic behavior and infrastructure health. Engineering teams could proactively monitor routing conditions, endpoint performance, and failover events before issues escalated into customer-facing incidents.
Fast DNS Management, Needs UI Improvement
Intuitive UI/UX and Strong Integrations That Simplify Automation
Reliable DNS Management with Impressive Traffic Routing
Flexible DNS Management with Technical Simplicity
Consistent Service But Account Management is Cumbersome Since IBM Acquisition
Powerful, Enterprise-Grade DNS with Standout Traffic Steering and Automation
higher cost
complexity