Exclaimer incident
Microsoft incident causing issues with signature imprinting and the portal in multiple regions
Exclaimer experienced a major incident on April 24, 2026 affecting US: Server-Side: Signature Application and US: UI: Admin User Interface, lasting 15h 20m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Apr 24, 2026, 04:03 PM UTC
We are currently investigating issue with Portal access and signature imprinting issue. This is related to the Azure outage - https://azure.status.microsoft/en-us/status
- identified Apr 24, 2026, 06:44 PM UTC
We are observing improvements in signature imprints and portal access. However, intermittent failures may still occur as the underlying Azure issue is not yet fully resolved. We continue to actively monitor progress from Microsoft and will provide updates here as more information becomes available.
- identified Apr 24, 2026, 10:07 PM UTC
We are continuing to see improvements, with no further reports at this time. Microsoft is still in the process of rolling out changes across the region, and we are closely monitoring progress. We will provide further updates as they become available.
- resolved Apr 25, 2026, 08:41 AM UTC
The azure incident has been resolved and our Exclaimer engineers we have been able to restore full functionality for our customers. Extended monitoring has not indicated any other outstanding issues at this time. If you are continuing to have issues with Exclaimer signature imprinting or the portal, please reach out to our support team, who will be happy to help.
- postmortem May 22, 2026, 04:16 PM UTC
Issue: Signature tester errors when testing Client-side Signatures Incident Length: 8 hour\(s\) and 2 minutes Incident Date: 21/04/2026, UTC 10:06– 18:08UTC 21/04/2026 Incident Status: Resolved **Summary** Attempting to run a Client-side signature test within the Exclaimer Portal resulted in an error message being provided within the Portal. Signatures continued to be applied to messages as expected for both Server-Side and Client-Side offerings. **Root Cause** An update to the Signature Tester introduced a new element that was not currently required, but was being expected, causing the tester results window to fail to load and preventing the results window from being generated within the portal only. **Mitigation** Once the issue had been identified by our Engineering team, the change was reverted, restoring full service to the signature tester within the Web Portal. **Incident Timeline** 21/04, 10:06 – A new deployment to the signature tester was released from testing environments to live servers. 17:30 – Customer reports are confirmed by the support team when speaking with a customer who reports that the tester is failing to display a result. 17:32 - Support confirms that the issue is present in multiple regions. 17:40 – Engineering teams are notified of the issue. 17:52 – Engineering teams are able to roll back the deployment to the UK region. 17:54 – Support team confirms the issue is no longer occurring within the UK region. 18:08 – Rollback completed across all regions. 18:16 – Exclaimer Support confirms that the issue has not reoccurred since the rollback was completed.