Exclaimer Outage History

Started Apr 17, 2026, 07:00 AM UTC· resolved Apr 17, 2026, 07:00 AM UTC

1. resolved Apr 20, 2026, 06:46 PM UTC

   An unexpected bad release of the Exclaimer Cloud Portal was able to be deployed to regions, preventing the Portal from being accessible to allow users to configure signatures or complete the Exclaimer onboarding. Automated rollbacks detected the error and reverted to the previous healthy version. An internal investigation was able to identify the cause of the bad release being able to be deployed to our systems, and further checks have been implemented to prevent future occurrences.

Read the full incident report →

Started Apr 15, 2026, 11:03 AM UTC· resolved Apr 30, 2026, 11:11 AM UTC

1. investigating Apr 15, 2026, 11:03 AM UTC

   Exclaimer engineers are currently investigating a problem where signatures are being applied to messages even though a signature is already present on the most recent message. The issue does not appear to be impacting all mail at this time. We will provide more information as it becomes available.

2. identified Apr 16, 2026, 03:23 PM UTC

   Exclaimer Engineers have been able to identify changes being made by Outlook when the email signature is applied, and then the email is saved as a draft. Resulting in a secondary signature being applied server-side if this is also enabled. The issue is being raised with Microsoft directly to understand this behavioural change further.

3. identified Apr 17, 2026, 09:42 AM UTC

   Exclaimer Engineers have made a change to signature generation to help prevent the issue from occurring for client-side signatures. We are continuing to raise the issue with Microsoft to gain a more in-depth understanding of the problem.

4. resolved Apr 30, 2026, 11:11 AM UTC

   Exclaimer Engineers have been able to release a change to the Add-in at the start of this week, alongside a fix that was released by Microsoft, and the issue no longer looks to be occurring frequently within messages. If you are still seeing duplicate email signatures being applied. Please reach out to our support team, who will be happy to help.

Read the full incident report →

Started Apr 04, 2026, 10:00 AM UTC· resolved Apr 16, 2026, 06:57 PM UTC

1. investigating Apr 04, 2026, 10:00 AM UTC

   Exclaimer Engineers are investigating a possible issue for customers in the MEA region who are unable to route emails to Exclaimer for Server-Side signatures, with messages being deferred and delayed. Emails are continuing to be processed. If any possible sending delay needs to be avoided, you can disable the Mail flow rules for Exclaimer Cloud within the Exchange Admin Center. This does not look to impact all customers within the region. More information will be provided when available.

2. identified Apr 04, 2026, 02:44 PM UTC

   Exclaimer Engineers are continuing to investigate issues affecting customers in the MEA region who are facing delays or deferrals when sending emails. Our findings indicate that Exclaimer itself is functioning properly in the region, and successful connections are being established for all incoming messages. Occasionally, we notice that our monitoring systems initiate a connection but then disconnect before completing the message transfer. Since these cases don't reach our servers, it suggests that the problem is likely outside of Exclaimer's framework, occurring when the sending email server attempts to route messages. We have contacted Microsoft to further investigate the situation. For customers experiencing delays in mail flow, an immediate workaround is to disable the Exchange Mail Flow rules. Despite the delays, we confirm that all messages are eventually being processed by Exclaimer as expected.

3. identified Apr 06, 2026, 01:44 AM UTC

   We are seeing continued improvements in mail flow performance. We are currently working with Microsoft to confirm whether their fix has been fully deployed. Error rates have decreased, and we are no longer observing issues in the MEA region. However, some customers in the US region are still experiencing impact. At this time, the mail flow rule disablement workaround can be safely reverted for customers who previously applied it to avoid delays. For customers who are still experiencing the issue, or encounter any new occurrences, we recommend disabling the Exclaimer transport rule (mail flow rule) as a temporary workaround. We will continue monitoring the situation closely and will provide further updates once we receive confirmation from Microsoft.

4. identified Apr 06, 2026, 01:45 AM UTC

   We are continuing to work on a fix for this issue.

5. identified Apr 07, 2026, 01:18 AM UTC

   Error rates have continued to decrease, and we’re now seeing minimal errors across both the MEA and US regions. We’re still actively working with Microsoft to better understand the root cause, overall impact, and confirmation of the fix. If the issue continues for any affected users, disabling the Exclaimer transport (mail flow) rule remains a valid temporary workaround.

6. monitoring Apr 08, 2026, 10:43 AM UTC

   Exclaimer Engineers are continuing to monitor the situation at this time. The rate of messages being deferred due to the connecting server failing to provide the email has dropped substantially as well since Monday. We are continuing to reach out to Microsoft to discuss the issue and obtain a complete understanding of it, and to confirm that the issue has been addressed.

