Okay - service seems to be returning to normal.
Sorry for the interruption everybody
Quick technical explanation for anybody interested…
Our database has a primary & secondary server, so if the primary has an issue, it fails over onto the secondary one and keeps going with only a minor hiccup. Stuff like that happens a few times a year maybe.
Our problem here happened when the failover didn’t occur quickly enough, and for an unknown reason, the secondary database died. When everything came back online, something wasn’t quite right (a very high load was on the new primary server), and we had to optimize a few things before it started working again. We’ll investigate more tomorrow when we’re back in the office, and determine the exact cause of what went wrong.