Last checked: 5 minutes ago
Get notified about any outages, downtime or incidents for SYNAQ and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for SYNAQ.
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 |
---|---|
SYNAQ Archive | Active |
SYNAQ Branding | Active |
SYNAQ Cloud Mail | Active |
SYNAQ Continuity | Active |
SYNAQ Q Portal | Active |
SYNAQ Securemail | Active |
View the latest incidents for SYNAQ and check for official updates:
Description: Summary and Impact to Customers On Wednesday 28th April 2021 from 13:38 to 14:56, SYNAQ Cloud Mail experienced a mail authentication incident. The resultant impact of the event was that users were unable to authenticate could not access the platform. Root Cause and Solution The root cause of this event was due to a failed route on our primary “High Availability” server and the Secondary server not taking over. With the route being down, the authentication requests were unable to reach the Cloud Mail proxy servers and authentication was unable to complete. To resolve this issue, the primary server had to be shutdown to bring the routes back up again. Once the routes had been restored to the Cloud Mail proxy server, authentication requests were once again being processed and users could access their mail. Upon further investigation, it was determined that the Secondary server had a configuration error which prevented it from being able to detect there was a problem with the primary server, which would have allowed it to take over. This configuration has been corrected and failover has since been tested and this moved across seamlessly. Remediation Actions • A full audit of all HA servers to ensure all their rules are identical. • Scheduled failover testing of HA servers to be implemented.
Status: Postmortem
Impact: Major | Started At: April 28, 2021, 11:38 a.m.
Description: Summary and Impact to Customers On Wednesday 28th April 2021 from 13:38 to 14:56, SYNAQ Cloud Mail experienced a mail authentication incident. The resultant impact of the event was that users were unable to authenticate could not access the platform. Root Cause and Solution The root cause of this event was due to a failed route on our primary “High Availability” server and the Secondary server not taking over. With the route being down, the authentication requests were unable to reach the Cloud Mail proxy servers and authentication was unable to complete. To resolve this issue, the primary server had to be shutdown to bring the routes back up again. Once the routes had been restored to the Cloud Mail proxy server, authentication requests were once again being processed and users could access their mail. Upon further investigation, it was determined that the Secondary server had a configuration error which prevented it from being able to detect there was a problem with the primary server, which would have allowed it to take over. This configuration has been corrected and failover has since been tested and this moved across seamlessly. Remediation Actions • A full audit of all HA servers to ensure all their rules are identical. • Scheduled failover testing of HA servers to be implemented.
Status: Postmortem
Impact: Major | Started At: April 28, 2021, 11:38 a.m.
Description: Dear Clients, The SYNAQ Securemail incident has been resolved and the service has returned to optimal functionality.
Status: Resolved
Impact: Critical | Started At: March 26, 2021, 10:15 a.m.
Description: Dear Clients, The SYNAQ Securemail incident has been resolved and the service has returned to optimal functionality.
Status: Resolved
Impact: Critical | Started At: March 26, 2021, 10:15 a.m.
Description: Summary and Impact to Customers On Friday 12th March 2021 from 07:52 to 14:45, SYNAQ Cloud Mail experienced a mail authentication incident. The resultant impact of the event was that users using ActiveSync to authenticate could not access the platform. Root Cause and Solution The root cause of this event was due to an error with the license for the ‘Next Generation’ mobile module, deployed at the beginning of February. The license failed to validate against the upstream licensing server and went into an automatic grace period. This grace period only lasts for 20 days and once the 20-day period had expired, the mobile module was no longer responding to authentication requests from ActiveSync. This was tested in staging and pre-production and passed tests successfully as this was not left to run past the 20-day grace period. In order to resolve this issue, a license that had been validated against the license server was deployed. Once deployed, authentication requests via ActiveSync resumed. Remediation Actions • A permanent fix to correct these validation issues will be released in the next patch which will be rolled out to our servers following our extensive testing process. • New monitoring alerts are being reviewed to be able to detect if these licenses move into the grace period again.
Status: Postmortem
Impact: Major | Started At: March 12, 2021, 5:52 a.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.