Historial de interrupciones de Exclaimer

1. 27 de agosto de 2026 a las 10:14 UTCidentified

   El personal de apoyo a las reclamaciones está abordando una cuestión que está afectando la entrega de respuestas de correo electrónico de nuestro equipo de apoyo. Si tiene un ticket de soporte continuo, puede iniciar sesión en el portal de soporte para comprobar cualquier actualización potencial y responder al ingeniero de soporte asignado a su caso. Puede acceder a sus entradas actuales y responder al Ingeniero de Apoyo asignado siguiendo los pasos indicados en esta guía: https://support.exclaimer.com/hc/en-gb/articles/9389259466141

2. 28 de agosto de 2026 a las 8:35 UTCresolved

   El personal de exclamación ha hecho un cambio interno, y la vigilancia indica que la cuestión se ha resuelto completamente. Si tiene un boleto abierto con nuestro equipo de soporte y no ha recibido una respuesta esta semana, por favor, siga su caso por correo electrónico o directamente a través de nuestro portal web. Para acceder a sus entradas actuales y responder a nuestro equipo de apoyo, sírvanse seguir las medidas que figuran en esta guía: https://support.exclaimer.com/hc/en-gb/articles/9389259466141.

Traducido automáticamente desde la actualización oficial del incidente.

1. 20 de agosto de 2026 a las 12:34 UTCinvestigating

   Los ingenieros son conscientes de un problema que afecta al Diseñador de Firmas, lo que impide que algunos clientes editen plantillas de firma. No hay impacto en el flujo de correo o la entrega de firma en este momento. Estamos investigando y proporcionaremos una actualización adicional dentro de 60 minutos.

2. 20 de agosto de 2026 a las 12:59 UTCmonitoring

   Los ingenieros de Exclaimer han resuelto el problema, y los clientes ya no deben experimentar ningún problema al utilizar el Diseñador de Firmas. Ahora estamos monitoreando para otras cuestiones.

3. 20 de agosto de 2026 a las 16:08 UTCresolved

   Los ingenieros han confirmado que se ha resuelto la alerta de servicio anterior. El servicio está ahora de vuelta a la salud plena y está trabajando como normal. Gracias por su paciencia.

Traducido automáticamente desde la actualización oficial del incidente.

1. 18 de agosto de 2026 a las 8:31 UTCinvestigating

   Exclaimer Engineers son conscientes de un problema transitorio que puede causar ciertas páginas, como Branding, Campaigns y Disclaimers, para no cargar a clientes dentro del Portal Exclaimer. Se está realizando un trabajo de rehabilitación para restaurar el acceso a estas secciones del portal. Las firmas siguen siendo aplicadas a los correos electrónicos. Si usted está viendo que las firmas no están siendo aplicadas, por favor contacte con nuestro equipo de soporte, que estará encantado de ayudar.

2. 18 de agosto de 2026 a las 10:39 UTCmonitoring

   Nuestros ingenieros han resuelto el problema, y los clientes ya no deben experimentar ningún problema al utilizar el Portal de Exclaimer Cloud. Ahora estamos monitoreando para asegurar que la estabilidad permanezca. Si continúas viendo problemas, por favor no dudes en contactar con nuestro equipo de apoyo, que estará encantado de ayudar.

3. 18 de agosto de 2026 a las 12:23 UTCmonitoring

   Exclaimer Ingenieros son conscientes de los informes del Diseñador de Firmas que no se cargan para algunos clientes. Se han tomado acciones iniciales de remediación, y el Diseñador de Firmas debe cargar ahora como se espera para los usuarios. Estamos investigando la causa del problema ahora

4. 18 de agosto de 2026 a las 13:21 UTCidentified

   Hemos identificado un problema dentro del portal donde algunos botones no están respondiendo a clics para algunos usuarios. Los ingenieros están trabajando ahora para resolver el problema.

5. 18 de agosto de 2026 a las 14:21 UTCmonitoring

   Los ingenieros han podido resolver la cuestión y han reanudado la supervisión de otras cuestiones.

6. 19 de agosto de 2026 a las 8:20 UTCresolved

   Nuestros ingenieros han monitoreado durante la noche y confirmado que ahora se resuelve

Traducido automáticamente desde la actualización oficial del incidente.

1. 8 de agosto de 2026 a las 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 de agosto de 2026 a las 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 de agosto de 2026 a las 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 de agosto de 2026 a las 13:08 UTCidentified

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

5. 8 de agosto de 2026 a las 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 de agosto de 2026 a las 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 de agosto de 2026 a las 19:14 UTCinvestigating

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

2. 4 de agosto de 2026 a las 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 de agosto de 2026 a las 19:54 UTCmonitoring

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

4. 5 de agosto de 2026 a las 6:34 UTCresolved

   This incident has been resolved.

