Störungsverlauf von Exclaimer

1. 27. August 2026 um 10:14 UTCidentified

   Exclaimer-Supportmitarbeiter befassen sich derzeit mit einem Problem, das die Zustellung von E-Mail-Antworten von unserem Support-Team beeinflusst. Wenn sie ein laufendes support-ticket haben, können sie sich im support-portal anmelden, um nach möglichen updates zu suchen und dem support-ingenieur zu antworten, der ihrem fall zugewiesen ist. Sie können auf Ihre aktuellen Tickets zugreifen und auf den zugewiesenen Support Engineer antworten, indem Sie die in diesem Leitfaden beschriebenen Schritte ausführen: https://support.exclaimer.com/hc/en-gb/articles/9389259466141

2. 28. August 2026 um 08:35 UTCresolved

   Exclaimer-Mitarbeiter haben eine interne Änderung vorgenommen, und die Überwachung zeigt, dass das Problem jetzt vollständig gelöst wurde. Wenn sie ein offenes ticket mit unserem support-team haben und diese woche keine antwort erhalten haben, folgen sie bitte ihrem fall per e-mail oder direkt über unser webportal. Um auf Ihre aktuellen Tickets zuzugreifen und unserem Support-Team zu antworten, befolgen Sie bitte die in diesem Leitfaden angegebenen Schritte: https://support.exclaimer.com/hc/en-gb/articles/9389259466141.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 20. August 2026 um 12:34 UTCinvestigating

   Ingenieure sind sich eines Problems bewusst, das den Signature Designer betrifft, was einige Kunden daran hindert, Signaturvorlagen zu bearbeiten. Es gibt keine Auswirkungen auf den Postfluss oder die Signaturzustellung zu diesem Zeitpunkt. Wir untersuchen und werden innerhalb von 60 Minuten ein weiteres Update bereitstellen.

2. 20. August 2026 um 12:59 UTCmonitoring

   Exclaimer-Ingenieure haben das Problem behoben, und Kunden sollten bei der Verwendung des Signature Designers keine Probleme mehr auftreten. Wir beobachten jetzt alle weiteren Fragen.

3. 20. August 2026 um 16:08 UTCresolved

   Ingenieure haben bestätigt, dass der vorherige Servicealarm behoben wurde. Der Service ist jetzt wieder voll gesund und funktioniert normal. Vielen Dank für Ihre Geduld.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 18. August 2026 um 08:31 UTCinvestigating

   Exclaimer-Ingenieure sind sich eines vorübergehenden Problems bewusst, das dazu führen kann, dass bestimmte Seiten, wie Branding, Kampagnen und Disclaimer, nicht für Kunden im Exclaimer-Portal geladen werden. Sanierungsarbeiten sind im Gange, um den Zugang zu diesen Abschnitten des Portals wiederherzustellen. Unterschriften werden immer noch auf E-Mails angewendet. Wenn Sie sehen, dass Unterschriften nicht angewendet werden, kontaktieren Sie bitte unser Support-Team, das Ihnen gerne hilft.

2. 18. August 2026 um 10:39 UTCmonitoring

   Unsere Ingenieure haben das Problem behoben, und Kunden sollten bei der Verwendung des Exclaimer Cloud Portals keine Probleme mehr auftreten. Wir beobachten jetzt, dass die Stabilität erhalten bleibt. Wenn Sie weiterhin Probleme sehen, zögern Sie bitte nicht, unser Support-Team zu kontaktieren, das Ihnen gerne hilft.

3. 18. August 2026 um 12:23 UTCmonitoring

   Exclaimer Engineers sind sich der Berichte bewusst, dass der Signature Designer für einige Kunden nicht geladen wurde. Erste Abhilfemaßnahmen wurden ergriffen, und der Signature Designer sollte nun wie erwartet für die Benutzer geladen werden. Wir untersuchen jetzt die Ursache des Problems

4. 18. August 2026 um 13:21 UTCidentified

   Wir haben ein Problem innerhalb des Portals identifiziert, bei dem einige Buttons für einige Benutzer nicht auf Klicks reagieren. Ingenieure arbeiten jetzt daran, das Problem zu lösen.

5. 18. August 2026 um 14:21 UTCmonitoring

   Ingenieure konnten das Problem lösen und haben die Überwachung für weitere Probleme wieder aufgenommen.

