Is there an SYNAQ outage?
SYNAQ status: Systems Active
Last checked: 8 minutes ago
Get notified about any outages, downtime or incidents for SYNAQ and 1800+ other cloud vendors. Monitor 10 companies, for free.
Last checked: 8 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 the 3rd April from 12:49pm to 16:58, SYNAQ Cloud Mail experienced a service incident. The resultant impact of the event was the intermittent mailbox access and mail sending and receiving delays. Root Cause and Solution The root cause of this event was due to a lack of communication between a cluster VMHost and its backing storage. This caused the inability for users to authenticate against stores and archive servers that were operating on the affected host. As a result, Clients experienced intermittent mailbox access and mail delivery issues. In order to resolve this incident, the affected VMHost was rebooted to re-establish communication with the backing storage, so that mailbox access and delivery could function as per normal. Remediation Actions • Improve our monitoring process to include this unique scenario, to prevent it from recurring in the future.
Status: Postmortem
Impact: Major | Started At: April 3, 2019, 10:49 a.m.
Description: Summary and Impact to Customers On Wednesday 13th March 2019 from 07:40am – 20:04pm SYNAQ Securemail experienced a major incident. The resultant impact of the event was Clients were initially unable to send and receive mail and thereafter experienced mail delays. Root Cause and Solution The root cause of this event was due to exhausted DNS connections on our DNS servers as a result of two authoritive name servers that were not responding to DNS queries for the domains that they were the authoritive for. DNS is important to the operation of the Securemail service because it is used to perform multiple security checks, resolve MX records and to allow connectivity to our platform via the relevant host names. This caused connections from our DNS server to the two authoritive name servers to remain open as the affected servers did not respond to our queries. This caused the SYNAQ DNS servers to reach their connection limit and as such, prevented all further DNS queries from taking place. As a result, no mail could be sent or received. In order to solve this issue, and whilst we were waiting for the name server provider to resolve their incident, we implemented a temporary work-around where we redirected our DNS queries away from the root servers to other DNS servers that still had cached results and responded with the required domain information. This allowed mail to start flowing again and to work through the existing backlog of mails. At approximately 15:40pm, the name server provider resolved their incident and we rerouted our DNS queries back to the root servers. This allowed our mail delivery to resume at a normal rate and the backlog of mails was completed at 20:04pm. Remediation Actions We are investigating new methods to mitigate our connections limits from being reached should a third party DNS name server provider experience any incidents.
Status: Postmortem
Impact: Critical | Started At: March 13, 2019, 6:53 a.m.
Description: Summary and Impact to Customers On Wednesday 13th March 2019 from 07:40am – 20:04pm SYNAQ Securemail experienced a major incident. The resultant impact of the event was Clients were initially unable to send and receive mail and thereafter experienced mail delays. Root Cause and Solution The root cause of this event was due to exhausted DNS connections on our DNS servers as a result of two authoritive name servers that were not responding to DNS queries for the domains that they were the authoritive for. DNS is important to the operation of the Securemail service because it is used to perform multiple security checks, resolve MX records and to allow connectivity to our platform via the relevant host names. This caused connections from our DNS server to the two authoritive name servers to remain open as the affected servers did not respond to our queries. This caused the SYNAQ DNS servers to reach their connection limit and as such, prevented all further DNS queries from taking place. As a result, no mail could be sent or received. In order to solve this issue, and whilst we were waiting for the name server provider to resolve their incident, we implemented a temporary work-around where we redirected our DNS queries away from the root servers to other DNS servers that still had cached results and responded with the required domain information. This allowed mail to start flowing again and to work through the existing backlog of mails. At approximately 15:40pm, the name server provider resolved their incident and we rerouted our DNS queries back to the root servers. This allowed our mail delivery to resume at a normal rate and the backlog of mails was completed at 20:04pm. Remediation Actions We are investigating new methods to mitigate our connections limits from being reached should a third party DNS name server provider experience any incidents.
Status: Postmortem
Impact: Critical | Started At: March 13, 2019, 6:53 a.m.
Description: All services fully restored
Status: Resolved
Impact: Minor | Started At: Dec. 12, 2018, 5:02 p.m.
Description: All services fully restored
Status: Resolved
Impact: Minor | Started At: Dec. 12, 2018, 5:02 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.