7. resolved Apr 16, 2026, 06:57 PM UTC

   After extended monitoring, we are no longer seeing any issues impacting customers within these regions that would cause the issue initially reported at this time. We continue to reach out and discuss the incident with Microsoft, and will provide a Postmortem review once we have received completed feedback from them regarding this issue.

8. postmortem Apr 20, 2026, 06:14 PM UTC

   Issue: Possible Routing issues within MEA & US region for Microsoft Customers Incident Length: ~70 hour\(s\) Incident Date: 4/4/2026, UTC 9:37– 8:07 7/4/2026 Incident Status: Investigating **Summary** Mail flow for customers in the Middle East and Africa \(MEA\) region would encounter issues routing messages to Exclaimer, with Exchange servers reporting that the exclaimer smtp hosts rejected or did not respond to the request. We are still awaiting a full Post Incident Review from Microsoft and will update this Postmortem with additional information once it is available. **Root Cause** The issue is believed to be a configuration issue within Exchange in the region, preventing the connection to Exclaimer servers within the UAE or US region. All impacted messages appear to have been deferred, resulting in them being delivered at a later time, further confirming the expected mail flow between Exclaimer and Exchange Online. **Mitigation** Some Exchange servers which were consistently noted to be failing to provide the email to Exclaimer relays when requested, were passed over to Microsoft for review. Shortly afterwards these instances stopped appearing to submit traffic to Exclaimer, suggesting they have been had been taken out of service. Exclaimer Engineers have internally made changes to how message logs are stored between our servers, helping to improve and identify potential issues and errors within the STARTTLS process

Read the full incident report →

Started Apr 01, 2026, 10:31 AM UTC· resolved Apr 04, 2026, 10:03 AM UTC

1. investigating Apr 01, 2026, 10:31 AM UTC

   We are currently investigating an issue with some users not being able to access the Exclaimer Portal when choosing Launch, where the portal gets caught on a loading page. The issue does not appear to affect all users and all subscriptions at this time

2. identified Apr 01, 2026, 12:06 PM UTC

   Exclaimer Engineers have identified the cause of the issue and are currently working on a solution. Further updates will be provided once this is released.

3. resolved Apr 04, 2026, 10:03 AM UTC

   Exclaimer Engineers have identified the cause of the issue and released a fix, and the issue is no longer impacting users who previously reported it. Extended monitoring has not indicated any other outstanding issues at this time. If you are continuing to have issues accessing your Exclaimer subscription, please reach out to our support team, who will be happy to help.

Read the full incident report →

Started Apr 01, 2026, 05:26 AM UTC· resolved Apr 01, 2026, 02:17 PM UTC

1. investigating Apr 01, 2026, 05:26 AM UTC

   We are investigating issues with emails failing to route through Exclaimer for server side signature imprints. For now, we recommend disabling server side transport rules in Exchange Online (Identify messages to send to Exclaimer cloud) to ensure mail flow. We will continue to update as more information becomes available.

2. monitoring Apr 01, 2026, 07:25 AM UTC

   We have identified that the issue was caused by an internal mail‑processing component that had recently been enabled. Under certain conditions, this component could interfere with message handling and lead to the errors observed. The feature has now been disabled, and the issue has stopped. An unrelated third party was incorrectly attributed to the issue earlier. We have identified other internal changes that coincided with the timing of the incident, and these have been rolled back as a precaution. We are continuing to investigate to ensure there is no further impact. The service has remained stable since our last update, and we are continuing to monitor closely.

3. resolved Apr 01, 2026, 02:17 PM UTC

   After continued monitoring, we have confirmed that emails are now being processed as expected through Exclaimer. If you disabled the Exclaimer Mail Flow rule, please look to enable this again when ready. If you are continuing ot see issues, please reach out to our support team, who will be happy to help.

