Last checked: 13 seconds ago
Get notified about any outages, downtime or incidents for Exclaimer and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for Exclaimer.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!
Sign Up NowOutlogger tracks the status of these components for Xero:
Component | Status |
---|---|
Outlook Add-In | Active |
Portal | Active |
Exclaimer Cloud: Australia | Active |
Analytics | Active |
Client Side Signatures - Office 365 | Active |
Data Synchronization | Active |
Exclaimer Cloud UI | Active |
Feedback | Active |
Imprinting | Active |
Mail Routing - Exchange | Active |
Mail Routing - Office 365 | Active |
Onboarding | Active |
Sent Items Update | Active |
Exclaimer Cloud: Canada | Active |
Analytics | Active |
Client Side Signatures - Office 365 | Active |
Data Synchronization | Active |
Exclaimer Cloud UI | Active |
Feedback | Active |
Imprinting | Active |
Mail Routing - Exchange | Active |
Mail Routing - Office 365 | Active |
Onboarding | Active |
Sent Items Update | Active |
Exclaimer Cloud: Europe | Active |
Analytics | Active |
Client Side Signatures - G Suite | Active |
Client Side Signatures - Office 365 | Active |
Data Synchronization | Active |
Exclaimer Cloud UI | Active |
Feedback | Active |
Imprinting | Active |
Mail Routing - Exchange | Active |
Mail Routing - G Suite | Active |
Mail Routing - Office 365 | Active |
Onboarding | Active |
Sent Items Update | Active |
Exclaimer Cloud: Germany | Active |
Analytics | Active |
Client Side Signatures - Office 365 | Active |
Data Synchronization | Active |
Exclaimer Cloud UI | Active |
Feedback | Active |
Imprinting | Active |
Mail Routing - Exchange | Active |
Mail Routing - Office 365 | Active |
Onboarding | Active |
Sent Items Update | Active |
Exclaimer Cloud: UAE | Active |
Analytics | Active |
Client Side Signatures - Office 365 | Active |
Data Synchronization | Active |
Exclaimer Cloud UI | Active |
Feedback | Active |
Imprinting | Active |
Mail Routing - Exchange | Active |
Mail Routing - Office 365 | Active |
Onboarding | Active |
Sent Items Update | Active |
Exclaimer Cloud: UK | Active |
Analytics | Active |
Client Side Signatures - Office 365 | Active |
Data Synchronization | Active |
Exclaimer Cloud UI | Active |
Feedback | Active |
Imprinting | Active |
Mail Routing - Exchange | Active |
Mail Routing - Office 365 | Active |
Onboarding | Active |
Sent Items Update | Active |
Exclaimer Cloud: US | Active |
Analytics | Active |
Client Side Signatures - G Suite | Active |
Client Side Signatures - Office 365 | Active |
Data Synchronization | Active |
Exclaimer Cloud UI | Active |
Feedback | Active |
Imprinting | Active |
Mail Routing - Exchange | Active |
Mail Routing - G Suite | Active |
Mail Routing - Office 365 | Active |
Onboarding | Active |
Sent Items Update | Active |
View the latest incidents for Exclaimer and check for official updates:
Description: # Exclaimer Post Incident Report: Issue: Signatures not applying via server-side Incident Length: 7 Hours Incident Date: 17/09/2024, UTC 15:30 – 21:12 Incident Status: Resolved ### **Summary** Customers would find that signature templates, that have been applied through the groups option on the Senders tab would not apply. The signature tester would advise that the user is not a member of the group. This issue impacted signature application for both Client-side and Server-side application. Cached configurations on local clients would ensure that for some customers, signatures would continue to be available based on the last review of the signature rules on the subscription. No mail flow was impacted due to the issue, all messages were successfully routed through Exclaimer’s infrastructure and received by their intended recipient\(s\). ### **Root Cause** Planned Improvement work was carried out across all regions to the Exclaimer service. This improvement aims to remove ambiguity and prevent signature errors for renamed groups that are applied to signature templates. This was arranged to take place on the 17th of this month. An unexpected oversight resulted in the new identifier for groups not being adopted by signature rules automatically. ### **Mitigation** Once identified that the planned work was not having the desired result, the original task was halted, and a planned rollback process was initiated to return all environments to their original configuration at 16:13 UTC. All regions were rolled back to the original configuration at 21:12 UTC. An extended monitoring period confirmed no further reports being received after this time. ### **Incident Timeline** 15:15 – Initial reports of signatures failing to apply started to come through to the support team 15:30 – Alerted to high quantity of cases being raised through support channels. Identified possible issues relating to the planned improvement work. 15:38 – Investigation work begins across Engineering and Support Teams. 15:58 – Confirmed impacted customers across multiple regions. 16:00 – Status page published advising of issues. 16:13 – Remediation action of rolling back agreed. 16:44 – Rollback begins in all regions 16:45 – DE Region is roll back. 17:00 – Cause of issue identified within original work. Rollback continues. 17:44 – UAE Region is rolled back. 17:59 – CA Region is rolled back. 19:31 – EU region is rolled back. 19:54 – AU region is rolled back. 20:16 – US region is rolled back. 21:12 – UK region is rolled back. Incident Status moved to Monitoring. 18/09 09:24 – Incident Status moved to resolved
Status: Postmortem
Impact: Major | Started At: Sept. 17, 2024, 4 p.m.
Description: All services are now back to normal levels, and messages are being imprinted by the server-side feature.
Status: Resolved
Impact: None | Started At: Aug. 14, 2024, 3:59 a.m.
Description: This incident is now confirmed to be fully resolved.
Status: Resolved
Impact: None | Started At: July 30, 2024, 4:14 p.m.
Description: Between Jun 13, 9:16 pm and Jun 13, 10:29 pm and Jun 14, 11:29 pm – Jun 15, 12:09 am BST. A subset of customer mailflow limited to the CA region (approximately 5%), may have received a Non-Delivery Report (NDR) with the following information when their message was routed through one of Exclaimers mail-processing data centers: '550 5.7.1 Service unavailable, Client host [52.233.37.155] blocked using Spamhaus [...]' The IP in question was subsequently de-listed and Exclaimer engineers are engaging with Spamhaus to determine the root cause and understand the specific event that triggered the listing.
Status: Resolved
Impact: Minor | Started At: June 13, 2024, 8 p.m.
Description: Between Jun 13, 9:16 pm and Jun 13, 10:29 pm and Jun 14, 11:29 pm – Jun 15, 12:09 am BST. A subset of customer mailflow limited to the CA region (approximately 5%), may have received a Non-Delivery Report (NDR) with the following information when their message was routed through one of Exclaimers mail-processing data centers: '550 5.7.1 Service unavailable, Client host [52.233.37.155] blocked using Spamhaus [...]' The IP in question was subsequently de-listed and Exclaimer engineers are engaging with Spamhaus to determine the root cause and understand the specific event that triggered the listing.
Status: Resolved
Impact: Minor | Started At: June 13, 2024, 8 p.m.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage or down time. Join for free - no credit card required.