At 5:30PM EST the DTR primary chat server at the data center became non-responsive due to a scheduled 30 second networking change. That change left the SAN to "storage Area Network" un-available to the entire datacenter. GasBot Chat should be fine for now it's on a different segment. I have 2 spare chat servers but the DNS propagation time for fail-over might exceed the repair of the SAN time frame. If this were during peak hours we would have switched traffic. If it becomes an issue going forward I will fail us over to dtrch2 or dtrch3. I will keep everyone posted. Sorry for the trouble.

@rpm