64 Exclaimer incidents · 2024年11月 — official updates, affected components, duration and resolution details.
声名狼藉的支助人员目前正在处理一个影响我们支助组发送电子邮件答复的问题。 如果您有不间断的支持票,您可以登录到支持门户,查看任何可能的更新,并回复分配给您的支持工程师. 您可按本指南中概述的步骤访问现有门票并回复指定的支助工程师:https://support.exclaimer.com/hc/en-gb/articles/9389259466141
声名狼藉的工作人员进行了内部变动,监测显示,这一问题现已得到彻底解决。 请通过电子邮件或直接通过我们的门户网站跟进你的案子。 欲了解您的现票情况并回复我们的支援团队,请遵照本指南规定的步骤:https://support.exclaimer.com/hc/en-gb/articles/9389259466141.
自动翻译自官方事件更新。
工程师们意识到一个影响签名设计师的问题,这正在阻止一些客户编辑签名模板. 目前对邮件流动或签名交付没有影响. 我们正在调查,并将在60分钟内提供进一步的最新资料.
声望工程师已经解决了这个问题,客户在使用签名设计师时不应再遇到任何问题. 我们现在正在监测任何其他问题.
工程师证实之前的"服务警报"已经解决. 这项服务现已恢复到完全健康状态,正常运转。 谢谢你的耐心.
自动翻译自官方事件更新。
声优工程师们意识到一个瞬间的问题,这可能导致某些页面,如"品牌"(Branding),"Campaigns"(Campaigns)和"免责声明"(Despectors)在"声优门户"(Exlector Portal)内无法为客户加载. 目前正在进行补救工作,以恢复进入门户网站这些部分的机会。 签署工作仍在电子邮件上。 如果你看到没有签名,请联系我们的支援小组,后者将乐于提供帮助.
我们的工程师已经解决了这个问题,客户在使用ExClaimer Cloud门户网站时不应再遇到任何问题. 我们现在正在监测,以确保稳定。 如果你继续看到问题, 请不要犹豫 联系我们的支援团队, 谁会很乐意帮助.
声名狼藉的工程师们知道有报道称签名设计师未能为部分客户加载. 已采取初步补救行动,签名设计师现在应该按预期为用户加载。 我们正在调查问题的原因
我们已经在门户内找出一个问题,即有些按钮对一些用户的点击没有响应. 工程师们正在努力解决这个问题.
工程师们已经能够解决这个问题,并恢复了对任何进一步问题的监测.
我们的工程师已经监视了整个晚上 并证实这件事已经解决了
自动翻译自官方事件更新。
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
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.
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.
Engineers have been able to identify and confirm a fix and are implementing it in all impacted regions now.
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.
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.
We are currently seeing an increase in imprint failures for messages processed in the US1 datacenter.
We have identified an issue with the auto scaling on key services. These have been manually scaled and we are seeing recovery.
Imprinting has now recovered and is operationsl once more. Engineers will continue to monitor the situation.
This incident has been resolved.
声名狼藉的工程师们正在调查美国区域内潜在的邮件流送问题。 已采取预防行动来缓解这一问题,并将尽可能提供更多的信息.
应用的预防信息有效地稳定了可能的拖延。 工程师正在继续监测任何进一步问题的迹象.
我们的工程师们在周末监控了 邮件流 进展正常.
自动翻译自官方事件更新。
我们正在调查影响我们美国地区Postgres数据库基础设施的反复出现的不稳定情况。 这是由一个潜在的Azure基础设施问题(跟踪ID:SRV7-K0G)所引起. 一些美国客户可能在此窗口期间遇到Active Directory同步和管理员用户界面的间歇性问题. 我们正在与微软Azure合作,以尽快解决这个问题。 我们将每30分钟提供一次最新情况。 开始时间:2026年7月25日,22:20 BST
我们正在继续调查这一问题.
这一问题已经确定,一个解决办法正在实施之中。 电子邮件发送和签名申请不受影响,并将继续正常运作。 没有丢失客户数据 。 此前7月23日在美国发生的事件后,其中一个数据库复制品在故障解决后未能正常恢复,并由于这种存储被迅速用在了主数据库服务器上. 恢复工作正在进行之中,复制工作正在缓慢地赶上,我们预计这将在星期天进行。 所指出的影响仍然适用,因为我们暂时暂停了数据同步尝试(包括SCIM和HRIS),以便完成回收。 我们将在12小时内提供下一次最新情况.
更新 - 2026年7月26日,10:15 BST 数据库恢复工作提前了一夜完成。 储存已恢复正常水平,复制工作已完全赶上。 我们目前正在重新启用暂停服务。 一旦全面恢复服务,我们将向业务部门更新受影响的部分。 电子邮件发送和签名申请继续正常运作.
更新 - 2026年7月26日,16:25 BST 所有服务已完全恢复。 数据库的存储和复制是健康的。 数据同步(SCIM, HRIS)已正常恢复. 没有丢失客户数据。 我们为造成的不便道歉.
自动翻译自官方事件更新。
由于美国西部Azure的基础设施问题, 正在发送电子邮件,但在此窗口中可能不会应用签名。 我们正在积极努力恢复全面服务,并将每30分钟提供最新情况.
我们正在继续调查这一问题.
更新 - 2026年7月23日,17:20 BST 我们继续调查一个影响美国地区客户的电子邮件签名发送的问题, 电子邮件仍在发送中。 在此窗口中不得间歇地应用签名。 我们扩大了我们的美国基础设施,并正在积极努力恢复全面服务.
更新 - 2026年7月23日,18:15 BST 我们已经恢复向美国地区的客户发送电子邮件签名。 目前正在发送带有签名的电子邮件。 在微软调查美国阿苏尔西部基础设施问题时, 如果发现任何影响,我们将提供进一步的最新资料。 我们为造成的不便道歉.
美国地区客户的电子邮件签名发送已经恢复。 虽然根本问题在于阿祖尔的西美国基础设施,但我们调整了我们的系统,以减轻影响,并在停用期间维持服务。 在微软调查美国阿苏尔西部基础设施问题时.
美国地区客户的电子邮件签名发送已经恢复。 虽然根本问题在于阿祖尔的西美国基础设施,但我们调整了我们的系统,以减轻影响,并在停用期间维持服务。 我们正在继续监测局势。 遇到其他问题请联系支援。 我们为造成的不便道歉.
更新 - 2026年7月24日,09:30 BST 整个美国地区的所有服务都已完全恢复。 2026年7月23日Azure West US基础设施停用后,两个美国数据中心均正常使用电子邮件签名。 我们为造成的任何干扰道歉.
自动翻译自官方事件更新。
有些顾客在试图浏览签名、运动或免责标签时可能会收到“意外出错”页面。 如果您正在经历这个问题,请使用以下链接提出支持票。 https://support.exclaimer.com/hc/en-gb/p/cause-ticket 页面存档备份,存于互联网档案馆. 签字继续通过邮件流规则和ExClaimer加注按预期对信件适用.
声名狼藉的工程师们已经查明了问题的原因,并正在执行改革来解决问题。 我们还核实,这一问题影响到一小部分客户.
成功的变革已经解决了这一问题,包括减缓,防止这一问题再次发生。 客户在访问签名、运动或免责声明标签时不应再看到任何错误信息或遇到任何问题。 如果你遇到任何问题 请举起支持票 我们的团队很乐意帮忙 https://support.exclaimer.com/hc/en-gb/p/cause-ticket 页面存档备份,存于互联网档案馆
自动翻译自官方事件更新。
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
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.
The issue is now resolved and the all mail flow processing is operational
We were alerted to an issue with mail flow in our primary data centers. Our engineers are currently investigating and trying to resolve asap
Our engineers have identified the issue and are mitigating. Customers may still experience delays in mail delivery
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.
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.
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.
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.
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.
Our engineers have escalated the urgency of this with Microsoft and continue to push for updates as soon as possible.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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
Exclaimer Engineers have successfully mitigated the issue and mailflow had returned to normal levels.
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.
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
Our team have identified the issue and are actively working on a resolution. Further updates will follow once a fix has been identified.
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.
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.
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.
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.
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.
We are continuing to investigate the issue to determine the root cause. Our IT will report back shortly
We are still continuing to investigate the issue to determine the root cause. Our IT will report back soon
Our engineers have found the issue and reverted a change. Authentication tokens are now being received and we are continuing to monitor.
We are continuing to monitor for any further issues.
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.
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.
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
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.
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.
This incident has been resolved.