Sorry for the trouble this caused, everyone. We believe we've identified the bottleneck that caused today's issues and we're taking steps to try and prevent this from happening again.

It will take us a few days to do the work, but we should be able to prevent this without actually needing to move any accounts. Instead, we'll rearrange some of the services on the various machines, and add more hardware dedicated to the specific portion of the service that got bogged down today.

Thanks for the response Brian. Sounds good.