{
  "is": "issue",
  "title": "opal12 not responding",
  "body": "\u003cp\u003e\u003cem\u003eFixed\u003c/em\u003e - The outage was caused by a very heavy spike in system load, itself caused by a brief (but intense) attack from an abusive IP address. The problem has been mitigated and the server has been stable since our previous update. \n  \u003cspan class=\"faded\"\u003e(15:00 UTC — Jan 21)\u003c/span\u003e\n\n\u003c/p\u003e\n\u003cp\u003e\u003cem\u003eWatching\u003c/em\u003e - opal12 is back online and stable at this time. The cause of the outage is still under investigation. \n  \u003cspan class=\"faded\"\u003e(04:30 UTC — Jan 21)\u003c/span\u003e\n\n\u003c/p\u003e\n\u003cp\u003eopal12.opalstack.com (washington DC shared hosting) is currenty not responding. We\u0026rsquo;re investigating at this time. \n  \u003cspan class=\"faded\"\u003e(04:09 UTC — Jan 21)\u003c/span\u003e\n\n\u003c/p\u003e\n",
  "createdAt": "2025-01-21 04:09:43 +0000 UTC",
  "lastMod": "2025-01-21 04:09:43 +0000 UTC",
  "permalink": "https://opalstackstatus.com/issues/2025-01-21-opal12-not-responding/",
  "severity": "down",
  "resolved": true,
  "informational": false,
  "resolvedAt": "2025-01-21 15:00:05",
  "affected": ["Shared: Washington D.C. (USA)"],
  "filename": "2025-01-21-opal12-not-responding.md"
}