All systems are operational

Past Incidents

22nd January 2025

No incidents reported

21st January 2025

Web: Washington D.C. opal12 not responding

opal12.opalstack.com (washington DC shared hosting) is currenty not responding. We're investigating at this time.

  • 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.

  • opal12 is back online and stable at this time. The cause of the outage is still under investigation.

    • 20th January 2025

    No incidents reported

    19th January 2025

    No incidents reported

    18th January 2025

    No incidents reported

    17th January 2025

    Web: Frankfurt High load on opal15

    opal15.opalstack.com (Frankfurt shared hosting) is currently experiencing heavy load. We're working to resolve it at this time.

  • We've identified the cause of the problem and have taken measures to mitigate it as of about 3 hours ago. The server has been stable since that time.

  • The high load was caused by heavy CPU usage from the MariaDB service. We're still working to identify the exact cause but the server is stable at this time.

    • 16th January 2025

    Web: Washington D.C. MariaDB down on opal10

    At this time the MariaDB service on opal10 is offline. We're working to restore service and will update this post when more information is available.

  • The recovery is complete and the database service is back online.

  • We've been unable to recover the MariaDB service in-place, so we're restoring the service from the most recent backup which was completed about 13 hours ago at 04:21 UTC.

    The estimated recovery time is 4 hours or less. We'll update this post when more information is available.

  • The MariaDB InnoDB store on opal10 is corrupted. We're still working to recover but do not have an ETA at this time.