{
  "is": "issue",
  "title": "opal11 not responding",
  "body": "\u003cp\u003e\u003cem\u003eFixed\u003c/em\u003e - We\u0026rsquo;re continuing to monitor the server to make sure there are no additional issues. \n  \u003cspan class=\"faded\"\u003e(00:10 UTC — Jul 16)\u003c/span\u003e\n\n\u003c/p\u003e\n\u003cp\u003e\u003cem\u003eFixed\u003c/em\u003e - After some difficulty with the chassis swap and subsequent firmware updates, the data center team has completed repairs and opal11 is now back online. \n  \u003cspan class=\"faded\"\u003e(23:52 UTC — Jul 15)\u003c/span\u003e\n\n\u003c/p\u003e\n\u003cp\u003e\u003cem\u003eIdentified\u003c/em\u003e - The data center team determined that a full chassis swap is required to repair the server. They are proceeding with that at this time. \n  \u003cspan class=\"faded\"\u003e(20:12 UTC — Jul 15)\u003c/span\u003e\n\n\u003c/p\u003e\n\u003cp\u003e\u003cem\u003eIdentified\u003c/em\u003e - The cause of the outage appears to be a failed memory module. The data center team is working to repair it at this time. \n  \u003cspan class=\"faded\"\u003e(19:02 UTC — Jul 15)\u003c/span\u003e\n\n\u003c/p\u003e\n\u003cp\u003eopal11 (Frankfurt DE shared hosting) is currently not responding. We\u0026rsquo;re investigating at this time. \n  \u003cspan class=\"faded\"\u003e(18:52 UTC — Jul 15)\u003c/span\u003e\n\n\u003c/p\u003e\n",
  "createdAt": "2025-07-15 18:52:47 +0000 UTC",
  "lastMod": "2025-07-15 18:52:47 +0000 UTC",
  "permalink": "https://opalstackstatus.com/issues/2025-07-15-opal11-not-responding/",
  "severity": "down",
  "resolved": true,
  "informational": false,
  "resolvedAt": "2025-07-16 00:10:31",
  "affected": ["Shared: Frankfurt (DE)"],
  "filename": "2025-07-15-opal11-not-responding.md"
}