Cloud Platform Release v25.3.1

We’ve been working hard since our last release in September and are pleased to release version 25.3.1 of our cloud platform that fixes a number of bugs and introduces a couple new features as well. Below are the brief release notes for your reading enjoyment.

• Compute Availability: We released the first version of our compute offering. We’ve offered it to a select few customers for a number of years, and it’s now time to offer it to everyone by making it available in the panel. Users will now see a new tab after logging into the dashboard advertising this functionality. With a Compute subscription, users will be able to order Bare Metal Servers or Virtual Servers in any of 5 global locations to start with the objective of offering 9 locations by the end of 2025. Compute will only be available for users of other services including DNS, ADC-as-a-Service (Load Balancing, WAF, etc.) or Multicloud-Networking. Contact us at hello@totaluptime.com for more information.
  
  
• New Network ACLs: We released a new version of our Network ACL functionality for IPv4 and IPv6 control. The new ACL functionality improves on our prior system in three major ways. First, it allows the building of an ACL before application to a pack. Second, it deploys rules on our edge Juniper MX Routers – a far more robust platform and the ‘edge’ being a better location to block traffic vs. our current mid-tier appliance-based system. And lastly, it allows for attaching an ACL to more than one pack. Previously an ACL would need to be built for each pack, even if they were identical, creating extra work and consuming platform resources unnecessarily.
  
  
• Dashboard Improvements: We made a few adjustments to the dashboard. 1) We now have a more dynamic announcement section that allows us to provide more timely messages. 2) We added the ability to close dashboard sections so users don’t need to look at them all the time.
  
  
• View Built-in Monitors: We have a number of “built-in” monitors that customers can choose to monitor their devices instead of creating a custom monitor. But it was previously not possible to view the configuration of a built-in monitor nor would it show up in the “in use” column. We’ve finally corrected this!
  
  
• DNS Edit Bug: We resolved a bug that would show occasionally if you edited a record in DNS, but did not make a change and clicked save. In rare cases the updating icon would stay stuck on updating and never clear even though nothing was being updated.
  
  
• IPv6 Reassignment: Occasionally when reassigning a purchased IPv6 address to a sub-company, it would fail. We’ve now corrected this so it reassigns properly every time.
  
  
• Connection Monitors: We resolved an issue where the Connection Monitor tab in networking would periodically show a blank page when data actually existed. This was actually due to too much data and has now been corrected.
  
  
• Primary Zone PTR: We previously required that PTR records in a primary forward zone be created by request via a support case. This was due to the fact that these were most often used incorrectly, and thus when not delivering the desired results, caused excessive support ticket creation. We’ve now extended this functionality to the UI since we have found our DNS customer base more technical today than in years past.
  
  
• New Device Geo Weight Bug: If a pack had geo weighting enabled and a new device was added, it would appear to complete adding successfully in the UI but in fact it was erroring on the back-end. We corrected this.
  
  
• Device DNS Status Message: We changed the status message in a device where a DNS lookup was required to be more friendly. Previously it would say “DNS Status Code 0” (which was a good thing, but confusing) to say “DNS Resolution Successful” instead.
  
  
• Web Server High CPU: We resolved a small (yet incredibly annoying) UI bug that would create very high CPU usage on our front-end web servers when a user remained on the Configuration Builder page with a pack open in certain situations.
  
  
• DNS Query Report: We made a few very minor cosmetic changes to the DNS Reporting tab to better display the company drop-down menu (for those with reseller or sub-company functionality enabled) as well as the total query volume.
  
  
• Statistics Date Picker: Choosing a date range on the Statistics page was not entirely intuitive, so we adjusted this to now use a handy date picker instead.
  
  
• Chat Missing: During a minor release a few weeks ago, a JavaScript error prevented the Live Human Chat from properly loading in the bottom-right when in the panel. This is now back. Sorry about that!
  
  
• Device Status Icon: The Device Status icons are supposed to update automatically as new data comes into the platform. This stopped working due to an issue with our SignalR implementation recently. We’ve now corrected that again so you can just wait and watch them change vs. having to refresh. 
  
  
• Failover Pool Delete: We’ve solved an issue whereby if a user attempted to delete a Failover Pool that was in use, it would not properly detect and allow for automatic resolution of any conflicts. This would then require the user to manually go to the DNS tab and stop using the pool before coming back to try deleting it again. We’ve resolved that so you don’t need to perform unnecessary extra steps. 
  
  
• Returned IPs still in the ACL: If a customer returned an IP address, it would still appear in the Networking Firewall ACL list (old ACL) for configuration. This has also been corrected. There was no risk, it was just strange. When an IP address is returned, it is still technically related to that customer behind-the-scenes for two reasons: 1) if they want it back, they can get it within 90 days), and 2) it goes into a cool-down mode for cleaning before going back into the general pool a year later for other customers to purchase. 
  
  
• SSLv3, TLS1.0 and TLS1.1 disabled by default: When creating a new public facing port the really old protocols we still offer (for only a few more months) SSLv3, TLS1.0 and TLS1.1 would be enabled by default. Now they aren’t. And yes, they are going away soon and TLSv1.3 is being released soon too (it’s already there on the back-end going through final beta testing). 
  
  
• 2FA Activation bug: We resolved a permissions bug where if a user doesn’t have “Account” tab rights, they couldn’t get to the 2FA section to activate it (e.g. activate TOTP with the QR Code). Sorry about that, we fixed it. 
  
  
• Wildcard for SSL_PROXY: We no longer allow the wildcard port (* – asterisk) for the SSL_PROXY protocol. It was rarely used, and frankly, we encourage specific ports for security rather than using wildcards. 
  
  
• Trial Sign-up Approvals: We previously would allow anyone to sign up for a trial of any service, occasionally asking for a credit card in certain situations as a validation method. But with the vast number of bots signing up for trials and magically finding valid credit card numbers to enter, we have changed the trial system to a manual approval-based system. Now our team watches for sign-ups and manually validates them during business hours. Sorry, but the bots were quite annoying.
  
  

Please send us your feedback! As we continue to evolve our solution to be the leading ADC-as-a-Service platform, we want to know what you think. Tell us the good and the bad. Let us know what features you think we should have and which ones are a waste of time, buggy, or don’t make sense. The more feedback you give us, the better our product becomes because we really do listen! Please contact us! We love hearing from our customers.