Actually, it appears to have resolved itself since I posted that last report. Perhaps I was just catching the tail end of the maintenance process or something.