6. 19. August 2026 um 08:20 UTCresolved

   Unsere Ingenieure haben über den Abend überwacht und bestätigt, dass dies jetzt gelöst ist

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 8. August 2026 um 11:08 UTCinvestigating

   Exclaimer Engineers are investigating an issue within the UK that is preventing data from synchronizing to Exclaimer correctly. Initial reviews indicate the issue is only impacting UK-based subscriptions

2. 8. August 2026 um 11:15 UTCinvestigating

   After an initial investigation, the issue appears to be widespread; engineers are mobilizing fully to address the service issue. User data that has been synchronized to Exclaimer previously will continue to be displayed as expected.

3. 8. August 2026 um 12:28 UTCidentified

   Exclaimer Engineers have identified the cause of the error, and initial attempts to remediate the issue have not been successful at this time. The team is continuing to work to resolve the error. User data that has been synchronized to Exclaimer previously will continue to be displayed as expected. Another update will be provided within the next hour.

4. 8. August 2026 um 13:08 UTCidentified

   Engineers have been able to identify and confirm a fix and are implementing it in all impacted regions now.

5. 8. August 2026 um 13:34 UTCmonitoring

   Exclaimer engineers have now applied the fix to all impacted regions and have confirmed that data is synchronizing as expected for subscriptions. We are now continuing to monitor for any unexpected issues.

6. 8. August 2026 um 15:00 UTCresolved

   No further signs or unexpected errors have occurred since the remediation action was taken, and user data is now synchronising to Exclaimer as expected. If you are seeing issues with user information not appearing within Exclaimer as expected, please attempt to manually synchronise user data from within the Exclaimer Portal.

1. 4. August 2026 um 19:14 UTCinvestigating

   We are currently seeing an increase in imprint failures for messages processed in the US1 datacenter.

2. 4. August 2026 um 19:38 UTCidentified

   We have identified an issue with the auto scaling on key services. These have been manually scaled and we are seeing recovery.

3. 4. August 2026 um 19:54 UTCmonitoring

   Imprinting has now recovered and is operationsl once more. Engineers will continue to monitor the situation.

4. 5. August 2026 um 06:34 UTCresolved

   This incident has been resolved.

1. 31. Juli 2026 um 12:59 UTCinvestigating

   Exclaimer Engineers untersuchen derzeit ein potenzielles Problem mit der Zustellung von Postströmen in der US-Region. Es wurden vorbeugende Maßnahmen ergriffen, um das Problem zu mildern, und wenn möglich werden weitere Informationen bereitgestellt.

2. 31. Juli 2026 um 13:26 UTCmonitoring

   Die angewandten präventiven Botschaften haben die mögliche Verzögerung effektiv stabilisiert. Ingenieure überwachen weiterhin auf Anzeichen weiterer Probleme.

3. 3. August 2026 um 07:21 UTCresolved

   Unsere Ingenieure überwachten über das Wochenende und den Postfluss wie gewohnt.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 25. Juli 2026 um 22:07 UTCinvestigating

   Wir untersuchen derzeit die wiederkehrende Instabilität unserer US-Region Postgres-Datenbankinfrastruktur. Dies wird durch ein zugrunde liegendes Azure-Infrastrukturproblem verursacht (Tracking ID: SRV7-K0G). Einige US-Kunden können in diesem Fenster intermittierende Probleme mit der Active Directory-Synchronisierung und der Admin-Benutzeroberfläche haben. Wir arbeiten mit Microsoft Azure zusammen, um dies so schnell wie möglich zu beheben. Wir werden alle 30 Minuten Updates bereitstellen. Begonnen: 25 Jul 2026, 22:20 BST

2. 25. Juli 2026 um 22:10 UTCinvestigating

   Wir werden dieses Problem weiter untersuchen.

3. 26. Juli 2026 um 00:09 UTCidentified

   Das Problem wurde identifiziert und ein Fix wird implementiert. E-Mail-Zustellung und Signaturanwendung sind nicht betroffen und funktionieren weiterhin normal. Es sind keine Kundendaten verloren gegangen. Nach dem vorherigen Vorfall in den USA am 23. Juli erholte sich eine der Datenbankrepliken nicht normal, nachdem der Ausfall behoben worden war, und wegen dieser Speicherung wurde schnell auf dem primären Datenbankserver aufgebraucht. Die Erholung ist im Gange und die Replikation holt langsam auf, wir erwarten, dass dies im Laufe des Sonntags geschieht. Die festgestellten Auswirkungen gelten weiterhin, da wir die Datensynchronisationsversuche (einschließlich SCIM und HRIS) vorübergehend angehalten haben, um die Wiederherstellung abzuschließen. Wir werden das nächste Update innerhalb von 12 Stunden bereitstellen.

