Articles Tagged: load balancing

A question we frequently receive is: “How can I manually fail traffic over from my primary server to my failover server group in the Cloud Load Balancer?” Manually failing traffic is something you may wish to do if your primary server is experiencing issues that the monitor has not yet detected, or if you want […]

If you’re looking to implement an HTTP to HTTPS (SSL) redirect for your web application, you can now enable a feature directly on the load balancer instead of configuring it on your server. This significantly improves redirect performance and reduces the load on your servers. To implement this change, you must be on the main […]

Total Uptime’s Cloud Load Balancer and Web Application Firewall support a feature to block entire countries from reaching your website or application on a per-port basis. This is a powerful tool to stop unwanted traffic from getting anywhere near your servers or devices. When enabled, traffic that reaches our network will have the origin IP […]

PCI requires that TLSv1.0 be disabled. If you’re using the SSL protocol on our load balancer to take advantage of SSL Offload and/or SSL Acceleration, you can easily disable TLS 1.0. You don’t necessarily need to disable this on your server, since communication between the load balancer and your devices is a trusted connection, but […]

If you’re like many of our clients, you not only want to retrieve the original client IP for your web server logs, but you want to use them in code as well… for example, to track invalid login attempts, or record the IP in a database for online payments etc. (NOTE: If you need the […]

The server “weight” select menu shown at the far right of your server or device within a Server Group allows you to adjust how traffic is distributed by the load balancer when you have two or more devices in a configuration. In essence, the higher the number, the heavier the weight, and the more traffic […]

You can configure any monitor to test your server(s) as often as once per minute (the test “Interval”). Additionally, you can configure these parameters: Response Time-out (in seconds) – This is how long the monitor will wait for a particular test to come back positive or negative. Down Time (in seconds) – This is a […]

Our DNS Failover monitoring and Cloud Networking solutions (e.g. Load Balancing, firewall) have the ability to send email alerts when devices go up or down. In order to create an alert list and assign it to your failover pool, follow these steps: Go to the ACCOUNT link in the upper-right corner of the management portal. […]

The recommended way to monitor any type of database, including Microsoft SQL Server, is to create a hidden web-page that does a specific database query, and when successfully completed, sends a word (e.g. “OK”) to the web browser. This method is secure because you need not open SQL ports in your firewall to allow our […]

Yes, absolutely. When creating an HTTP monitor, you can go to the SPECIAL PARAMETERS tab and adjust the HTTP Request value to look for your special page. By default the HTTP Request value is “HEAD /”. If, for example, you wanted to test the page at http://www.mydomain.com/test.php, you would change the value in the HTTP Request […]

Search our Knowledge Base

About Total Uptime Technologies

Total Uptime Technologies, LLC is a privately held provider of Cloud solutions designed to help organizations achieve high availability in a demanding online world. Our multi-datacenter, multi-country Cloud platform easily delivers on our uptime promise because it has been engineered from the ground up to be fast, flexible and resilient.

While other organizations were busy renaming their legacy solutions as “Cloud” and dressing them up to take advantage of the latest hype, Total Uptime Technologies was engineering a true Cloud Platform that was multi-datacenter at its core. In our mind, Cloud meant resilient, and resilient meant that we had to design an application that could span infrastructure at different datacenters in different geographies – continents apart. Only then would we be content with calling it “Cloud”.