Histórico de interrupções do Exclaimer

1. 27 Eost 2026 da 10:14 UTCidentified

   A equipe de suporte do Exclaimer está atualmente abordando um problema que está afetando a entrega de respostas de email da nossa equipe de suporte. Se você tiver um ticket de suporte contínuo, você pode entrar no portal de suporte para verificar se há atualizações potenciais e responder ao engenheiro de suporte atribuído ao seu caso. Você pode acessar seus tickets atuais e responder ao Engenheiro de Suporte atribuído seguindo as etapas descritas neste guia: https://support.exclaimer.com/hc/en-gb/articles/9389259466141

2. 28 Eost 2026 da 08:35 UTCresolved

   O pessoal do Exclamador fez uma alteração interna, e o acompanhamento indica que a questão foi agora completamente resolvida. Se você tem um ticket aberto com nossa equipe de suporte e não recebeu uma resposta esta semana, por favor, acompanhe o seu caso via e-mail ou diretamente através do nosso portal web. Para acessar seus tickets atuais e responder à nossa equipe de suporte, siga as etapas fornecidas neste guia: https://support.exclaimer.com/hc/en-gb/artigos/9389259466141.

Traduzido automaticamente da atualização oficial do incidente.

1. 20 Eost 2026 da 12:34 UTCinvestigating

   Os engenheiros estão cientes de um problema que afeta o Signature Designer, o que está impedindo alguns clientes de editar modelos de assinatura. Não há impacto no fluxo de correio ou entrega de assinatura neste momento. Estamos investigando e forneceremos uma atualização adicional dentro de 60 minutos.

2. 20 Eost 2026 da 12:59 UTCmonitoring

   Engenheiros de Exclaimer resolveram o problema, e os clientes não devem mais ter problemas ao usar o Designer de Assinaturas. Estamos agora a acompanhar quaisquer outras questões.

3. 20 Eost 2026 da 16:08 UTCresolved

   Os engenheiros confirmaram que o alerta de serviço anterior foi resolvido. O serviço está agora de volta à plena saúde e está funcionando como normal. Obrigado pela vossa paciência.

Traduzido automaticamente da atualização oficial do incidente.

1. 18 Eost 2026 da 08:31 UTCinvestigating

   Os Engenheiros Exclaimer estão cientes de um problema transitório que pode fazer com que certas páginas, como Branding, Campanhas e Avisos Legais, não carreguem para clientes dentro do Portal Exclaimer. Estão em curso trabalhos de reparação para restaurar o acesso a estas secções do portal. As assinaturas ainda estão sendo aplicadas aos e-mails. Se você estiver vendo que as assinaturas não estão sendo aplicadas, entre em contato com nossa equipe de suporte, que ficará feliz em ajudar.

2. 18 Eost 2026 da 10:39 UTCmonitoring

   Nossos engenheiros resolveram o problema, e os clientes não devem mais ter problemas ao usar o Portal Exclaimer Cloud. Estamos agora a acompanhar para assegurar que a estabilidade permaneça. Se você continuar a ver problemas, não hesite em contatar nossa equipe de suporte, que ficará feliz em ajudar.

3. 18 Eost 2026 da 12:23 UTCmonitoring

   Exclaimer Engenheiros estão cientes de relatórios sobre o Designer de Assinatura falhando em carregar para alguns clientes. As ações iniciais de remediação foram tomadas, e o Signature Designer deve agora carregar como esperado para os usuários. Estamos a investigar a causa da questão agora

4. 18 Eost 2026 da 13:21 UTCidentified

   Identificamos um problema dentro do portal onde alguns botões não estão respondendo a cliques para alguns usuários. Os engenheiros estão a trabalhar para resolver o problema.

5. 18 Eost 2026 da 14:21 UTCmonitoring

   Os engenheiros foram capazes de resolver o problema e retomaram o acompanhamento de quaisquer outras questões.

6. 19 Eost 2026 da 08:20 UTCresolved

   Os nossos engenheiros acompanharam durante a noite e confirmaram que isto está resolvido

Traduzido automaticamente da atualização oficial do incidente.

1. 8 Eost 2026 da 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 Eost 2026 da 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 Eost 2026 da 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 Eost 2026 da 13:08 UTCidentified

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

5. 8 Eost 2026 da 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 Eost 2026 da 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 Eost 2026 da 19:14 UTCinvestigating

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

2. 4 Eost 2026 da 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 Eost 2026 da 19:54 UTCmonitoring

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

4. 5 Eost 2026 da 06:34 UTCresolved

   This incident has been resolved.

