EPM SaaS service disruption on UK environment

We wanted to provide some more information for the event affecting EPM SaaS in our UK region. Starting at 2:05 AM PDT we experienced power and network connectivity issues for some instances, and degraded performance on the storage service that we use to run EPM SaaS. As a result, EPM SaaS has not been available in the UK region. The power and networking connectivity had been restored to the affected instances and storage service but we have to restore the services in the UK on new instances in order to recover the service. We are working to recover the service as soon as by replacing the affected instances.

As a reminder, the EPM agent still enforce all policies on the endpoint and the Offline Policy Authorization Generator can be used to create offline policies - https://docs.cyberark.com/Product-Doc/OnlineHelp/EPM/Latest/en/Content/EPM/Server%20User%20Guide/One-time%20Run%20Authorization%20Tool.htm

We apologize for the inconvenience that this may have caused.

Update: At 16:30 EDT August 25 all services were restored.

A fix has been implemented and we are monitoring the results.

Due to the cloud provider outage, the underline storage we have been using got corrupted and we are now busy with replacing all affected instances and volumes. This is expected to get few more hours. We apologized on any inconvenience this may cause.

As a reminder, the EPM agent still enforce all policies on the endpoint and the Offline Policy Authorization Generator can be used to create offline policies - https://docs.cyberark.com/Product-Doc/OnlineHelp/EPM/Latest/en/Content/EPM/Server%20User%20Guide/One-time%20Run%20Authorization%20Tool.htm

Our cloud infrastructure provider still working at highest priority on remediating the issue.

Cloud infrastructure provider in the London area and the team is still working on this issue

There is a general problem in our cloud infrastructure provider in the London area and the team is working on this issue at highest priority.

CyberArk engineers have identified the issue and are working to implement a fix. We thank you for your patience at this time.