4. 26. Juli 2026 um 09:15 UTCmonitoring

   Update - 26 Jul 2026, 10:15 BST Die Datenbankwiederherstellung ist über Nacht vor dem Zeitplan abgeschlossen. Die Speicherung ist auf ein normales Niveau zurückgekehrt und die Replikation ist vollständig aufgeholt. Wir sind derzeit dabei, angehaltene Dienste wieder zu aktivieren. Wir werden die betroffenen Komponenten auf Operational aktualisieren, sobald die Dienste vollständig wiederhergestellt wurden. E-Mail-Zustellung und Signaturanwendung funktionieren weiterhin normal.

5. 26. Juli 2026 um 15:24 UTCresolved

   Update - 26 Jul 2026, 16:25 BST Alle Dienste wurden vollständig wiederhergestellt. Datenbankspeicherung und Replikation sind gesund. Die Datensynchronisation (SCIM, HRIS) wurde normal fortgesetzt. Es gingen keine Kundendaten verloren. Wir entschuldigen uns für jegliche Unannehmlichkeiten.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 23. Juli 2026 um 15:32 UTCinvestigating

   Wir haben derzeit Probleme mit der Zustellung von E-Mail-Signaturen für Kunden in der US-Region aufgrund eines zugrunde liegenden Azure-Infrastrukturproblems in den USA. E-Mails werden zugestellt, aber Unterschriften können während dieses Fensters nicht angewendet werden. Wir arbeiten aktiv daran, den Full-Service wiederherzustellen und werden alle 30 Minuten Updates bereitstellen.

2. 23. Juli 2026 um 15:35 UTCinvestigating

   Wir werden dieses Problem weiter untersuchen.

3. 23. Juli 2026 um 16:28 UTCinvestigating

   Update - 23 Jul 2026, 17:20 BST Wir untersuchen weiterhin ein Problem mit Auswirkungen auf die Zustellung von E-Mail-Signaturen für Kunden in der US-Region, das durch ein externes Azure-Infrastrukturproblem in den USA verursacht wurde. E-Mails werden immer noch zugestellt. Signaturen können während dieses Fensters zeitweise nicht angewendet werden. Wir haben unsere US-Infrastruktur skaliert und arbeiten aktiv daran, den Full-Service wiederherzustellen.

4. 23. Juli 2026 um 17:19 UTCinvestigating

   Update - 23 Jul 2026, 18:15 BST Wir haben die Zustellung von E-Mail-Signaturen für Kunden in der US-Region wiederhergestellt. E-Mails werden jetzt mit Unterschriften geliefert. Wir beobachten die Situation weiterhin, während Microsoft das zugrunde liegende Azure West US-Infrastrukturproblem untersucht. Wir werden ein weiteres Update bereitstellen, wenn Auswirkungen festgestellt werden. Wir entschuldigen uns für jegliche Unannehmlichkeiten.

5. 23. Juli 2026 um 17:20 UTCmonitoring

   Die Zustellung von E-Mail-Signaturen wurde für Kunden in der US-Region wiederhergestellt. Während das zugrunde liegende Problem bei Azures West-US-Infrastruktur lag, haben wir Anpassungen an unseren Systemen vorgenommen, um die Auswirkungen zu verringern und den Service während des Ausfalls aufrechtzuerhalten. Wir beobachten die Situation weiterhin, während Microsoft das zugrunde liegende Azure West US-Infrastrukturproblem untersucht.

6. 23. Juli 2026 um 20:06 UTCmonitoring

   Die Zustellung von E-Mail-Signaturen wurde für Kunden in der US-Region wiederhergestellt. Während das zugrunde liegende Problem bei Azures West-US-Infrastruktur lag, haben wir Anpassungen an unseren Systemen vorgenommen, um die Auswirkungen zu verringern und den Service während des Ausfalls aufrechtzuerhalten. Wir beobachten die Situation weiterhin. Bitte kontaktieren Sie den Support, wenn Sie weitere Probleme haben. Wir entschuldigen uns für jegliche Unannehmlichkeiten.