1. 31 Gouere 2026 da 12:59 UTCinvestigating

   Engenheiros Exclaimer estão investigando um potencial problema de entrega de fluxo de correio na região dos EUA neste momento. Foram tomadas medidas preventivas para atenuar a questão e, sempre que possível, serão fornecidas mais informações.

2. 31 Gouere 2026 da 13:26 UTCmonitoring

   As mensagens preventivas aplicadas estabilizaram efetivamente o potencial atraso. Os engenheiros continuam a monitorizar quaisquer sinais de outros problemas.

3. 3 Eost 2026 da 07:21 UTCresolved

   Nossos engenheiros monitoraram durante o fim de semana e o fluxo de correio como tendo progredido como normal.

Traduzido automaticamente da atualização oficial do incidente.

1. 25 Gouere 2026 da 22:07 UTCinvestigating

   Atualmente estamos investigando instabilidade recorrente afetando nossa infraestrutura de banco de dados da região dos EUA Postgres. Isto é causado por um problema de infraestrutura subjacente ao Azure (Tracking ID: SRV7-K0G). Alguns clientes dos EUA podem ter problemas intermitentes com a sincronização do Active Directory e a interface de usuário do administrador durante esta janela. Estamos trabalhando com a Microsoft Azure para resolver isso o mais rápido possível. Nós forneceremos atualizações a cada 30 minutos. Iniciado: 25 jul 2026, 22:20 BST

2. 25 Gouere 2026 da 22:10 UTCinvestigating

   Continuamos a investigar esta questão.

3. 26 Gouere 2026 da 00:09 UTCidentified

   A questão foi identificada e está a ser implementada uma solução. O aplicativo de entrega de e-mail e assinatura não são afetados e continuam a operar normalmente. Nenhum dado do cliente foi perdido. Após o incidente anterior nos EUA em 23 de julho uma das réplicas do banco de dados não se recuperou normalmente depois que a falha foi resolvida, e por causa desse armazenamento foi rapidamente usado no servidor de banco de dados primário. A recuperação está em curso e a replicação está a recuperar lentamente, esperamos que isso aconteça ao longo do domingo. Os impactos observados ainda se aplicam à medida que pausamos temporariamente as tentativas de sincronização de dados (incluindo SCIM e HRIS) para completar a recuperação. Forneceremos a próxima atualização dentro de 12 horas.

4. 26 Gouere 2026 da 09:15 UTCmonitoring

   Atualização - 26 jul 2026, 10:15 BST A recuperação da base de dados terminou durante a noite antes do previsto. O armazenamento retornou aos níveis normais e a replicação está totalmente presa. Estamos atualmente em processo de re-enviar serviços pausados. Atualizaremos os componentes afetados para operacional uma vez que os serviços tenham sido totalmente restaurados. O aplicativo de entrega de e-mail e assinatura continuam funcionando normalmente.

5. 26 Gouere 2026 da 15:24 UTCresolved

   Atualização - 26 jul 2026, 16:25 BST Todos os serviços foram totalmente restaurados. O armazenamento e a replicação do banco de dados são saudáveis. A sincronização dos dados (SCIM, HRIS) retomou normalmente. Nenhum dado do cliente foi perdido. Pedimos desculpa por qualquer inconveniente causado.

Traduzido automaticamente da atualização oficial do incidente.

1. 23 Gouere 2026 da 15:32 UTCinvestigating

   Atualmente estamos tendo problemas com entrega de assinatura de e-mail para clientes na região dos EUA devido a um problema de infraestrutura subjacente Azure nos EUA ocidentais. Os e- mails estão a ser entregues, mas as assinaturas podem não ser aplicadas durante esta janela. Estamos trabalhando ativamente para restaurar o serviço completo e fornecer atualizações a cada 30 minutos.

2. 23 Gouere 2026 da 15:35 UTCinvestigating

   Continuamos a investigar esta questão.

3. 23 Gouere 2026 da 16:28 UTCinvestigating

   Atualização - 23 jul 2026, 17:20 BST Continuamos a investigar um problema que afeta a entrega de assinatura de e-mail para clientes na região dos EUA, causado por um problema de infraestrutura externa Azure nos EUA ocidentais. O e-mail ainda está a ser entregue. As assinaturas podem não ser aplicadas intermitentemente durante esta janela. Nós escalamos nossa infraestrutura dos EUA e estamos trabalhando ativamente para restaurar o serviço completo.

4. 23 Gouere 2026 da 17:19 UTCinvestigating

   Atualização - 23 jul 2026, 18:15 BST Nós restauramos a entrega de assinatura de email para clientes na região dos EUA. E-mails estão sendo entregues com assinaturas aplicadas. Continuamos a monitorizar a situação enquanto a Microsoft investiga a questão subjacente da infra-estrutura da Azure West US. Nós forneceremos uma atualização adicional se algum impacto for detectado. Pedimos desculpa por qualquer inconveniente causado.

