Slash your load times and reduce the impact of provider outages.
Optimize your Multi-CDN setup with automatic load balancing. You can refresh your Pools as often as every 30 seconds so users will always get the fastest connections.
Update your CDN pools as often as every 30 seconds, so users are always routed to the fastest CDN in your network.
Disasters are inevitable, but ITO pools ensure that your clients will continue to enjoy the same fast experience as if nothing had happened.
Manage traffic flow to your cloud services without any additional lookup time.
Whether you're scaling up or moving more systems to the cloud, load balancing with ITO pools will help you transition seamlessly and securely.
Effortlessly migrate your existing infrastructure to the cloud or create a hybrid network with no performance degradation.
Don't limit yourself to just one cloud service provider. Diversify your stack to get the best price points and services from each provider.
Are you running out of bandwidth with one of your CDN providers? Seamlessly add and remove CDN's from ITO Pools with no downtime.
No hardware, no code required. Just enable ITO for your A or CNAME record pool, create monitoring checks, and tweak the ITO settings to your needs.
Stay on top of your providers with round the clock monitoring. Sonar keeps a log of any service disruptions of latency, so you can keep your provider accountable for their service guarantees.
Most CDN's will have different pricing for each region, but just because it costs more doesn't mean it's better. Serve CDN's only in the areas they perform best in, and save money.
Have a preferred CDN for certain areas? No problem! Activate GTD or create an IP Filter and apply it to the same record you apply your pool to. That way you can deliver the best performing CDN to users in that area.
Since you are steering your traffic at the DNS level through your hosting provider, there are no extra lookups required. This can save your valuable milliseconds and is more efficient than third-party or application-level solutions.
In this example, we are going to show how to use ITO pools to optimize a CDN implementation since it is the most popular use case.
In a typical CDN configuration, you would have a CNAME record pointing to the hostname of your CDN provider. The CDN would decide where to send end-users based on their proximity to nearby web servers.
If you have more than one CDN (without ITO enabled), you will use a CNAME record pool. Record pools allow you to specify multiple endpoints, in this case, multiple CDN hostnames. If you have a preferred CDN, you can set different weights for each endpoint to increase or decrease traffic as needed.
ITO Pools are optimized record pools that automatically steer traffic to the best performing endpoint(s).
Our sonar monitoring service will periodically check the response times for the endpoints in your pool. These response times are checked as often as every 30 seconds by ITO and will automatically return the fastest responding hostnames in the pool.
In this example, our user has two CDN's in the US East and US West regions. It looks like they are also using GTD, which delivers region-specific responses. When combined with ITO, the fastest endpoint in that region will be returned in the pool.
That means, in US West, CDN 1 will be returned while in US East, CDN 2 is faster and will be returned.
Let's look at this on a network level. When a user in US East queries example.com Constellix (the authoritative name servers) will check the response times of the CDN's in the pool. Since CDN 2 is faster, the pool will return the hostname for CDN 2 and that CDN will point the user to the closest web server.
To help you get started, here are some best practices that will help you get up and running in no time.
Every time an endpoint is no longer returned in a pool, Constellix will notify a list of contacts. You can set this up Constellix DNS in the Contact Lists setting.
You can set the Monitoring Frequency of ITO Pools to be as often as 30 seconds. That means every 30 seconds, Sonar will test the response times of all the endpoints in that pool and return the fastest performing endpoints.
Monitoring Frequency does not impact your Sonar checks and will only return the latest response times detected by Sonar (based on the Check Frequency you specified for that endpoint in Sonar).
The Sonar monitoring network is made up of 90+ nodes located at critical peering points around the globe.
ITO is able to offer the fastest traffic steering solutions because it operates at the DNS level. Application-level solutions require more lookups and less efficient means of routing. ITO is also faster than most third-party solutions because it is native to the Constellix DNS platform.
ITO Pools can be combined with GeoDNS services like GTD to overcome common routing issues associated with GeoIP services. For example, if a system originated in one location, but was moved to another; GeoIP databases will still report that system as being located in the original location.
GTD corrects this issue because it can detect the real-time physical location of the system.