Fortra | Status

Between 6:00am EST and 10:00am EST on May 30, we are upgrading the platform version for the Phishlabs Production cluster. This will increment the minor version numbers of several of the service mesh components in the cluster, but will not require any service downtime. Based on testing in the Development and Staging environments, service mesh will remain functional throughout the update.

We can confirm that the issue impacting internal Security Incident processes has now been resolved, and service stability has been restored.

Following the investigation, our technical teams identified the underlying cause and implemented a corrective fix. Additional preventative measures have also been put in place to improve service resilience and reduce the likelihood of recurrence.

While this issue resulted in delays to certain internal workflows, we would like to reassure customers that all security outcomes were achieved within expected timeframes throughout the incident, and there was no impact to the delivery of security protections or response obligations.

We have completed validation activities and continue to closely monitor the environment to ensure ongoing stability and performance.

We sincerely apologise for any inconvenience caused and appreciate your patience and understanding while our teams worked to fully resolve the issue.

Cloud Email Protection: Update internal configuration

The CEP production updates have been completed.

We will be performing some maintenance updates to Fortra VM services on Wednesday May 4th at 7:00 AM CST. Services will remain available but performance may be temporarily slower than usual. User reauthentication may be required upon completion of the update.

We will be performing some maintenance updates to Fortra VM services on Wednesday May 6th at 7:00 AM CST. Services will remain available but performance may be temporarily slower than usual. User reauthentication may be required upon completion of the update.

We are pleased to confirm that the issue impacting PhishLabs Support Services has now been fully resolved.

Email updates relating to support cases are operating normally and services have been fully restored.

Throughout the incident, security-related takedown activities and updates remained fully operational through the MyPhishLabs portal, with no impact to security operations or customer protection outcomes.

We sincerely apologise for any inconvenience caused and thank you for your patience and understanding throughout this incident.

Resolved: Thank you again for your patience as we worked through today’s service impact. Fortra teams have confirmed the solution applied has fully resolved the DMARC Email Security service degradation.

Fortra is committed to the resiliency and stability of our platform. A full incident report will be available within 5 business days, which will include a full root cause analysis, mitigation, and future prevention steps. If customers want to receive this formal RCA, please put in a request with our support team to deliver.

Customer Action: As the resolution has been applied by Fortra technical teams, mail could have been delivered to spam folders, so its always best practice to review your spam folder accordingly.

We are providing a final public update regarding the service disruption impacting Cloud Data Protection customers hosted within the AWS Middle East (UAE) region (me-central-1).

AWS has advised that additional time is required to fully restore the remaining impacted infrastructure. As a result, Cloud Data Protection services for a limited number of customers remain affected while recovery activities continue.

Given the limited scope of the remaining impact, this status page will no longer be used for ongoing updates related to this incident. Any further communication will be provided directly to the affected customers.

We sincerely apologise for the disruption this incident has caused and appreciate the patience and understanding shown throughout this event.

Our Engineering and Operations teams will continue to monitor the situation closely and work alongside AWS until full-service restoration is confirmed.

The issue impacting the me-central-1 region has now been fully resolved. All the services have been recovered and are operating normal.