4. postmortem Apr 09, 2026, 07:42 PM UTC

   Issue: Messages failed to be routed through Exclaimer correctly within AU region Incident Length: 3 hour\(s\) and 6 minutes Incident Date: 01/04/2026 UTC 05:53– 8:59 Incident Status: Resolved **Summary** Australian Region customers with the Sent Items feature enabled would encounter an issue routing messages, resulting in message delivery issues and non-delivery reports \(NDRs\) being received. **Root Cause** The issue was caused by a recently enabled mail processing feature globally, which introduced unexpected behavior within the SMTP proxy servers. This affected how messages were handled when routing back to Exchange Online. **Mitigation** Initial resolution was implemented by reverting the mail processing feature update globally. Further improvements to error handling have since been implemented to identify the cause of similar issues faster in the future. **Incident Timeline** 01/04 5:53 – Incident is declared after customer reports of mail flow issues are received to the Support Team 5:57 – Initial investigation indicates the issue appears to be isolated to AU region customers. 6:03 – Exclaimer Engineers confirm the resulting error code correlates with error logs within internal logging 6:32 – Initial hypothesis suggests degradation with an external SMTP provider is the cause of the issue. Whilst they announce a fix, the backlog of impacted messages does not change. 6:41 – Error rates begin to decrease and incident is believe to be resolved. 7:08 – Exclaimer Engineers monitoring note that a drop in 5xx errors is visible, along with a drop in active message counts. Suggesting correlation between the errors being seen and the number of messages submitted to Exclaimer. 7:32 – Engineers begin investigating internal systems further for any lingering issues. 7:37 – The error is confirmed to be related to routing the email back to Exchange Online, disproving the earlier hypothesis. Recent changes to mail routing are reverted to monitor for impact or changes. The error rate is noted to instantly drop at this time. 8:03 – The error rate begins to approach zero, investigation into the cause within recent releases begins. As part of this incident, areas of improvement within internal and external communication have been identified. Action has been taken to improve this and prevent future instances of misattribution and miscommunication from occurring.

Read the full incident report →

Started Mar 20, 2026, 02:59 PM UTC· resolved Mar 23, 2026, 11:18 AM UTC

1. investigating Mar 20, 2026, 02:59 PM UTC

   We are currently investigating an issue where signatures are not being applied to messages at this time. There is no impact on mail flow; emails will continue to be routed through Exclaimer without issue. If you have any ongoing issues or concerns, please reach out to our Support Team, who will be able to assist.

2. investigating Mar 20, 2026, 04:02 PM UTC

   We are continuing to investigate the issue.

3. monitoring Mar 20, 2026, 05:22 PM UTC

   Exclaimer Engineers have been able to identify a possible cause and have performed a change to help address the issue being seen. Signatures now look to be getting applied to all messages as expected, and engineers will continue to monitor.

4. resolved Mar 23, 2026, 11:18 AM UTC

   After extended monitoring over the weekend, we have been able to confirm the issue has been resolved and there have been no further errors or missed signatures for our customers. Customers who are continuing to see issues should contact our support team, who will be happy to help investigate any issues you may be seeing.

Read the full incident report →

Started Mar 17, 2026, 10:59 PM UTC· resolved Mar 18, 2026, 08:34 AM UTC

1. investigating Mar 17, 2026, 10:59 PM UTC

   We are currently investigating this issue.

2. monitoring Mar 18, 2026, 08:10 AM UTC

   We have identified what was behind the degraded service in the UK and have put a fix in place to remediate the issue. Mail routing has returned to a stable state and we are currently monitoring the situation

3. resolved Mar 18, 2026, 08:34 AM UTC

   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.

Read the full incident report →

Started Mar 04, 2026, 02:19 PM UTC· resolved Mar 06, 2026, 09:39 AM UTC

1. investigating Mar 04, 2026, 02:19 PM UTC

   Exclaimer Engineers are investigating a possible issue that may impact some customers who are configuring Exclaimer Cloud for Microsoft 365. The issue is not expected to impact a larger number of customers, and re-running the setup should resolve the issue. If you are having issues with the setup, please reach out to our Support Team, who will be able to assist.

2. resolved Mar 06, 2026, 09:39 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 16, 2026, 06:05 PM UTC· resolved Feb 16, 2026, 09:17 PM UTC

1. investigating Feb 16, 2026, 06:05 PM UTC

   Exclaimer Engineers have been made aware that our certification provider is currently undergoing emergency maintenance on their platform. This may affect customers who are setting up a subscription or attempting to purchase one. We will provide further updates once they are available. If you have any issues with Exclaimer at this time, please reach out to our great Support team, who will be able to assist further.

2. identified Feb 16, 2026, 06:45 PM UTC

   Exclaimer Engineers are continuing to monitor the ongoing maintenance with our certification provider and identify impacted customers. The next update will be provided in an hour's time, or once further information becomes available.

3. monitoring Feb 16, 2026, 07:25 PM UTC

   Our certificate provider has confirmed that the maintenance has been completed, and we are seeing that certificates are being created as expected for subscriptions. Exclaimer Engineers will continue to monitor for any further issues at this time.

