Load balancing and health checking.
Easily integrate health checks into your load balancing configurations with baked-in Failover. Failover automatically moves your traffic from unavailable resources to healthy ones. The most affordable and easiest type of load balancing to configure.
Failover is supported for A, AAAA, ANAME, and CNAME records. All you need to do is enable Failover for your record, and specify the IP addresses or hostnames of your backup resources. These backups are only used when the primary IP/hostname is unavailable.
We make the internet faster and more reliable. See how we can help your organization with a Constellix demo.
Talk to an Expert→The main reason you would want failover enabled in your DNS solutions is to prevent an outage and keep healthy traffic to the most reliable sources. DNS outages can occur for a multitude of reasons like DDoS attacks, configuration errors, or faulty equipment. If your organization has experienced an outage, you know the overall severity it can have on your business. The downtime can cost you thousands in lost revenue, and the hundreds of employee hours doing damage control really starts to add up.
Learn More✓ GeoProximity
✓ Global Load Balancing
✓ Traffic Steering
✓ Round Robin
✓ Latency Load Balancing
Constellix offers enhanced failover monitoring, so your failover changes happen faster. Failover is available for: A, AAAA, ANAME, and CNAME records.
• Users can choose up to 14 different monitoring locations,
• 30 second to one day monitoring intervals,
• Traceroute and visual traceroute in notification report
• Avoid false positives with verified checks
• All IP's in the configuration are constantly monitored
Constellix understands the importance of 100% uptime, because we are the only provider in the industry who has it. Time and time again, we see providers that have global and regional issues that take down large portions of the internet. In these instances, downtime could have been prevented if redundancy were taking place. It is a fool-proof strategy and overall best practice to prevent service disruptions.
Schedule Migration