{
  "is": "issue",
  "title": "Opal4 not responding",
  "body": "\u003cp\u003e\u003cem\u003eFixed\u003c/em\u003e - We\u0026rsquo;ve successfully mitigated the attack and Opal4 has been stable since our last update. \n  \u003cspan class=\"faded\"\u003e(16:02 UTC — Feb 28)\u003c/span\u003e\n\n\u003c/p\u003e\n\u003cp\u003e\u003cem\u003eWatching\u003c/em\u003e - We\u0026rsquo;ve identified an ongoing attack pattern against sites on opal4 and have taken steps to mitigate it platform-wide. We\u0026rsquo;ll continue to monitor. \n  \u003cspan class=\"faded\"\u003e(16:08 UTC — Feb 27)\u003c/span\u003e\n\n\u003c/p\u003e\n\u003cp\u003e\u003cem\u003eInvestigating\u003c/em\u003e - Opal4 is back online.\u003c/p\u003e\n\u003cp\u003eThe problem was caused by high load following heavy RAM usage by the system `httpd` service. We\u0026rsquo;re still investigating the cause of the RAM usage. \n  \u003cspan class=\"faded\"\u003e(23:22 UTC — Feb 26)\u003c/span\u003e\n\n\u003c/p\u003e\n\u003cp\u003eOpal4 is currently unresponsive. We\u0026rsquo;ll update this incident when more info is available. \n  \u003cspan class=\"faded\"\u003e(22:55 UTC — Feb 26)\u003c/span\u003e\n\n\u003c/p\u003e\n",
  "createdAt": "2020-02-26 22:55:25 +0000 UTC",
  "lastMod": "2020-02-26 22:55:25 +0000 UTC",
  "permalink": "https://opalstackstatus.com/issues/2020-02-26-opal4-not-responding/",
  "severity": "down",
  "resolved": true,
  "informational": false,
  "resolvedAt": "2020-02-28 16:02:52",
  "affected": ["Shared: Dallas (USA)"],
  "filename": "2020-02-26-opal4-not-responding.md"
}