4. resolved Feb 16, 2026, 09:17 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 04, 2026, 01:52 PM UTC· resolved Feb 05, 2026, 06:26 PM UTC

1. investigating Feb 04, 2026, 01:52 PM UTC

   Exclaimer Engineers are aware that the Portal is not loading as expected for customers again after an earlier issue. This is being looked into as a high priority for our team. This issue does not impact signature rules, and signatures continued to be applied to users as expected during the issue. If you have any questions or concerns, please reach out to our support team, who will be happy to assist.

2. monitoring Feb 04, 2026, 02:07 PM UTC

   A fix has been implemented, and access to our portal has been restored. Our Engineering team is now monitoring the service for any further issues.

3. resolved Feb 05, 2026, 06:26 PM UTC

   After extended monitoring, our engineers have not seen any further issues stopping customers from accessing our Portal. This weekends planned maintenance work will continue as planned as part of this work will help address the stability of the Portal and improve accessibility for customers in the future. If you have any questions or concerns, please don't hesitate to contact our great support team, who will be happy to help.

Read the full incident report →

Started Feb 02, 2026, 11:10 PM UTC· resolved Feb 02, 2026, 11:59 PM UTC

1. identified Feb 02, 2026, 11:10 PM UTC

   Exclaimer engineers have identified a global issue with Azure that is impacting our ability to handle messages, as new compute resource cannot currently be created to handle demand, and as such customers in AU might experience issues with message delivery. You can look to disable the Mail flow rule ‘Identify messages to send to Exclaimer Cloud’ to restore mail flow. We will continue to monitor the performance to ensure that the service fully recovers, and provide any updates received by Microsoft. They currently anticipate the fix for this will be in place by 00:00 UTC. If you are experiencing any other issues with Exclaimer at this time, please contact our support team right away.

2. monitoring Feb 02, 2026, 11:33 PM UTC

   Scaling capability appears to have been restored by Microsoft, we're now monitoring our service to ensure it recovers to full capacity.

3. resolved Feb 02, 2026, 11:59 PM UTC

   Azure service has been restored, and services have scaled up as required, we are no longer seeing any issues within our service as a consequence. If you are continuing to experience issues within Exclaimer at this time, please don't hesitate to reach out to our support team, who will be happy to help!

Read the full incident report →

Started Feb 02, 2026, 02:18 PM UTC· resolved Feb 03, 2026, 12:06 PM UTC

1. investigating Feb 02, 2026, 02:18 PM UTC

   Exclaimer Engineers are aware of a relay IP address within the UK having been added to the Sender Score Return Path Blocklist. The IP is no longer reporting as being on this list. We have reached out to obtain more information. Client-side signatures are unaffected by this issue. If you are experiencing issues with mail flow at this time, we advise you to disable the Exclaimer Mail flow rule within the Exchange Admin Center and to contact our support team who will be more than happy to help.

2. monitoring Feb 02, 2026, 03:11 PM UTC

   Monitoring has indicated there has been no impact from the listing, and the IP has not been added back onto the list at this time. Our Engineers will continue to monitor for any further reports.

3. resolved Feb 03, 2026, 12:06 PM UTC

   No issues have occurred since our last update, and we will now mark this incident as resolved. If you require any assistance, please contact our support team, who will be more than happy to help.

Read the full incident report →

Started Jan 27, 2026, 03:41 PM UTC· resolved Jan 28, 2026, 04:23 PM UTC

1. investigating Jan 27, 2026, 03:41 PM UTC

   Exclaimer Engineers are investigating an issue impacting the reporting of signatures applied through the Exclaimer Add-in or Signature Sync system. Client-side Signatures will continue to be applied as expected to messages at this time

2. resolved Jan 28, 2026, 04:23 PM UTC

   Exclaimer Engineers have successfully resolved the issue and confirmed that there was no impact preventing signatures from being added. If you are experiencing any issues with signatures not appearing when expected, please reach out to our support team, who will be happy to assist.

Read the full incident report →

Started Jan 23, 2026, 02:39 AM UTC· resolved Jan 26, 2026, 02:33 PM UTC

1. investigating Jan 23, 2026, 02:39 AM UTC

   We are currently investigating an issue affecting email delivery within our Exclaimer services. Email routed through Exchange Online may be impacted due to an ongoing Microsoft incident (MO1221364).

2. monitoring Jan 23, 2026, 06:32 AM UTC

   We have confirmed that Microsoft has deployed a fix to address the issue and confirmed resolution for Incident (MO1221364). We are continuing to monitor the service for stability.

3. monitoring Jan 23, 2026, 06:38 AM UTC

   We are continuing to monitor for any further issues.