1. 31 de julio de 2026 a las 12:59 UTCinvestigating

   Exclaimer Ingenieros están investigando un posible problema de entrega de flujo de correo dentro de la región estadounidense en este momento. Se han adoptado medidas preventivas para mitigar la cuestión y se proporcionará más información cuando sea posible.

2. 31 de julio de 2026 a las 13:26 UTCmonitoring

   Los mensajes preventivos aplicados han estabilizado efectivamente el posible retraso. Los ingenieros siguen supervisando cualquier signo de nuevas cuestiones.

3. 3 de agosto de 2026 a las 7:21 UTCresolved

   Nuestros ingenieros monitorearon durante el fin de semana y el flujo de correo mientras avanzaba como normal.

Traducido automáticamente desde la actualización oficial del incidente.

1. 25 de julio de 2026 a las 22:07 UTCinvestigating

   Actualmente estamos investigando inestabilidad recurrente que afecta a nuestra infraestructura de bases de datos Postgres de la región de Estados Unidos. Esto es causado por un problema subyacente de infraestructura Azure (Tracking ID: SRV7-K0G). Algunos clientes de EE.UU. pueden experimentar problemas intermitentes con la sincronización Active Directory y la interfaz de usuario de admin durante esta ventana. Estamos trabajando con Microsoft Azure para resolver esto lo más rápido posible. Proporcionaremos actualizaciones cada 30 minutos. Inicio: 25 jul 2026, 22:20 BST

2. 25 de julio de 2026 a las 22:10 UTCinvestigating

   Seguimos investigando esta cuestión.

3. 26 de julio de 2026 a las 0:09 UTCidentified

   Se ha determinado la cuestión y se está aplicando una solución. La entrega de correo electrónico y la solicitud de firma no están afectadas y siguen operando normalmente. No se han perdido datos de clientes. Después del incidente anterior en EE.UU. el 23 de julio, una de las réplicas de la base de datos no se recuperó normalmente después de que se resolvió el outage, y debido a este almacenamiento se utilizó rápidamente en el servidor principal de la base de datos. La recuperación está en progreso y la replicación está llegando lentamente, esperamos que esto suceda durante el curso del domingo. Los impactos observados todavía se aplican ya que hemos pausado temporalmente los intentos de sincronización de datos (incluyendo SCIM y HRIS) para completar la recuperación. Proporcionaremos la siguiente actualización dentro de 12 horas.

4. 26 de julio de 2026 a las 9:15 UTCmonitoring

   Actualización - 26 jul 2026, 10:15 BST La recuperación de bases de datos se ha completado durante la noche anterior a la fecha prevista. El almacenamiento ha regresado a niveles normales y la replicación está completamente atrapada. Actualmente estamos en el proceso de reinstalación de los servicios de pausa. Actualizaremos los componentes afectados a Operaciones una vez que se hayan restaurado completamente los servicios. La entrega de correo electrónico y la aplicación de firma siguen funcionando normalmente.

5. 26 de julio de 2026 a las 15:24 UTCresolved

   Actualización - 26 jul 2026, 16:25 BST Todos los servicios han sido totalmente restaurados. El almacenamiento y la replicación de bases de datos son saludables. La sincronización de datos (SCIM, HRIS) se ha reanudado normalmente. No se perdieron datos de clientes. Nos disculpamos por cualquier inconveniente causado.

Traducido automáticamente desde la actualización oficial del incidente.

1. 23 de julio de 2026 a las 15:32 UTCinvestigating

   Actualmente estamos experimentando problemas con la entrega de firmas de correo electrónico para clientes en la región de EE.UU. debido a un problema de infraestructura Azure subyacente en EE.UU. Occidental. Los correos electrónicos están siendo entregados, pero las firmas no se pueden aplicar durante esta ventana. Trabajamos activamente para restaurar el servicio completo y proporcionaremos actualizaciones cada 30 minutos.

2. 23 de julio de 2026 a las 15:35 UTCinvestigating

   Seguimos investigando esta cuestión.

3. 23 de julio de 2026 a las 16:28 UTCinvestigating

   Actualización - 23 jul 2026, 17:20 BST Seguimos investigando un problema que afecta a la entrega de firmas de correo electrónico para clientes en la región de Estados Unidos, causado por un problema externo de infraestructura Azure en Estados Unidos Occidental. El correo electrónico sigue siendo entregado. Las firmas pueden no aplicarse intermitentemente durante esta ventana. Hemos escalado nuestra infraestructura estadounidense y estamos trabajando activamente para restaurar el servicio completo.

4. 23 de julio de 2026 a las 17:19 UTCinvestigating

   Actualización - 23 jul 2026, 18:15 BST Hemos restaurado la entrega de firmas de correo electrónico para clientes en la región de Estados Unidos. Los correos electrónicos se están entregando con firmas aplicadas. Continuamos monitoreando la situación mientras Microsoft investiga el problema subyacente de la infraestructura de Azure West US. Proporcionaremos una actualización adicional si se detecta algún impacto. Nos disculpamos por cualquier inconveniente causado.

