Critical incident

Fortra: Email Security - SEA - Resolution Complete

Current status of Fortra: Operational — live Fortra status

Timeline

1. Jun 29, 2026, 16:08 UTC
   investigating
   Summary of Issue & Impact: We are experiencing a service degradation that is impacting Email Security, specifically Suspicious Email Analysis (SEA) and are working to resolve the issue as quickly as possible. During this time, users may experience impacts to inbound messages to the SEA service that are not being processed into incidents as of June 26th. Next Steps: Our technical team is working diligently to identify the root cause and implement a solution. Please expect updates every hour until service is restored. We apologize for the inconvenience and appreciate your patience as we work to resolve the issue. Status: Investigating Next Update: 1:05pm EST
2. Jun 29, 2026, 17:07 UTC
   identified
   Status Update: Update: Our technical teams have identified the cause of the issue. The Fortra teams are working on applying the resolution. As for details on current status and impact, please see below: - SEA Teams are now processing the queued messages from the 26th to current. - There was no data loss caused by this outage. - Messages in SEA queue from the 26th through the issue being resolved (~12:15 EST today) will all show reported at dates of today, not when the user reported them (Please be aware) - As SEA Teams clear the backlog, this will result in a large amount of user notifications and threat alerts as we work though the backlog. Current Status: Resolution In Process Next Update: 2:05pm EST
3. Jun 29, 2026, 19:35 UTC
   identified
   Subject: Email Security - SEA - Service Disruption Update: Our technical teams have identified the cause of the issue. The Fortra teams are working on applying the resolution. As for details on current status and impact, please see below: - SEA Teams are now processing the queued messages from the 26th to current. - ~ 80% have been processed so far, 20% of backlog remains. - There was no data loss caused by this outage. - Messages in SEA Teams queue from the 26th through the issue being resolved (~12:15 EST today) will all show reported at dates of today, not when the user reported them (Please be aware) - As SEA Teams clear the backlog, this will result in a large amount of user notifications and threat alerts as we work though the backlog. (Please be aware of this) Current Status: Resolution In Process Next Update: 4:30pm EST
4. Jun 29, 2026, 20:31 UTC
   monitoring
   Update Summary: Our technical teams have identified the cause of the issue. The Fortra teams have applied a resolution and the queued backlog has been consumed. As for details on current status and impact, please see below: - There was no data loss caused by this outage. - The Incident analysis queues are being worked through by our SEA Ops Teams, but due to the high volumes we may see higher response times. We are scaling up our capacity to help mitigate impacts to customers. - Please note, Messages reported to SEA that were in queue from the 26th through the issue being resolved (~12:15 EST today) will all show reported at dates of today, not when the user reported them (Please be aware) Current Status: Resolution Applied - Monitoring Next Update: 5:30pm EST
5. Jun 29, 2026, 22:04 UTC
   resolved
   Resolved: Thank you again for your patience as we worked through today’s service impact. Fortra teams have confirmed all critical services are restored and backend processes within SEA have been fully processed. If there are any further questions or needs, please submit a case to our Fortra Support Team. 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 preventative steps.

Updates as published by Fortra (original).