4. resolved Jan 26, 2026, 02:33 PM UTC

   No further issues with mail flow have been identified over the weekend that were caused by this incident. If you are continuing to experience issues with your Exclaimer Subscription, please don't hesitate to reach out, and our team will be more than happy to assist.

Read the full incident report →

Started Jan 09, 2026, 02:51 PM UTC· resolved Jan 19, 2026, 08:56 PM UTC

1. investigating Jan 09, 2026, 02:51 PM UTC

   Exclaimer Engineers are aware of an ongoing issue where one of our Server IPs looks to have been added to the Spamhaus eXploits Blocklist on multiple occasions. Spamhaus is advising that the IP has already been removed from the List. Our engineering team is currently investigating the issue for more information.

2. monitoring Jan 09, 2026, 04:32 PM UTC

   After monitoring mail flow through Exclaimer, we have confirmed there's been no further messages reported as blocked due to the Spamhaus Blocklist since 14:53GMT. Exclaimer Engineers have reached out to Spamhaus to discuss the issue at this time and to obtain more information on the resulting action that added this IP to the blocklist.

3. resolved Jan 19, 2026, 08:56 PM UTC

   This incident has been resolved, and a Postmortem will be provided shortly.

4. postmortem Jan 19, 2026, 08:57 PM UTC

   Issue: Some messages are marked Undeliverable 'blocked using Spamhaus' Incident Length: 1 hour and 27 minutes Incident Date: 9/01/2026, UTC 13:26– 14:53 UTC 9/01/2026 Incident Status: Resolved **Summary** US customers using Exclaimer Cloud to apply a signature once the email was sent would see some messages get rejected when routed back from Exclaimer, with the reason stated as '_Client host blocked using Spamhaus_'. The rejection was caused by a false positive against the IP address by Spamhaus’ servers, which was cleared after a short period of time. Some customers experienced continued mail flow issues due to replication delays in Exchange Online, which would result in some relays continuing to believe the IP address is on this list. **Root Cause** Discussions with Spamhaus’ technical team were able to identify that messages routed through the Exclaimer relay were hitting invalid email addresses or recipient addresses where the bounce management had been incorrectly configured. They have been able to confirm that there is no issue within this US relay, which would indicate an issue within Exclaimer directly. **Mitigation** During the Incident, Mail Flow was directed away from the impacted relay within the US region. Messages that have already been queued to be processed by the impacted relay would continue attempting to use this relay until the message was resubmitted for a retry. Once the engineers had confirmed that the IP addresses were no longer flagged by Spamhaus and had not been returned to the list, the relay was brought back into service. Additionally, with an understanding of Exclaimer, Spamhaus has agreed to a long-term whitelisting of our system within their filtering, which will prevent this from occurring again for our customers globally. **Incident Timeline** 13:26 – The Exclaimer IP for the US relay was added to the Spamhaus eXploits Blocklist \(XBL\) 14:20 – The Exclaimer IP for the US relay is cleared from the Spamhaus XBL 14:28 – Exclaimer Support team raises internally that customers are reporting that messages are being blocked by this list. 14:33 - Engineering teams within Exclaimer confirm that the IP address is not showing as listed, and the responses look to be generated by Microsoft relays within Exchange Online. 14:34- Internal Investigation begins to investigate internally for the cause of the relay being added to the list. 14:45 – Exclaimer Engineers set the impacted relay to be excluded from traffic management, preventing messages from being routed to the impacted IP range. 14:53 – Exclaimer Engineers confirm that the delisting is picked up by Microsoft servers, and rejection messages reasons that specify Spamhaus’ stop. 15:01 – With mail flow confirmed to flow without impact. Exclaimer reaches out to Microsoft and Spamhaus’ teams to identify the cause of the IP address being flagged. 17:32 – Engineers note that the IP is listed on the Spamlist once more for a few minutes before being removed automatically. 12/01, 09:00 – Microsoft advised that contact needs to be made with Spamhaus to determine the cause of the block. 09:05 – Exclaimer Engineers confirm there have been no further reports of the IP address being added onto the Spamhaus xBl, and enable the impacted relay to process messages once more. 13/01, 16:28 – A response is received from Spamhaus regarding this issue, which confirms the suspected cause of the incident and confirms that the Exclaimer domain has been added to their trusted domain listing. 19/01, 15:02 Confirmation is received that all relays globally for Exclaimer are covered within the trusted listing by Spamhaus, confirming the block will not occur again.

Read the full incident report →

Started Dec 18, 2025, 10:27 AM UTC· resolved Feb 20, 2026, 03:56 PM UTC

