{
  "is": "issue",
  "title": "Opal3 not responding",
  "body": "\u003cp\u003e\u003cem\u003eFixed\u003c/em\u003e - The problem was caused by extremely high RAM usage from a process run by a hosting customer. We\u0026rsquo;ve notified the customer of the problem and have taken steps to prevent it from happening again. \n  \u003cspan class=\"faded\"\u003e(16:59 UTC — Jan 17)\u003c/span\u003e\n\n\u003c/p\u003e\n\u003cp\u003e\u003cem\u003eFixed\u003c/em\u003e - Opal3 is stable after the reboot. We\u0026rsquo;ll update this post when we\u0026rsquo;ve determined the cause of the outage. \n  \u003cspan class=\"faded\"\u003e(16:25 UTC — Jan 17)\u003c/span\u003e\n\n\u003c/p\u003e\n\u003cp\u003e\u003cem\u003eInvestigating\u003c/em\u003e - Opal3 is back online after a reboot. The cause of the outage is still under investigation. \n  \u003cspan class=\"faded\"\u003e(15:59 UTC — Jan 17)\u003c/span\u003e\n\n\u003c/p\u003e\n\u003cp\u003e\u003cem\u003eInvestigating\u003c/em\u003e - We\u0026rsquo;re rebooting Opal3 at this time. \n  \u003cspan class=\"faded\"\u003e(15:52 UTC — Jan 17)\u003c/span\u003e\n\n\u003c/p\u003e\n\u003cp\u003eopal3.opalstack.com is currently not responding. We\u0026rsquo;ll follow up here when more info is available. \n  \u003cspan class=\"faded\"\u003e(15:39 UTC — Jan 17)\u003c/span\u003e\n\n\u003c/p\u003e\n",
  "createdAt": "2021-01-17 15:39:44 +0000 UTC",
  "lastMod": "2021-01-17 15:39:44 +0000 UTC",
  "permalink": "https://opalstackstatus.com/issues/2021-01-17-opal3-not-responding/",
  "severity": "down",
  "resolved": true,
  "informational": false,
  "resolvedAt": "2021-01-17 16:59:24",
  "affected": ["Shared: San Francisco (USA)"],
  "filename": "2021-01-17-opal3-not-responding.md"
}