{
  "is": "issue",
  "title": "Opal14 not responding",
  "body": "\u003cp\u003e\u003cem\u003eFixed\u003c/em\u003e - There was a second incident of the same type of problem but on a different site operated by the same customer. We\u0026rsquo;ve mitigated the problem to prevent it from occurring again and the server is stable at this time. \n  \u003cspan class=\"faded\"\u003e(14:53 UTC — Mar 31)\u003c/span\u003e\n\n\u003c/p\u003e\n\u003cp\u003e\u003cem\u003eWatching\u003c/em\u003e - Opal14 is back online. The cause of the issue was high Apache RAM usage which resulted from a bad rewrite rule in a customer site. We\u0026rsquo;ve isolated the site and are working with the customer to correct the problem. We\u0026rsquo;ll continue to monitor. \n  \u003cspan class=\"faded\"\u003e(23:20 UTC — Mar 30)\u003c/span\u003e\n\n\u003c/p\u003e\n\u003cp\u003eOpal14 (SFO shared hosting) is currently not responding. We\u0026rsquo;re investigating at this time. \n  \u003cspan class=\"faded\"\u003e(23:04 UTC — Mar 30)\u003c/span\u003e\n\n\u003c/p\u003e\n",
  "createdAt": "2024-03-30 23:04:31 +0000 UTC",
  "lastMod": "2024-03-30 23:04:31 +0000 UTC",
  "permalink": "https://opalstackstatus.com/issues/2024-03-30-opal14-not-responding/",
  "severity": "down",
  "resolved": true,
  "informational": false,
  "resolvedAt": "2024-03-31 14:53:17",
  "affected": ["Shared: San Francisco (USA)"],
  "filename": "2024-03-30-opal14-not-responding.md"
}