1. identified Dec 18, 2025, 10:27 AM UTC

   Exclaimer is aware of an error that has resulted in duplicate payments being taken from some customers this month. We are in the process of refunding all duplicate payments; these should be returned within seven(7) business days. We apologise for any inconvenience that may have occurred. More information will be provided directly to impacted customers.

2. identified Dec 19, 2025, 09:26 AM UTC

   We have now contacted the impacted customers directly to confirm that the refund for the duplicate transaction is underway and to provide more information on the issue.

3. resolved Feb 20, 2026, 03:56 PM UTC

   Our finance team has contacted customers who were impacted, and refunds have been arranged directly.

Read the full incident report →

Started Dec 05, 2025, 09:13 AM UTC· resolved Dec 05, 2025, 09:48 AM UTC

1. investigating Dec 05, 2025, 09:13 AM UTC

   We are currently aware of an issue preventing customers from accessing our support portal. The issue appears to be potentially caused by an ongoing issue within Cloudflare that is impacting a large collection of services and sites. Signatures are continuing to be applied to messages, and access to our portal is working as expected. We're continuing to monitor for any changes at this time.

2. resolved Dec 05, 2025, 09:48 AM UTC

   After a monitoring period to confirm there are no returning issues. We can confirm that Cloudflare has implemented a fix to resolve the issue, and we have confirmed that the support portal can be accessed as expected

Read the full incident report →

Started Nov 18, 2025, 11:52 AM UTC· resolved Nov 18, 2025, 06:11 PM UTC

1. identified Nov 18, 2025, 11:52 AM UTC

   Exclaimer engineers are aware of an issue impacting Cloudflare's Global Network. Cloudflare is used by Exclaimer to provide access to our services; this may impact access to our portal in all regions at this time. There is no impact on our signature imprinting through Client-side or Server-side at this time. More information will be provided as we continue to monitor the situation and look to mitigate the impact if possible.

2. identified Nov 18, 2025, 11:53 AM UTC

   We're continuing to monitor Cloudflare's services for any improvements.

3. identified Nov 18, 2025, 12:24 PM UTC

   We're continuing to monitor Cloudflare's services for any improvements that may enable us to take further mitigating measures. We can confirm through our monitoring that signatures are continuing to be applied as expected. If you are having issues with signatures not being applied, please reach out to our support team, who will be happy to help.

4. monitoring Nov 18, 2025, 12:37 PM UTC

   Cloudflare has advised that services are beginning to recover, but that pages may occasionally fail to load and provide an error as they remediate the issue fully. We are seeing that our Cloud portal is now loading as expected in most instances.

5. monitoring Nov 18, 2025, 01:54 PM UTC

   We have noted that accessibility to the site has degraded again, resulting in the portal being inaccessible at this time. We can confirm through our monitoring that signatures are continuing to be applied as expected. If you are having issues with signatures not being applied, please reach out to our support team, who will be happy to help.

6. monitoring Nov 18, 2025, 04:01 PM UTC

   Cloudflare has advised that a fix has been implemented, and they are now working on resolving outstanding issues. We have verified that our site and portal are loading as expected for an extended period of time, and have taken mitigation actions to minimize further impact. Our Engineers will continue to monitor for any signs of the portal or website becoming inaccessible again over the next few hours.

7. resolved Nov 18, 2025, 06:11 PM UTC

   Cloudflare has confirmed that all services are now operating normally. A full investigation is ongoing into the cause and will be available via Cloudflare's site once it has been completed. If you are still experiencing issues with Exclaimer, please reach out to our support team, who will be happy to help.

