Is there an SYNAQ outage?
SYNAQ status: Systems Active
Last checked: 53 seconds ago
Get notified about any outages, downtime or incidents for SYNAQ and 1800+ other cloud vendors. Monitor 10 companies, for free.
Last checked: 53 seconds 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: SYNAQ Cloud Mail services have been fully restored.
Status: Resolved
Impact: Minor | Started At: Sept. 10, 2019, 6:48 a.m.
Description: SYNAQ Cloud Mail services have been fully restored.
Status: Resolved
Impact: Minor | Started At: Sept. 10, 2019, 6:48 a.m.
Description: Summary and Impact to Customers On Monday 9 th September 2019 from 10:00am – 18:35 pm and Tuesday 10 th September 2019 from 08:48am – 11:09 am, SYNAQ Cloud Mail experienced a degraded service incident which caused mail delays and interrupted mailbox use for a subset of clients. The resultant impact of the event was that certain users experienced a delay in mails and their mailboxes were very slow to respond. Root Cause and Solution The root cause of this event was due to a failed controller on a backend storage device. As a result of the failure, all data accessing the storage had to failover to a single data path. This failover caused an abnormal level of usage over the single data path, resulting in increased latency times for data reads and writes, which in turn caused delayed mail delivery and interrupted mail access for a subset of users. In order to resolve this issue, the controller was replaced and dual paths were restored. As a result, mail delivery and access performance was restored to the affected users. Remediation Actions SYNAQ engineers are implementing a storage plan to increase the single data path capacity to handle failover load without impacting users.
Status: Postmortem
Impact: Minor | Started At: Sept. 9, 2019, 8:35 a.m.
Description: Summary and Impact to Customers On Thursday 5 th September from 07:48am – 09:52am, SYNAQ Securemail experienced a service incident which affected the delivery of mails for all .za domains. The resultant impact of the event was that Clients were unable to send and receive mail to and from .za domains. Root Cause and Solution The root cause of this event was due to an issue experienced by the ZA root servers where they were no longer allowing secure queries from DNS servers. As a result, when our DNS cache servers were trying to query the affected root servers, it was returning an invalid response, which resulted in the inability to send and receive mails to and from .za domains. In order to resolve this issue, the enforced secure queries capability were disabled to the ZA root servers and we were once again able to resolve all .za domain information. Remediation Actions Custom monitoring checks are going to be built to proactively identify these forms of DNS issues.
Status: Postmortem
Impact: Minor | Started At: Sept. 5, 2019, 5:48 a.m.
Description: Summary and Impact to Customers On Thursday 5 th September from 07:48am – 09:52am, SYNAQ Securemail experienced a service incident which affected the delivery of mails for all .za domains. The resultant impact of the event was that Clients were unable to send and receive mail to and from .za domains. Root Cause and Solution The root cause of this event was due to an issue experienced by the ZA root servers where they were no longer allowing secure queries from DNS servers. As a result, when our DNS cache servers were trying to query the affected root servers, it was returning an invalid response, which resulted in the inability to send and receive mails to and from .za domains. In order to resolve this issue, the enforced secure queries capability were disabled to the ZA root servers and we were once again able to resolve all .za domain information. Remediation Actions Custom monitoring checks are going to be built to proactively identify these forms of DNS issues.
Status: Postmortem
Impact: Minor | Started At: Sept. 5, 2019, 5:48 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.
