Executive summary VM Hypervisor showed signs of going bad on Friday night.  Mitigating steps were taken.  Server failed on Sunday night too late for anyone to be able to work on it until Monday.  Server was restored at 11:30AM.  Hypervisor is now stable, however critical services hosted on that hypervisor will be moved to more …

We are working to bring it back up. We’re hopeful it will be back online within the hour, I will send updates if that changes.

CIS successfully revived our router, and most MCS hosts and services are back online. We’re still looking over the monitoring to identify what are actual issues vs. transient errors that will self-correct (some servers may not be properly syncing their time via NTP, for example), and will be addressing them as we find them. If …

The unexpected power issue that caused this outage has caused a failure in a critical component of the MCS router. We’re currently working with CIS on getting this back online, either with a replacement supervisor card, or an ad-hoc temporary solution until a replacement can be installed. We’re currently estimating another couple of hours of …

Late last week, we instituted a change in the network configuration for desktop networks. This particular change came with an unintended side effect that is resulting in some people’s computers not getting an address from the network when plugged in. In the past, if a host was not registered with us and was plugged into …