This problem has been resolved. Our engineers were performing some DNS maintenance which resulted in the DNS settings for SurfProtect to stop working, along with other services. As the DNS entries for SurfpProtect have a short time to live to allow our engineers to migrate traffic in case of hardware failure, the problem became immediately apparent for the service. The Team will perform a post-mortem to see what went wrong and why our testing didn't catch the problem.
