Problem appears to be related either to our host, @ServInt, or a general unhealthy Internet backbone somewhere. Should be resolved soon.