{
  "is": "issue",
  "title": "Opal1 not responding",
  "body": "\u003cp\u003e\u003cem\u003eFixed\u003c/em\u003e - Opal1 is back online and stable online following a reboot.\u003c/p\u003e\n\u003cp\u003eThe issue was caused by high RAM usage by the server\u0026rsquo;s web-based database admin site. \n  \u003cspan class=\"faded\"\u003e(21:58 UTC — Jul 8)\u003c/span\u003e\n\n\u003c/p\u003e\n\u003cp\u003eOpal1 (Washington DC shared hosting) is currently not responding to requests.\u003c/p\u003e\n\u003cp\u003eWe suspect the issue is heavy server load, but we\u0026rsquo;re unable to log in to confirm so to restore service we\u0026rsquo;re now rebooting the server. \n  \u003cspan class=\"faded\"\u003e(21:40 UTC — Jul 8)\u003c/span\u003e\n\n\u003c/p\u003e\n",
  "createdAt": "2022-07-08 21:40:47 +0000 UTC",
  "lastMod": "2022-07-08 21:40:47 +0000 UTC",
  "permalink": "https://opalstackstatus.com/issues/2022-07-08-opal1-not-responding/",
  "severity": "down",
  "resolved": true,
  "informational": false,
  "resolvedAt": "2022-07-08 21:58:13",
  "affected": ["Shared: Washington D.C. (USA)"],
  "filename": "2022-07-08-opal1-not-responding.md"
}