An electrical fire in a UPS belonging to our clocation provider resulted in a power outage for our equipment starting about 02:30EDT Sunday, July 5. Power was restored approximately 80 minutes later. However, our firewalls were incorrectly configured to not automatically reboot when power is restored, resulting in a further delay restoring services. All services were restored by approximately 10:30EDT. We have corrected the configuration error. Please accept our apologies for the longer than necessary outage.
This morning, from about 11:00am to 11:35am, our servers (mail, web, dns) were unreachable. This turned out to have been a networking configuration error by our colocation provider, and they quickly corrected the problem. This was a very unusual occurrence – in the past 6 years, there have been at most 2 or 3 problems at the colocation facility, which we consider to be an exemplary track record, and we remain 100% confident in our choice of provider. Thank you for your understanding, and please accept our apologies for the outage and inconvenience.
Mail delivery was delay starting about 6pm Thursday September 4 until about 1:00am Friday. An automatic update for the anti-virus software database caused the virus definitions database to be larger than the version of the clamav software could handle, and mail was queued instead of being delivered. We have updated the clamav software and things shoule be back to normal. We do not believe that this problem will recur, or that any mail was lost during this delay.
Please accept our apologies for the inconvenience and annoyance of the delay, and our thanks for being a SYONEX customer.
Early this morning, the anti-virus software’s automatic update process went crazy and filled up the filesystem that handles mail. This was fixed this morning. We expect to update the anti-virus software in the near future. Please accept my apologies for the inconvenience.
There were problems getting to the SYONEX sites this afternoon (roughly 4pm to 5pm EST) from locations on the rogers.com network, which have now been fixed. The sites were accessible from other networks during this time. Our understanding (at present) is that it was a problem in the Rogers network.