Istoricul incidentelor Exclaimer

1. 27 august 2026 la 10:14 UTCidentified

   Personalul de sprijin Exclaimer abordează în prezent o problemă care afectează furnizarea de răspunsuri prin e-mail de la echipa noastră de sprijin. Dacă aveți un bilet de sprijin în curs de desfășurare, vă puteți conecta la portalul de sprijin pentru a verifica orice actualizări potențiale și de a răspunde la inginerul de sprijin atribuit cazului dumneavoastră. Puteți accesa biletele curente și răspunde inginerului de sprijin desemnat urmând pașii prezentați în acest ghid: https://support.exclaimer.com/hc/en-gb/articles/9389259466141

2. 28 august 2026 la 08:35 UTCresolved

   Personalul de la Exclaimer a făcut o schimbare internă, iar monitorizarea indică faptul că problema a fost acum rezolvată complet. Dacă aveți un bilet deschis cu echipa noastră de sprijin și nu au primit un răspuns în această săptămână, vă rugăm să urmăriți cazul dvs. prin e-mail sau direct prin intermediul portalului nostru web. Pentru a accesa biletele curente și a răspunde echipei noastre de sprijin, vă rugăm să urmați pașii furnizați în acest ghid: https://support.exclaimer.com/hc/en-gb/articles/9389259466141.

Traducere automată din actualizarea oficială a incidentului.

1. 20 august 2026 la 12:34 UTCinvestigating

   Inginerii sunt conștienți de o problemă care afectează Signature Designer, care împiedică unii clienți să editeze șabloane de semnătură. Nu există niciun impact asupra fluxului de poștă sau a livrării semnăturii în acest moment. Investigăm şi vom oferi o nouă actualizare în 60 de minute.

2. 20 august 2026 la 12:59 UTCmonitoring

   Inginerii Exclaimer au rezolvat problema, iar clienții nu ar trebui să mai experimenteze probleme atunci când utilizează Signature Designer. Acum monitorizăm orice alte probleme.

3. 20 august 2026 la 16:08 UTCresolved

   Inginerii au confirmat că alerta de serviciu anterioară a fost rezolvată. Serviciul a revenit la starea de sănătate şi funcţionează normal. Mulţumesc pentru răbdare.

Traducere automată din actualizarea oficială a incidentului.

1. 18 august 2026 la 08:31 UTCinvestigating

   Inginerii Exclaimer sunt conștienți de o problemă tranzitorie care poate provoca anumite pagini, cum ar fi Branding, campanii, și Disclaiers, să nu se încarce pentru clienții din cadrul portalului Exclaimer. Remediarea este în curs de desfășurare pentru a restabili accesul la aceste secțiuni ale portalului. Semnăturile sunt încă aplicate pe e-mailuri. Dacă vedeți că semnăturile nu sunt aplicate, vă rugăm să contactați echipa noastră de sprijin, care va fi fericit să ajute.

2. 18 august 2026 la 10:39 UTCmonitoring

   Inginerii noştri au rezolvat problema, iar clienţii nu ar mai trebui să aibă probleme atunci când folosesc Portalul Cloud Exclaimer. Acum monitorizăm pentru a asigura stabilitatea. Dacă continuaţi să vedeţi probleme, vă rugăm să nu ezitaţi să contactaţi echipa noastră de sprijin, care va fi fericit să ajute.

3. 18 august 2026 la 12:23 UTCmonitoring

   Inginerii Exclaimer sunt conştienţi de rapoartele proiectantului de semnătură care nu a încărcat pentru unii clienţi. Au fost luate iniţial măsuri de remediere, iar Signature Designer ar trebui să încarce acum, conform aşteptărilor pentru utilizatori. Investigăm cauza problemei acum

4. 18 august 2026 la 13:21 UTCidentified

   Am identificat o problemă în cadrul portalului unde unele butoane nu răspund la clicuri pentru unii utilizatori. Inginerii lucrează acum pentru a rezolva problema.

5. 18 august 2026 la 14:21 UTCmonitoring

   Inginerii au reușit să rezolve problema și au reluat monitorizarea pentru orice alte probleme.

6. 19 august 2026 la 08:20 UTCresolved

   Inginerii noştri au monitorizat în această seară şi au confirmat că acest lucru este acum rezolvat

Traducere automată din actualizarea oficială a incidentului.

1. 8 august 2026 la 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 la 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 la 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 la 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 la 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 la 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 la 19:14 UTCinvestigating

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

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

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

4. 5 august 2026 la 06:34 UTCresolved

   This incident has been resolved.