7. 24. Juli 2026 um 08:45 UTCresolved

   Update - 24 Jul 2026, 09:30 BST Alle Dienste wurden in der gesamten US-Region vollständig wiederhergestellt. Die Zustellung von E-Mail-Signaturen funktioniert in beiden US-Rechenzentren nach dem Ausfall der Azure West US-Infrastruktur am 23. Juli 2026 normal. Wir entschuldigen uns für jede verursachte Störung.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 10. Juli 2026 um 11:03 UTCinvestigating

   Exclaimer-Ingenieure untersuchen ein Problem, bei dem einige Kunden eine "unerwartete Fehlermeldung" erhalten, wenn sie versuchen, zu den Registerkarten Signaturen, Kampagnen oder Disclaimer zu navigieren. Wenn dieses Problem auftritt, erheben Sie bitte ein Support-Ticket über den unten stehenden Link. https://support.exclaimer.com/hc/en-gb/p/raise-ticket Signaturen werden weiterhin wie erwartet auf Nachrichten sowohl über die E-Mail-Flow-Regel als auch über das Exclaimer-Add-In angewendet.

2. 10. Juli 2026 um 14:39 UTCidentified

   Exclaimer Engineers haben die Ursache des Problems identifiziert und implementieren Änderungen, um die Ursache zu beheben. Wir haben auch überprüft, dass dieses Problem eine kleine Teilmenge von Kunden betraf.

3. 10. Juli 2026 um 15:52 UTCresolved

   Eine erfolgreiche Änderung hat sich mit dem Problem befasst, einschließlich der Minderung, um zu verhindern, dass das Problem erneut auftritt. Kunden sollten beim Zugriff auf die Registerkarten Signaturen, Kampagnen oder Disclaimer keine Fehlermeldungen mehr sehen oder Probleme auftreten. Wenn Sie Probleme mit dem Exclaimer Portal haben, sammeln Sie bitte ein Support-Ticket und unser Team hilft Ihnen gerne weiter https://support.exclaimer.com/hc/en-gb/p/raise-ticket

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 1. Juli 2026 um 11:45 UTCidentified

   Exclaimer engineers are aware of an issue where messages within the UK may be impacted and fail to be delivered at this time. The team is actively working to address the issue

2. 1. Juli 2026 um 12:10 UTCmonitoring

   Exclaimer engineers have applied a fix to address the issue, ensuring no further messages will be affected. Any messages that were impacted would have been deferred for delivery and would be sent rather than failing to be delivered entirely. We will continue to monitor and provide further updates in the next hour.

3. 1. Juli 2026 um 15:41 UTCresolved

   The issue is now resolved and the all mail flow processing is operational

1. 29. Juni 2026 um 07:35 UTCinvestigating

   We were alerted to an issue with mail flow in our primary data centers. Our engineers are currently investigating and trying to resolve asap

2. 29. Juni 2026 um 08:00 UTCidentified

   Our engineers have identified the issue and are mitigating. Customers may still experience delays in mail delivery

3. 29. Juni 2026 um 08:26 UTCmonitoring

   We have mitigated the issue and mail flow is working again in all regions. We are monitoring now to ensure this has resolved the issue.

4. 29. Juni 2026 um 08:51 UTCresolved

   The incident has been resolved by our engineers and mail routing is operational across all regions. Customers may have experience mail delivery delays but these would have been delivered following retries.

1. 25. Juni 2026 um 16:48 UTCidentified

   Exclaimer is aware of an issue that may cause problems when attempting to purchase and set up Exclaimer Cloud via the Microsoft Marketplace at this time. Starting a Trial, or purchasing through an authorized reseller or directly from Exclaimer, is working as expected. More information will be provided once it is available.

2. 30. Juni 2026 um 14:53 UTCresolved

   Customers are now able to purchase and set up via Microsoft marketplace again. There was a latent configuration issue within our Microsoft tenant that only became a problem recently. We are still investigating what changed Microsoft side that lead to this becoming an issue.

1. 23. Juni 2026 um 16:33 UTCidentified

   Customers in the AU and US may experience issues with emails being quarantined by Microsoft defender due to false positive phishing detection. Our engineers are working with Microsoft to have the domain reputation cleared as soon as possible.

