The Sterling main brand site was unavailable for a period of around 2 hours on the morning of Friday 18th. This was caused by a change to the proxy configuration which was incorrectly deployed by an external automated process. This automated push should have been anticipated (by Hut) and handled in the correct way.
As soon as we were aware of the issue, a fix was immediately created and pushed to the proxy which resolved the issues fully. Normally our 3rd party monitoring tool (https://uptimerobot.com/) would alert us to within 1 minute of any downtime. However on this occasion due to a configuration change in the service external to us which we were not notified about we did not receive the downtime notification. This has now been reconfigured correctly and we should recieve any future notifications in the normal timely manner.
To mitigate against future issues such as this, we will engage with a second monitoring service (probably AWS based) so if one is not working or notifying us the second one should serve as a backup.