Servers: opal3.opalstack.com
Fixed - We’ve positively identified the cause of the memory spike and have mitigated it. (13:38 UTC — Sep 10)
Watching - 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. (13:17 UTC — Sep 10)
Watching - Opal3 is back online at this time. We’ll continue to monitor. (13:11 UTC — Sep 10)
Investigating - We’re rebooting opal3 at this time. (13:00 UTC — Sep 10)
Opal3 is currently not responding. We’re investigating. (12:02 UTC — Sep 10)