2. 24. Juni 2026 um 12:51 UTCidentified

   Our engineers have escalated the urgency of this with Microsoft and continue to push for updates as soon as possible.

3. 29. Juni 2026 um 12:11 UTCidentified

   Our engineers are continuing to engage with Microsoft regarding this issue and escalating to highest priority. This is only affecting mail flow of customers that are using the Engagement analytics feature. Customers can disable the Analytics feature within the Exclaimer Portal manually or contact Exclaimer Support for assistance.

4. 1. Juli 2026 um 10:13 UTCmonitoring

   Exclaimer Engineers, in cooperation with Microsoft, have been able to update their detection system to prevent our analytic links from being incorrectly identified as phishing. This change should complete replication through Microsoft 365 over the next 24 hours. Customers who have disabled analytics within the Exclaimer Portal can look to enable the Analytics feature within the Exclaimer Portal or contact Exclaimer Support for assistance if needed. We will provide another update tomorrow or when more information is available.

5. 7. Juli 2026 um 10:41 UTCresolved

   After extended monitoring, Exclaimer engineers are no longer seeing any continued instances of click-tracking links within the impacted regions being flagged by Microsoft Defender at this time. Customers who previously disabled this feature can look to enable click-tracking analytics from within the Exclaimer Cloud portal. If you are continuing to see issues, please don't hesitate to reach out to our support team, who will be able to assist.

1. 22. Juni 2026 um 19:01 UTCinvestigating

   Exclaimer engineers are aware of an issue causing some images not to appear within the signature tester result when a test is run. The same images appear as expected in the signature designer and in live messages. There is no impact on email signatures, as these images are applied as expected.

2. 23. Juni 2026 um 08:01 UTCresolved

   This incident has been resolved. Web-hosted images in the signature editor are now loading correctly across all regions. A recent update to the cloud UI's Content Security Policy inadvertently restricted external image sources, causing hosted images to fail to display. The policy has been updated to allow the required image sources, and the fix has been deployed to all production regions. We're monitoring to confirm stability. We apologize for any disruption this caused.

1. 10. Juni 2026 um 14:45 UTCinvestigating

   Exclaimer Engineers are aware of an issue that may cause messages to be delayed when sent to Exclaimer Cloud for Microsoft 365 users in the UK. More information will be provided once it is available.

2. 10. Juni 2026 um 14:52 UTCinvestigating

   Exclaimer Engineers have made a change in the UK region to prevent messages from being delivered to the affected servers. This should prevent further messages from being impacted and ensure that impacted messages are processed as expected on the next attempt.

3. 10. Juni 2026 um 15:02 UTCmonitoring

   Exclaimer Engineers have confirmed that the error rate is now dropping after a spike in both UK regions, suggesting that other actions taken have been able to address the issue. We are continuing to look into the cause whilst monitoring for any further issues.

4. 10. Juni 2026 um 15:43 UTCresolved

   After continued monitoring, we have confirmed the issue is no longer occurring. Servers that were displaying errors have been removed and replaced within our UK region to prevent the issue from reoccurring. If you are still seeing issues with mail flow when using Exclaimer at this time, please reach out to our support team directly, who will be happy to help.

1. 28. Mai 2026 um 08:40 UTCidentified

   Issue: An Azure storage failure in EU2 is resulting in delays processing messages there, engineering teams are actively mitigating the issue. Symptoms: Some messages processed in EU could be delayed. Next Update In: 30 mins or less

2. 28. Mai 2026 um 09:03 UTCmonitoring

   Exclaimer Engineers have successfully mitigated the issue and mailflow had returned to normal levels.

3. 28. Mai 2026 um 13:12 UTCresolved

   The Azure SQL database in EU2 has been fully restored by Microsoft. EU2 endpoints have been re-enabled and mailflow is balanced. All services are confirmed healthy with no further impact to customers.

1. 28. Mai 2026 um 08:01 UTCinvestigating

   Engineers are aware of an issue impacting our ability to apply signatures to messages as they are composed, the message 'Failed to acquire auth token' is displayed. There is no impact to email delivery at this time, once the issue has been resolved signatures will start to be applied again. If you have our server-side offering configured, then you will find that signatures are applied to messages after they are sent. If you have any other issues, please contact our support team who will be happy to help

2. 28. Mai 2026 um 12:16 UTCidentified

   Our team have identified the issue and are actively working on a resolution. Further updates will follow once a fix has been identified.

