Yesterday, Ookles and Audible both had server problems.
I don't even know what Ookles is, except that it's Scott Johnson's new baby, and so it's bound to be cool when he gets around to telling us what it does. But Scott was quick to mention that they had a server failure, resulting in the new company's first full-scale fire drill. Good podcast topic.
Audible was down too, at least for me: downloading my new book took 6 hours yesterday, a retry overnight got only half-way, and now we're 90 minutes into the third attempt. Yesterday, I could get about 1K/sec; today it's up to 10K/sec; it's still pretty hopeless.
But there's no way to know whether Audible is aware they have a problem.