Opal3 is currently not responding. We're investigating.
We've positively identified the cause of the memory spike and have mitigated it.
The root cause was a massive spike in system load due to a runaway customer process using most of the available system RAM. We'll work with the customer to ensure it doesn't happen again.
Opal3 is back online at this time. We'll continue to monitor.
We're rebooting opal3 at this time.