1. 31 iulie 2026 la 12:59 UTCinvestigating

   Inginerii Exclaimer investighează în acest moment un potenţial flux de corespondenţă în regiunea SUA. S-au luat măsuri preventive pentru atenuarea problemei și vor fi furnizate mai multe informații, atunci când este posibil.

2. 31 iulie 2026 la 13:26 UTCmonitoring

   Mesajele preventive aplicate au stabilizat efectiv întârzierea potențială. Inginerii continuă să monitorizeze orice semne de alte probleme.

3. 3 august 2026 la 07:21 UTCresolved

   Inginerii noştri au monitorizat în week-end şi fluxul de poştă ca progresând normal.

Traducere automată din actualizarea oficială a incidentului.

1. 25 iulie 2026 la 22:07 UTCinvestigating

   Investigăm în prezent instabilitatea recurentă care afectează infrastructura bazei noastre de date din regiunea SUA Postgres. Acest lucru este cauzat de o problemă de infrastructură Azure care stă la baza (Identificare de cale: SRV7-K0G). Unii clienți americani pot experimenta probleme intermitente cu Active Directory sincronizare și interfața de utilizator admin în timpul acestei ferestre. Lucrăm cu Microsoft Azure pentru a rezolva acest lucru cât mai repede posibil. Vom furniza actualizări la fiecare 30 de minute. Start: 25 iulie 2026, 22:20 BST

2. 25 iulie 2026 la 22:10 UTCinvestigating

   Continuăm să investigăm această problemă.

3. 26 iulie 2026 la 00:09 UTCidentified

   Problema a fost identificată și se pune în aplicare o soluție. Trimiterea prin e-mail și cererea de semnătură nu sunt afectate și continuă să funcționeze în mod normal. Nu s-au pierdut date despre clienţi. În urma incidentului anterior din SUA din 23 iulie, una dintre replicile bazei de date nu şi-a revenit în mod normal după rezolvarea întreruperii, iar din cauza acestui depozit a fost folosită rapid pe serverul bazei de date primare. Recuperarea este în curs de desfăşurare, iar replicarea este lentă, ne aşteptăm ca acest lucru să se întâmple duminică. Impactul menţionat încă se aplică deoarece am întrerupt temporar încercările de sincronizare a datelor (inclusiv SCIM şi HRIS) pentru a finaliza recuperarea. Vom furniza următoarea actualizare în 12 ore.

4. 26 iulie 2026 la 09:15 UTCmonitoring

   Actualizare - 26 iulie 2026, 10:15 BST Recuperarea bazei de date s-a terminat peste noapte înainte de termen. Păstrarea a revenit la nivele normale şi replicarea este complet prinsă. În prezent suntem în proces de re-aprofundare a serviciilor întrerupte. Vom actualiza componentele afectate la Operationala odata ce serviciile au fost restaurate complet. Cererea de livrare prin e-mail și semnătură continuă să funcționeze în mod normal.

5. 26 iulie 2026 la 15:24 UTCresolved

   Actualizare - 26 iulie 2026, 16:25 BST Toate serviciile au fost restaurate complet. Stocarea şi replicarea bazelor de date sunt sănătoase. Sincronizarea datelor (SCIM, HRIS) a fost reluată în mod normal. Nu s-au pierdut date despre clienţi. Ne cerem scuze pentru orice neplăceri cauzate.

Traducere automată din actualizarea oficială a incidentului.

1. 23 iulie 2026 la 15:32 UTCinvestigating

   Ne confruntăm în prezent cu probleme legate de livrarea semnăturilor de e-mail pentru clienţii din regiunea SUA din cauza unei probleme de infrastructură Azure care stă la baza acesteia în vestul SUA. E-mailurile sunt livrate dar semnăturile nu pot fi aplicate în timpul acestei ferestre. Suntem activ de lucru pentru a restabili serviciul complet și va oferi actualizări la fiecare 30 de minute.

2. 23 iulie 2026 la 15:35 UTCinvestigating

   Continuăm să investigăm această problemă.

3. 23 iulie 2026 la 16:28 UTCinvestigating

   Actualizare - 23 iulie 2026, 17:20 BST Continuăm să investigăm o problemă care afectează livrarea semnăturii de e-mail pentru clienţii din regiunea SUA, cauzată de o problemă externă a infrastructurii Azure din vestul SUA. E-mail este încă în curs de livrare. Semnătura nu poate fi aplicată intermitent în timpul acestei ferestre. Am extins infrastructura SUA și lucrăm în mod activ pentru a restabili serviciul complet.

