{
  "is": "issue",
  "title": "Opal12 was offline",
  "body": "\u003cp\u003e\u003cem\u003eFixed\u003c/em\u003e - We\u0026rsquo;ve confirmed that the maintenance is complete and there are no further issues at this time. \n  \u003cspan class=\"faded\"\u003e(02:35 UTC — May 14)\u003c/span\u003e\n\n\u003c/p\u003e\n\u003cp\u003e\u003cem\u003eWatching\u003c/em\u003e - Opal12 is back online and we\u0026rsquo;re awaiting confirmation from the data center that the maintenance is complete. \n  \u003cspan class=\"faded\"\u003e(02:20 UTC — May 14)\u003c/span\u003e\n\n\u003c/p\u003e\n\u003cp\u003e\u003cem\u003eWatching\u003c/em\u003e - Opal12 is now offline for scheduled maintenance. \n  \u003cspan class=\"faded\"\u003e(01:00 UTC — May 14)\u003c/span\u003e\n\n\u003c/p\u003e\n\u003cp\u003e\u003cem\u003eWatching\u003c/em\u003e - Opal12 will be going offline for troubleshooting and repair in approximately 50 minutes at 9PM US/Eastern time. \n  \u003cspan class=\"faded\"\u003e(00:12 UTC — May 14)\u003c/span\u003e\n\n\u003c/p\u003e\n\u003cp\u003e\u003cem\u003eWatching\u003c/em\u003e - We\u0026rsquo;ve scheduled maintenance downtime on opal12 to correct the issue with the network controller. Details are at \u003ca href=\"https://status.opalstack.com/schedules/36\"\u003ehttps://status.opalstack.com/schedules/36\u003c/a\u003e. \n  \u003cspan class=\"faded\"\u003e(14:13 UTC — May 9)\u003c/span\u003e\n\n\u003c/p\u003e\n\u003cp\u003e\u003cem\u003eWatching\u003c/em\u003e - We suspect that the server\u0026rsquo;s network controller is failing. We\u0026rsquo;re now working with the data center team to have the problem corrected. \n  \u003cspan class=\"faded\"\u003e(19:54 UTC — May 7)\u003c/span\u003e\n\n\u003c/p\u003e\n\u003cp\u003eOpal12 (Washington DC shared hosting) was offline for approximately 25 minutes beginning at 18:53 UTC due to an interruption in network connectivity.\u003c/p\u003e\n\u003cp\u003eWe rebooted the server approximately 10 minutes later.\u003c/p\u003e\n\u003cp\u003eThe server is back online and we\u0026rsquo;re working with our data center team to determine the cause of the problem. \n  \u003cspan class=\"faded\"\u003e(18:53 UTC — May 7)\u003c/span\u003e\n\n\u003c/p\u003e\n",
  "createdAt": "2022-05-07 18:53:00 +0000 UTC",
  "lastMod": "2022-05-07 18:53:00 +0000 UTC",
  "permalink": "https://opalstackstatus.com/issues/2022-05-07-opal12-was-offline/",
  "severity": "down",
  "resolved": true,
  "informational": false,
  "resolvedAt": "2022-05-14 02:35:03",
  "affected": ["Shared: Washington D.C. (USA)"],
  "filename": "2022-05-07-opal12-was-offline.md"
}