After a database crash on Friday, the site was unreachable. Pair worked over the weekend to recover the data in the database, so we didn't have to restore from backup and lose about 24 hours of activity. The recovery took about 48 hours (and a felt eternity), as MySQLd took its time rebuilding various ISAM indices. At various times I wondered whether it would have been OK to ditch 24 hours of site activity in favour of bringing the site back up quicker.
We thank Pair for proactively noticing that the database server had problems and initiating a recovery even before we opened a ticket for that.
There are some things that are broken, like Best Nodes and Worst Nodes, because the jobs that (re)create those listings did not run, but that should fix itself within the next 24 hours. If you note any other unusual weirdness or brokenness, please reply here.
It's great to have you all back again!