{
  "is": "issue",
  "title": "Unplanned reboot of opal3",
  "body": "\u003cp\u003eOn Saturday 10 December at around 0800 UTC (midnight US/Pacific) opal3.opalstack.com in San Francisco became unresponsive. After several unsuccessful attempts to access the server for troubleshooting, we rebooted the server and it was back online around 0900 UTC (1am US/Pacific).\u003c/p\u003e\n\u003cp\u003eThe outage appears to have been triggered by a very rapid spike in system memory usage. The high load unfortunately interrupted the system logging facilities so we weren\u0026rsquo;t able to precisely identify the cause, but we suspect that it was due to an buggy Apache rewrite rule in a customer application. \n  \u003cspan class=\"faded\"\u003e(00:00 UTC — Dec 10)\u003c/span\u003e\n\n\u003c/p\u003e\n",
  "createdAt": "2022-12-10 00:00:00 +0000 UTC",
  "lastMod": "2022-12-10 00:00:00 +0000 UTC",
  "permalink": "https://opalstackstatus.com/issues/2022-12-10-unplanned-reboot-of-opal3/",
  "severity": "down",
  "resolved": true,
  "informational": false,
  "resolvedAt": "2022-12-13 21:05:56",
  "affected": ["Shared: San Francisco (USA)"],
  "filename": "2022-12-10-unplanned-reboot-of-opal3.md"
}