Forcepoint incident
Email Security Cloud - Advanced Encryption Service Un-available
Forcepoint experienced a minor incident on January 28, 2026 affecting Global, lasting 1h 49m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jan 28, 2026, 04:52 PM UTC
Customer Impact: Forcepoint's Email Security Cloud customers who use our Advanced Encryption service may experience that their secure emails are being queued and may re-attempted for delivery. Customers who do not use our encryption service will not experience any impact on mail flow. Description: We are currently experiencing a problem with our external email encryption provider due to which our email security solution is not able to receive an encryption or decryption token from our vendor. We are working with our vendor to restore service as soon as possible. Next Update: 18:00 UTC
- identified Jan 28, 2026, 05:57 PM UTC
Customer Impact: Forcepoint's Email Security Cloud customers who use our Advanced Encryption service may experience that their secure emails are being queued and may be re-attempted for delivery. Customers who do not use our encryption service will not experience any impact on mail flow. Current Status & Next Steps: We are currently experiencing a problem with our external email encryption provider, due to which our email security solution is not able to receive an encryption or decryption token from our vendor. We identified the issue and requested the vendor to revert the applied changes. Next update time: 19:00 UTC
- monitoring Jan 28, 2026, 06:20 PM UTC
Customer Impact: Forcepoint's Email Security Cloud customers who use our Advanced Encryption service may experience that their secure emails are being queued and may be re-attempted for delivery. Customers who do not use our encryption service will not experience any impact on mail flow. Current Status & Next Steps: Our vendor has reverted the changes, and the problem is resolved We are currently monitoring our environment for stability and will provide a final update once we have confirmation.
- resolved Jan 28, 2026, 06:42 PM UTC
This incident has been resolved.