4. 23 iulie 2026 la 17:19 UTCinvestigating

   Actualizare - 23 iulie 2026, 18:15 BST Am restaurat livrarea semnăturii e-mail pentru clienţii din regiunea SUA. E-mailurile sunt acum livrate cu semnături aplicate. Continuăm să monitorizăm situaţia în timp ce Microsoft investighează problema infrastructurii Azure West SUA. Vom oferi o actualizare suplimentară dacă se detectează vreun impact. Ne cerem scuze pentru orice neplăceri cauzate.

5. 23 iulie 2026 la 17:20 UTCmonitoring

   Livrarea semnăturii e-mail a fost restaurată pentru clienţii din regiunea SUA. În timp ce problema de bază a fost cu infrastructura din vestul SUA a lui Azure, am făcut ajustări la sistemele noastre pentru a atenua impactul și a menține serviciul în timpul întreruperii. Continuăm să monitorizăm situaţia în timp ce Microsoft investighează problema infrastructurii Azure West SUA.

6. 23 iulie 2026 la 20:06 UTCmonitoring

   Livrarea semnăturii e-mail a fost restaurată pentru clienţii din regiunea SUA. În timp ce problema de bază a fost cu infrastructura din vestul SUA a lui Azure, am făcut ajustări la sistemele noastre pentru a atenua impactul și a menține serviciul în timpul întreruperii. Continuăm să monitorizăm situaţia. Vă rugăm să contactaţi asistenţa dacă aveţi alte probleme. Ne cerem scuze pentru orice neplăceri cauzate.

7. 24 iulie 2026 la 08:45 UTCresolved

   Actualizare - 24 iulie 2026, 09:30 BST Toate serviciile au fost restaurate pe deplin în regiunea SUA. Livrarea semnăturii prin e-mail funcționează în mod normal în ambele centre de date din SUA, ca urmare a întreruperii infrastructurii Azure West SUA pe 23 iulie 2026. Ne cerem scuze pentru orice întrerupere cauzată.

Traducere automată din actualizarea oficială a incidentului.

1. 10 iulie 2026 la 11:03 UTCinvestigating

   Inginerii Exclaimer investighează o problemă în cazul în care unii clienți pot primi o pagină "a avut loc o eroare neașteptată" atunci când încearcă să navigheze la Signatures, Campaigne, sau Disclamations tab-uri. Dacă vă confruntați cu această problemă, vă rugăm să ridicați un bilet de sprijin folosind link-ul de mai jos. A se vedea nota de subsol 1. Semnăturile continuă să fie aplicate aşa cum se aşteaptă la mesaje atât prin regula fluxului de corespondenţă, cât şi prin suplimentul Exclaimer.

2. 10 iulie 2026 la 14:39 UTCidentified

   Inginerii Exclaimer au identificat cauza problemei și pun în aplicare modificări pentru a aborda cauza. Am verificat, de asemenea, că această problemă a afectat un subset mic de clienți.

3. 10 iulie 2026 la 15:52 UTCresolved

   O schimbare reușită a abordat problema, inclusiv atenuarea pentru a preveni repetarea problemei. Clienții nu ar trebui să mai vadă nici un mesaj de eroare sau să mai întâmpine probleme atunci când accesează filele Semnături, Campanie sau Disclamați. Dacă vă confruntați cu orice probleme cu portalul Exclaimer, vă rugăm să ridicați un bilet de sprijin, și echipa noastră va fi fericit să ajute A se vedea nota de subsol 1

Traducere automată din actualizarea oficială a incidentului.

1. 1 iulie 2026 la 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 iulie 2026 la 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 iulie 2026 la 15:41 UTCresolved

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

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

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

3. 29 iunie 2026 la 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 iunie 2026 la 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 iunie 2026 la 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 iunie 2026 la 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 iunie 2026 la 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 iunie 2026 la 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 iunie 2026 la 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 iulie 2026 la 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 iulie 2026 la 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 iunie 2026 la 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 iunie 2026 la 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 iunie 2026 la 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 iunie 2026 la 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 iunie 2026 la 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 iunie 2026 la 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 la 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 la 09:03 UTCmonitoring

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

3. 28 mai 2026 la 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 la 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 la 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 la 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 la 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 la 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 iunie 2026 la 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 la 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 la 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 la 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 la 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 la 10:32 UTCmonitoring

   We are continuing to monitor for any further issues.

6. 25 mai 2026 la 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 iunie 2026 la 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 la 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 la 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 la 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 la 08:43 UTCresolved

   This incident has been resolved.