5. 23 de julio de 2026 a las 17:20 UTCmonitoring

   La entrega de firma de correo electrónico ha sido restaurada para clientes en la región de Estados Unidos. Mientras que el problema subyacente era con la infraestructura de EE.UU. Occidental de Azure, hicimos ajustes a nuestros sistemas para mitigar el impacto y mantener el servicio durante la salida. Continuamos monitoreando la situación mientras Microsoft investiga el problema subyacente de la infraestructura de Azure West US.

6. 23 de julio de 2026 a las 20:06 UTCmonitoring

   La entrega de firma de correo electrónico ha sido restaurada para clientes en la región de Estados Unidos. Mientras que el problema subyacente era con la infraestructura de EE.UU. Occidental de Azure, hicimos ajustes a nuestros sistemas para mitigar el impacto y mantener el servicio durante la salida. Seguimos vigilando la situación. Por favor, contacte con soporte si experimenta otros problemas. Nos disculpamos por cualquier inconveniente causado.

7. 24 de julio de 2026 a las 8:45 UTCresolved

   Actualización - 24 jul 2026, 09:30 BST Todos los servicios han sido totalmente restaurados en toda la región de Estados Unidos. La entrega de firmas de correo electrónico funciona normalmente en ambos centros de datos estadounidenses tras la superación de infraestructura de Azure West US el 23 de julio de 2026. Nos disculpamos por cualquier perturbación causada.

Traducido automáticamente desde la actualización oficial del incidente.

1. 10 de julio de 2026 a las 11:03 UTCinvestigating

   Los ingenieros de Exclaimer están investigando un problema donde algunos clientes pueden recibir una página de "error no esperado" al intentar navegar a las pestañas de Signatures, Campañas o Descargos. Si está experimentando este problema, por favor levante un ticket de soporte usando el enlace de abajo. https://support.exclaimer.com/hc/en-gb/p/raise-ticket Las firmas siguen siendo aplicadas como se espera a los mensajes a través de la regla de flujo de correo y el complemento Exclaimer.

2. 10 de julio de 2026 a las 14:39 UTCidentified

   Exclaimer Engineers han identificado la causa del problema y están implementando cambios para abordar la causa. También hemos verificado que este problema afectaba a un pequeño subconjunto de clientes.

3. 10 de julio de 2026 a las 15:52 UTCresolved

   A successful change has addressed the issue, including mitigation to prevent the issue from occurring again. Los clientes ya no deben ver ningún mensaje de error o encontrar problemas al acceder a las pestañas Signatures, Campañas o Descargos. Si usted está experimentando algún problema con el Portal de Exclaimer, por favor levante un ticket de soporte, y nuestro equipo estará encantado de ayudar https://support.exclaimer.com/hc/en-gb/p/raise-ticket

Traducido automáticamente desde la actualización oficial del incidente.

1. 1 de julio de 2026 a las 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 de julio de 2026 a las 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 de julio de 2026 a las 15:41 UTCresolved

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

1. 29 de junio de 2026 a las 7: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 de junio de 2026 a las 8:00 UTCidentified

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

3. 29 de junio de 2026 a las 8: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 de junio de 2026 a las 8: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 de junio de 2026 a las 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 de junio de 2026 a las 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 de junio de 2026 a las 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 de junio de 2026 a las 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 de junio de 2026 a las 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 de julio de 2026 a las 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 de julio de 2026 a las 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 de junio de 2026 a las 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 de junio de 2026 a las 8: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 de junio de 2026 a las 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 de junio de 2026 a las 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 de junio de 2026 a las 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 de junio de 2026 a las 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 de mayo de 2026 a las 8: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 de mayo de 2026 a las 9:03 UTCmonitoring

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

3. 28 de mayo de 2026 a las 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 de mayo de 2026 a las 8: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 de mayo de 2026 a las 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 de mayo de 2026 a las 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 de mayo de 2026 a las 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 de mayo de 2026 a las 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 de junio de 2026 a las 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 de mayo de 2026 a las 4: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 de mayo de 2026 a las 8:49 UTCinvestigating

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

3. 25 de mayo de 2026 a las 9:47 UTCinvestigating

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

4. 25 de mayo de 2026 a las 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 de mayo de 2026 a las 10:32 UTCmonitoring

   We are continuing to monitor for any further issues.

6. 25 de mayo de 2026 a las 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 de junio de 2026 a las 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 de mayo de 2026 a las 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 de mayo de 2026 a las 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 de mayo de 2026 a las 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 de mayo de 2026 a las 8:43 UTCresolved

   This incident has been resolved.