We believe this issue is now resolved (and has been for an hour or
so). We are still working to determine the root cause, but it appears
to be related to an internal network failure that affected some of our
hosts. We will be working to ensure this doesn't happen again.
Thanks,
Gary