{
  "is": "issue",
  "title": "opal5 not responding",
  "body": "\u003cp\u003e\u003cem\u003eFixed\u003c/em\u003e - Opal5 is stable following the reboot. We\u0026rsquo;ll continue to monitor. \n  \u003cspan class=\"faded\"\u003e(18:44 UTC — Apr 18)\u003c/span\u003e\n\n\u003c/p\u003e\n\u003cp\u003e\u003cem\u003eInvestigating\u003c/em\u003e - Opal5 is back online, we\u0026rsquo;re still investigating. \n  \u003cspan class=\"faded\"\u003e(18:30 UTC — Apr 18)\u003c/span\u003e\n\n\u003c/p\u003e\n\u003cp\u003e\u003cem\u003eInvestigating\u003c/em\u003e - We\u0026rsquo;re rebooting opal5 at this time. \n  \u003cspan class=\"faded\"\u003e(18:22 UTC — Apr 18)\u003c/span\u003e\n\n\u003c/p\u003e\n\u003cp\u003e\u003cem\u003eInvestigating\u003c/em\u003e - The high load condition has returned so we\u0026rsquo;re continuing our investigation. \n  \u003cspan class=\"faded\"\u003e(18:11 UTC — Apr 18)\u003c/span\u003e\n\n\u003c/p\u003e\n\u003cp\u003e\u003cem\u003eFixed\u003c/em\u003e - Opal5 is back online. The problem was high load caused by heavy disk I/O activity due to high swap usage by a customer process. We\u0026rsquo;ve increased available swap and are working with the customer to resolve the issue. \n  \u003cspan class=\"faded\"\u003e(17:51 UTC — Apr 18)\u003c/span\u003e\n\n\u003c/p\u003e\n\u003cp\u003eOpal5 (shared hosting in Frankfurt DE) is currently not responding to web and SSH requests. We\u0026rsquo;re investigating. \n  \u003cspan class=\"faded\"\u003e(17:31 UTC — Apr 18)\u003c/span\u003e\n\n\u003c/p\u003e\n",
  "createdAt": "2022-04-18 17:31:00 +0000 UTC",
  "lastMod": "2022-04-18 17:31:00 +0000 UTC",
  "permalink": "https://opalstackstatus.com/issues/2022-04-18-opal5-not-responding/",
  "severity": "down",
  "resolved": true,
  "informational": false,
  "resolvedAt": "2022-04-18 18:44:09",
  "affected": ["Shared: Frankfurt (DE)"],
  "filename": "2022-04-18-opal5-not-responding.md"
}