Collective2 experienced a service outage starting at 15:45 ET today. It lasted approximately 45 minutes. The immediate cause of the problem was a database file that needed to be repaired. We’re still trying to determine the cause of the file failure. While it’s never happy news to discuss service failure, I do want to reassure our members that we have several layers of file and hardware redundancy which can be used in cases like this.
I apologize for the inconvenience this caused you.
- Matthew
