This incident has been resolved. We have completed our investigation and attributed it to a stuck backup process that overloaded the machine's CPU usage. After remotely logging in and killing that process, the machine still refused to respond, in which a reboot command was executed. The machine rebooted and came back online with no errors afterward.