8. postmortem Nov 19, 2025, 10:15 AM UTC

   Cloudflare has provided a full Post Incident Review on their site, [which can be found here.](https://blog.cloudflare.com/18-november-2025-outage/) They have summarized the issue to be caused by an unexpected bug within some logic for a Bot Management feature that resulted in an abnormally high level of requests that caused the issue to look like a Distributed Denial of Service \(DDoS\) attack against Cloudflare, delaying the resolution time initially. Exclaimer’s Signature application continued to work as expected during the incident, with only web-based access to the Signature management portal impacted at times.

Read the full incident report →

Started Nov 14, 2025, 12:22 PM UTC· resolved Nov 14, 2025, 04:24 PM UTC

1. identified Nov 14, 2025, 12:22 PM UTC

   Exclaimer Engineers are engaged in an issue with some storage components in US that are being impacted by a resource availability shortage in the east us Azure Datacenter. Currently, customers onboarding or running on-demand data crawls will notice a delay in this data being collected. Exclaimer Engineers are engaged with Microsoft to mitigate the capacity issues and return the system to normal. Customer mailflow is not impacted. Next update within 60 minutes or sooner

2. identified Nov 14, 2025, 01:27 PM UTC

   Exclaimer Engineers are continuing to work with Microsoft on resolving the issues with the storage components affecting onboarding and aggregation in the US. Microsoft is prioritising our request to make the adjustments required available to us so that we can restore operations fully. Next update to follow in 60 minutes

3. identified Nov 14, 2025, 02:36 PM UTC

   We are continuing to work with Engineers at Microsoft who have confirmed that mitigative steps required to resolve the issues affecting our storage components in East US which is currently resource constrained has been approved. As soon as this the allocation is complete, Exclaimer Engineers will be able to proceed with the steps required to fully restore User Data Synchronization and Onboarding services. Any customers that have attempted to synchronize their data will catch up once this has been completed as the operation is queued internally within Exclaimer's systems. Next update to follow in 60 minutes

4. identified Nov 14, 2025, 03:37 PM UTC

   Microsoft have completed the mitigative steps that were affecting our storage components in East US and the affected storage is healthy once again. Exclaimer Engineers are now resyncing the data to the affected storage instances. This will take some time as we are partially limited by the capacity contraints ongoing in the East US Azure datacenter. Once complete, the User Data Synchronization and Onboarding services will be re-enabled and any customer aggregations that have been queued during this time will complete. Next update to follow in 90 minutes or sooner.

5. resolved Nov 14, 2025, 04:24 PM UTC

   The data has been fully resynced to the affected instances, the User Data Synchronization and Onboarding services have been re-enabled and all pending customer aggregations that were queued during this time have completed. Exclaimer Engineers will continue to monitor the health of the service and the impact to customers has been resolved.

Read the full incident report →

Started Nov 11, 2025, 12:00 PM UTC· resolved Nov 11, 2025, 12:00 PM UTC

1. resolved Nov 12, 2025, 10:12 AM UTC

   Distributors to the Exclaimer Cloud system may have experienced issues provisioning new subscriptions until 9:30 GMT on the 12th November. This issue impacted a small percentage of global requests that were submitted to the system. Any requests that failed to be processed would need to be resubmitted if they have not been successful.

Read the full incident report →

Started Oct 29, 2025, 04:24 PM UTC· resolved Oct 30, 2025, 12:42 AM UTC

1. investigating Oct 29, 2025, 04:24 PM UTC

   We are currently aware of an issue that is impacting the Exclaimer Add-in from being able to apply a signature to messages. This looks to be caused by a problem within Microsoft Azure at this time, which Microsoft is now investigating. More updates will be provided once we have further information.

2. investigating Oct 29, 2025, 04:42 PM UTC

   Microsoft has confirmed that as of 16:00 GMT, they have been experiencing DNS issues resulting in the service impact. They have taken action to try to mitigate the issue and expect their portal to be loading shortly. Direct updates can be found on Microsoft's public status page for widespread incidents - https://status.cloud.microsoft/ Exclaimer Engineers have reviewed our internal systems and confirmed that our Server-side system is applying signatures as expected at this time.

3. monitoring Oct 29, 2025, 05:10 PM UTC

   Exclaimer Engineers have applied a routing workaround to bypass the Azure Front Door Service, which looks to have been the cause of the outage. Customers should find that the signature is applying as expected from the Add-in shortly once the new routing path has been obtained by the users Outlook client Updates from can continue to be monitored on the following page:- https://status.cloud.microsoft/

4. monitoring Oct 29, 2025, 05:34 PM UTC

   Monitoring of our mitigation looks to have restored close to half of the Add-in performance of being able to apply a signature to messages within Outlook, with indicators that some attempts are failing due to errors from Microsoft services. Microsoft is currently rolling back recent changes to Azure Front Door to restore service at this time. We are continuing to monitor for any further issues. You can find updates on Microsoft's public status page for widespread incidents - https://status.cloud.microsoft/. We have recorded that this page also looks to be impacted, and may occasionally not load.

5. monitoring Oct 29, 2025, 08:20 PM UTC

   Microsoft advised earlier today that the deployment of their 'last known good' configuration to Microsoft Azure is showing signs of successful recovery at this time; however, due to the extent of the issue, they are estimating full recovery to happen by 23:20 UTC on 29 October 2025. Exclaimer Engineers are continuing to monitor at this time for any changes, but are seeing signs of this recovery occurring. Earlier work that was undertaken to reduce the impact remains in place and is still seeing our mail flow processes working without signs of being impacted. If you are having issues sending messages at this time or you have any outstanding questions, please don't hesitate to reach out to our support team.

6. monitoring Oct 29, 2025, 11:55 PM UTC

   Exclaimer Engineers are not observing any ongoing issues with the Exclaimer Add-in right now, indicating the service is working as expected for both client-side and server-side signatures. Microsoft has advised that they are operating at 98% availability, suggesting a very low chance of any issues occurring, but continues to work towards full resolution. Microsoft has updated the completion time to be 00:40 UTC on 30 October 2025, and we will continue to monitor at this time. If you are experiencing issues applying a signature to your emails through our Add-in, or you have any outstanding questions, please don't hesitate to reach out to our support team.

7. resolved Oct 30, 2025, 12:42 AM UTC

   Microsoft has now cleared the incident from its widespread status page, and we are awaiting the Post-Incident Review from them. We're not currently seeing any unusual or unexpected issues with the Exclaimer Add-in. Our engineers will continue to monitor and advise customers if anything is detected. If you are continuing to experience issues applying your signatures to emails through the Add-in, please don't hesitate to reach out to our support team, who will be happy to help!

Read the full incident report →

Started Oct 09, 2025, 10:34 AM UTC· resolved Oct 09, 2025, 04:59 PM UTC

1. identified Oct 09, 2025, 10:34 AM UTC

   Exclaimer engineers are aware of an issue that is impacting the Azure Front Door service which is having an impact on services such as the Exclaimer Add-in, Exclaimer Meeting Branding, or when attempting to download some files from our Website. More information can be seen on Microsoft's Azure Status page: https://azure.status.microsoft/en-gb/status We are actively monitoring the situation and will provide updates as this progresses.

2. identified Oct 09, 2025, 10:58 AM UTC

   Microsoft has advised the following information "We understand that this is due to a dependency on some underlying Kubernetes instances which crashed, we have been restarting these underlying Kubernetes instances and these instances coming back online." Microsoft believes the issue will be resolved in the next 90 minutes for all impacted customers. Our internal monitoring is indicating that the number of warnings has reduced as well. Another update will be provided once we have confirmation that the issue is fully resolved.

3. monitoring Oct 09, 2025, 11:47 AM UTC

   Microsoft has successfully recovered 96% of impacted resources, and services are no longer displaying errors as expected. Exclaimer Engineers are monitoring for any remaining issues that may be caused by this incident.

4. monitoring Oct 09, 2025, 04:48 PM UTC

   Microsoft has addressed the primary issue, and Exclaimer Engineers are continuing to monitor for any further issues.

5. resolved Oct 09, 2025, 04:59 PM UTC

   Microsoft have now declared the issue as resolved. We have reached out to Microsoft to request further details for the post-mortem.

Read the full incident report →

Started Oct 07, 2025, 09:48 AM UTC· resolved Oct 14, 2025, 08:24 AM UTC

1. investigating Oct 07, 2025, 09:48 AM UTC

   Exclaimer's Support team is aware of an issue that caused an Undeliverable message to be received when replying to an existing ticket. The problem should no longer be occurring; however, we are still investigating the cause. You can log in to our support portal directly to access your current tickets and respond to the associated Support Engineer using the steps within this guide: https://support.exclaimer.com/hc/en-gb/articles/9389259466141

2. identified Oct 08, 2025, 02:08 PM UTC

   Exclaimer Support is continuing to work on issues that are causing some messages sent in response to support tickets to return an undeliverable message. The issue has been escalated to our service provider to investigate further, as initial remedial action hasn't addressed the issue. Customers can continue to log in to the support portal directly to update tickets and ensure a response is received by our Support Team. Steps on how to login and access your tickets can be found here: https://support.exclaimer.com/hc/en-gb/articles/9389259466141

3. identified Oct 09, 2025, 08:08 AM UTC

   Exclaimer has implemented a temporary fix to address the issue being seen, which will allow for future messages to be replied to without messages returning an undeliverable message. Messages sent by the support team earlier may still be impacted and return an undeliverable when replied to. If needed, you can log in to our support portal directly to access your current tickets and respond to the associated Support Engineer using the steps within this guide: https://support.exclaimer.com/hc/en-gb/articles/9389259466141

4. resolved Oct 14, 2025, 08:24 AM UTC

   After extended monitoring, we have verified that the changes made to resolve the issue have been implemented with a positive effect, and our support system provider has confirmed that there have not been any new instances of messages failing to deliver since the end of last week.

Read the full incident report →