3. 28. Mai 2026 um 14:17 UTCmonitoring

   Engineering has successfully tested and deployed a fix for the add-in to resolve this issue. We will continue to closely monitor the add-in’s performance following the release. Please note that the speed of adoption may vary depending on Outlook cache. If you are currently experiencing any further issues with Exclaimer, please contact our Support team for assistance.

4. 28. Mai 2026 um 16:04 UTCmonitoring

   We continue to see a reduction of errors as the new version rolls out and are monitoring its progress. Please note that the speed of adoption may vary depending on Outlook cache. If you are currently experiencing any further issues with Exclaimer, please contact our Support team for assistance.

5. 29. Mai 2026 um 10:47 UTCresolved

   Microsoft have confirmed that the original issue impacting customers was the result of a server-side change that has since been reverted. Our telemetry also confirms that over 40% of customer requests are coming from the newly released version that similarly resolved customer issues prior to Microsoft's deployment reversal, this continues to roll out. We intend to leave this fix in place as it improves the add-ins resilience to possible authentication issues. If you are currently experiencing any further issues with Exclaimer, please contact our Support team for assistance.

6. 10. Juni 2026 um 17:46 UTCpostmortem

   Issue:  Client side signature fails to apply and the message 'Failed to acquire auth token' is displayed. Incident Length: 10 Day\(s\) and 3 hour\(s\)  Incident Date: 18/05/2026, 11:00 UTC - 28/05/2026, 14:05 UTC   Incident Status: Resolved   **Summary**   When composing a new email, the Exclaimer add-in was unable to acquire an authentication token, resulting in signatures not being inserted and an error message being displayed for customers using Outlook for iOS.   All other platforms, including Windows desktop, New Outlook, Mac, Web, and Android, were unaffected.   Server-side signatures continued to apply normally for customers with that configuration.  **Root Cause**   The Exclaimer Outlook Add-in uses a Microsoft authentication flow designed for Office add-ins, which is intended to authenticate users silently in the background without any user interaction. Around 18 May, this silent authentication flow stopped working on Outlook for iOS.   Following an investigation, Microsoft confirmed that a change on their side had caused the silent authentication failure, and that this change was subsequently rolled back.  **Mitigation**   On identifying where the authentication flow was failing, Exclaimer Engineers updated the Outlook Add-in \(v1.29.200\) to introduce a fallback path for when silent authentication cannot complete.   Rather than surfacing an error, the add-in now prompts the user to sign in interactively, allowing authentication to complete and the signature to be applied, improving authentication flow resilience.   This was deployed on 28 May and has been retained permanently as a resilience improvement.    **Incident Timeline**  18/05, ~11:00 UTC - Silent authentication begins failing on Outlook for iOS. Customers start experiencing signature failures on this platform   18/05, 12:51 – Exclaimer releases a new version of the Exclaimer Add-in \(v1.27.200\)   21/05, 19:01 - First report of errors from the Add-in reaches Exclaimer Engineering. Investigation begins.   22/05, 07:26 Engineering confirmed a review of the latest Add-in release had been completed; no active indicators of the issue are present based on the changes made.  10:14 – Active theory was composed on the cause of the issue; code changes are then prepared by Engineering to be released the following week to prevent potential issues over the weekend.     26/05, 10:01 UTC - First code change deployed to improve logging and extend authentication timeouts.    12:10 – Add-in v.1.28.0 is released to the production channel of the Add-in. Review of impacted systems indicates no improvement.   27/05, 13:25 UTC - v.1.29.0 is deployed to both channels to surface more detail from the authentication failure on iOS.    28/05, 07:44 UTC - Severity escalated given customer impact and duration.   10:42 – Issue confirmed to only impact iOS, with other errors likely being unrelated.    11:03 – Internal investigation is prioritized to identify the cause.   11:30 - Internal reproduction of the issue achieved for the first time, enabling rapid iteration on a fix.   13:02 - The point of failure in the authentication flow fully identified, Exclaimer Engineers also identify development of a Fix and begin prioritizing a full release.   13:50 – Add-in version \(v1.29.200\) is prepared for release, awaiting confirmation of the resolution within the preview channel before being released to the production channel.   14:05 - Updated add-in \(v1.29.200\) verified in preview and released out to production channel.   14:31 - Customer confirmation of resolution is received   29/05, 08:10 UTC - Microsoft confirms that a change on their side caused the authentication failure and that it has been rolled back. Exclaimer Engineers agree to keep the changes applied based on this information at this time.

