{
  "is": "issue",
  "title": "unexpected reboot of opal4",
  "body": "\u003cp\u003e\u003cem\u003eFixed\u003c/em\u003e - Opal4 has remained stable for the past several hours. We haven\u0026rsquo;t been able to determine the precise cause of the unexpected reboots earlier today but we suspect it was a possible fault in the server\u0026rsquo;s remote management interface. We\u0026rsquo;ve reset that system and are seeing further no problems at this time. \n  \u003cspan class=\"faded\"\u003e(22:59 UTC — Jun 6)\u003c/span\u003e\n\n\u003c/p\u003e\n\u003cp\u003e\u003cem\u003eInvestigating\u003c/em\u003e - opal4 is back online at this time. Our investigation is still in progress. \n  \u003cspan class=\"faded\"\u003e(16:46 UTC — Jun 6)\u003c/span\u003e\n\n\u003c/p\u003e\n\u003cp\u003e\u003cem\u003eInvestigating\u003c/em\u003e - opal4 is once again offline for troubleshooting and maintenance. During this time, the server may be placed into a rescue mode where it will respond to ping, but SSH connections will fail and other services will not be available. \n  \u003cspan class=\"faded\"\u003e(16:01 UTC — Jun 6)\u003c/span\u003e\n\n\u003c/p\u003e\n\u003cp\u003e\u003cem\u003eInvestigating\u003c/em\u003e - opal4 is experiencing heavy load at this time. \n  \u003cspan class=\"faded\"\u003e(15:21 UTC — Jun 6)\u003c/span\u003e\n\n\u003c/p\u003e\n\u003cp\u003e\u003cem\u003eInvestigating\u003c/em\u003e - Opal4 is back online at this time, the investigation is ongoing. \n  \u003cspan class=\"faded\"\u003e(14:46 UTC — Jun 6)\u003c/span\u003e\n\n\u003c/p\u003e\n\u003cp\u003e\u003cem\u003eInvestigating\u003c/em\u003e - opal4 is now being taken offline for emergency maintenance. \n  \u003cspan class=\"faded\"\u003e(13:59 UTC — Jun 6)\u003c/span\u003e\n\n\u003c/p\u003e\n\u003cp\u003e\u003cem\u003eInvestigating\u003c/em\u003e - The server was rebooted again unexpectedly, we\u0026rsquo;re investigating the cause. \n  \u003cspan class=\"faded\"\u003e(13:29 UTC — Jun 6)\u003c/span\u003e\n\n\u003c/p\u003e\n\u003cp\u003e\u003cem\u003eInvestigating\u003c/em\u003e - We\u0026rsquo;ve lost connectivity to opal4 and suspect another reboot, we\u0026rsquo;re investigating further. \n  \u003cspan class=\"faded\"\u003e(13:21 UTC — Jun 6)\u003c/span\u003e\n\n\u003c/p\u003e\n\u003cp\u003eopal4.opalstack.com (Dallas shared hosting) rebooted unexpectedly a few moments ago as around 12:25 UTC. The server is back online and operating normally at this time. \n  \u003cspan class=\"faded\"\u003e(12:46 UTC — Jun 6)\u003c/span\u003e\n\n\u003c/p\u003e\n",
  "createdAt": "2025-06-06 12:46:27 +0000 UTC",
  "lastMod": "2025-06-06 12:46:27 +0000 UTC",
  "permalink": "https://opalstackstatus.com/issues/2025-06-06-unexpected-reboot-of-opal4/",
  "severity": "down",
  "resolved": true,
  "informational": false,
  "resolvedAt": "2025-06-06 22:59:55",
  "affected": ["Shared: Dallas (USA)"],
  "filename": "2025-06-06-unexpected-reboot-of-opal4.md"
}