5. 23 Gouere 2026 da 17:20 UTCmonitoring

   A entrega de assinatura de email foi restaurada para clientes na região dos EUA. Enquanto o problema subjacente era com a infraestrutura dos EUA ocidentais da Azure, fizemos ajustes em nossos sistemas para mitigar o impacto e manter o serviço durante a interrupção. Continuamos a monitorizar a situação enquanto a Microsoft investiga a questão subjacente da infra-estrutura da Azure West US.

6. 23 Gouere 2026 da 20:06 UTCmonitoring

   A entrega de assinatura de email foi restaurada para clientes na região dos EUA. Enquanto o problema subjacente era com a infraestrutura dos EUA ocidentais da Azure, fizemos ajustes em nossos sistemas para mitigar o impacto e manter o serviço durante a interrupção. Continuamos a acompanhar a situação. Por favor contacte o suporte se tiver mais problemas. Pedimos desculpa por qualquer inconveniente causado.

7. 24 Gouere 2026 da 08:45 UTCresolved

   Atualização - 24 jul 2026, 09:30 BST Todos os serviços foram totalmente restaurados em toda a região dos EUA. A entrega de assinatura de e-mail está funcionando normalmente em ambos os datacenters dos EUA após a falha de infraestrutura Azure West EUA em 23 de julho de 2026. Pedimos desculpa por qualquer perturbação causada.

Traduzido automaticamente da atualização oficial do incidente.

1. 10 Gouere 2026 da 11:03 UTCinvestigating

   Engenheiros Exclaimer estão investigando um problema onde alguns clientes podem receber uma página 'erro inesperado ocorrido' ao tentar navegar para as abas Assinaturas, Campanhas ou Avisos de Renúncia. Se você está experimentando este problema, por favor levante um ticket de suporte usando o link abaixo. https://support.exclaimer.com/hc/en-gb/p/raise-ticket As assinaturas continuam a ser aplicadas conforme esperado às mensagens através da regra de fluxo de correio e do suplemento Exclaimer.

2. 10 Gouere 2026 da 14:39 UTCidentified

   Exclaimer Engenheiros identificaram a causa do problema e estão implementando mudanças para lidar com a causa. Verificamos também que esta questão afetou um pequeno subconjunto de clientes.

3. 10 Gouere 2026 da 15:52 UTCresolved

   Uma mudança bem sucedida abordou a questão, incluindo mitigação para evitar que a questão ocorra novamente. Os clientes não devem mais ver mensagens de erro ou encontrar quaisquer problemas ao acessar as abas Assinaturas, Campanhas ou Avisos. Se você estiver tendo quaisquer problemas com o Portal Exclaimer, por favor levante um ticket de suporte, e nossa equipe ficará feliz em ajudar https://support.exclaimer.com/hc/en-gb/p/raise-ticket

Traduzido automaticamente da atualização oficial do incidente.

1. 1 Gouere 2026 da 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 Gouere 2026 da 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 Gouere 2026 da 15:41 UTCresolved

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

1. 29 Mezheven 2026 da 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 Mezheven 2026 da 08:00 UTCidentified

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

3. 29 Mezheven 2026 da 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 Mezheven 2026 da 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 Mezheven 2026 da 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 Mezheven 2026 da 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 Mezheven 2026 da 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 Mezheven 2026 da 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 Mezheven 2026 da 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 Gouere 2026 da 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 Gouere 2026 da 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 Mezheven 2026 da 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 Mezheven 2026 da 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 Mezheven 2026 da 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 Mezheven 2026 da 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 Mezheven 2026 da 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 Mezheven 2026 da 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 Mae 2026 da 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 Mae 2026 da 09:03 UTCmonitoring

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

3. 28 Mae 2026 da 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 Mae 2026 da 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 Mae 2026 da 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 Mae 2026 da 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 Mae 2026 da 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 Mae 2026 da 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 Mezheven 2026 da 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 Mae 2026 da 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 Mae 2026 da 08:49 UTCinvestigating

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

3. 25 Mae 2026 da 09:47 UTCinvestigating

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

4. 25 Mae 2026 da 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 Mae 2026 da 10:32 UTCmonitoring

   We are continuing to monitor for any further issues.

6. 25 Mae 2026 da 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 Mezheven 2026 da 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 Mae 2026 da 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 Mae 2026 da 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 Mae 2026 da 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 Mae 2026 da 08:43 UTCresolved

   This incident has been resolved.