1. 25. Mai 2026 um 04:00 UTCinvestigating

   We are investigating a possible service alert. Issue: Users are unable to receive any authentication tokens when attempting to login to https://portal.exclaimer.com using password login. The issue currently looks to only be affecting users who are logging into the Exclaimer portal using Password login. Logins using Microsoft/Google SSO currently get through without any issues. Symptoms: Users will be prompted to enter a token when trying to login to the portal but no authentication tokens are received in the user's registered email address.

2. 25. Mai 2026 um 08:49 UTCinvestigating

   We are continuing to investigate the issue to determine the root cause. Our IT will report back shortly

3. 25. Mai 2026 um 09:47 UTCinvestigating

   We are still continuing to investigate the issue to determine the root cause. Our IT will report back soon

4. 25. Mai 2026 um 10:32 UTCmonitoring

   Our engineers have found the issue and reverted a change. Authentication tokens are now being received and we are continuing to monitor.

5. 25. Mai 2026 um 10:32 UTCmonitoring

   We are continuing to monitor for any further issues.

6. 25. Mai 2026 um 10:51 UTCresolved

   Engineers have confirmed that the previous service alert has been resolved. The service is now back to full health and is working as normal. Thank you for your patience.

7. 10. Juni 2026 um 18:27 UTCpostmortem

   Issue: Authentication tokens not received via email for users accessing Exclaimer Portal  Incident Length: 7 hour\(s\) and 17 minutes  Incident Date: 25/05/2026, UTC 03:12– 10:29 UTC  Incident Status: Resolved  **Summary**  Customers logging into the Exclaimer Portal using the Username and Password option were unable to receive authentication tokens for a period of time, preventing them from being able to access the portal.   The exception did not trigger alerting that engaged our key engineering team, resulting in an extended impact time.  **Root Cause**  A process-level exception had occurred and not been successfully restarted. This resulted in token codes being generated but not emailed to users when required.  **Mitigation**  A rollback of the key service that included this process resolved the issue and allowed for a backlog of token code messages that had been generated to be cleared and distributed, which then restored standard service.      Further improvements to internal escalation and alerting processes have been put into place to reduce the delay in acknowledging the issue and beginning resolution steps over public holidays.  **Incident Timeline**  03:12 - Exclaimer Engineers identify a possible issue with customers being unable to log in to the portal when using a Username and Password.    03:36 – Further testing confirms the issue is impacting the authentication code stage, where the email is never received. Other forms of authentication are working as expected.   03:18 – Status page is updated to ensure customers are aware of the issue and to advise alternative login methods.   07:37 – Exclaimer Engineering is alerted and begins to investigate the scope of the issue. Additional engineering resources are called in to investigate the cause.   08:51 – A rollback of the last set of changes made to the service is performed. Testing begins to see if the issue continues   09:04 – Exclaimer Engineers identify the issue is still ongoing despite the rollback work   09:26 - Engineers confirm that the token codes are being generated as expected, indicating the service runs as anticipated to ensure accounts are secure.   09:40 – Consistent replication of the issue is confirmed, expediting testing and remediation processes.   09:59 – Exclaimer Engineers complete further system rollbacks to address the issue.   10:19 – Engineering note that a group of token code messages are confirmed to have been sent as expected and are also received within the mailboxes of accounts.   10:29 – Log review indicates that all submitted codes are processed as expected and new requests for token codes are received by users as expected.

1. 19. Mai 2026 um 16:23 UTCresolved

   Exclaimer Customers using Exclaimer Cloud for Microsoft 365 would have encountered an error when attempting to run the connector setup wizard from the 'Manage Mail Flow' page, causing the wizard to fail to run. This issue would have no impact on customers who have not previously run the Connector Setup wizard for Microsoft 365

1. 11. Mai 2026 um 17:33 UTCinvestigating

   Exclaimer Engineers are looking into an issue that will result in customers seeing signatures are applied after a short delay at this time. More information will be provided when possible.

2. 11. Mai 2026 um 17:45 UTCmonitoring

   Engineers have confirmed that the issue has been addressed with additional capacity being utilized within the UK. They are now monitoring for any further issues.

3. 12. Mai 2026 um 08:43 UTCresolved

   This incident has been resolved.