Some systems are experiencing issues

Stickied Incidents

12th September 2024

Web: Washington D.C. opal12 blocked by Malwarebytes

At this time opal12.opalstack.com (Washington DC shared hosting) is being blocked by Malwarebytes. The cause was an outbound SSH attack from a compromised customer shell account which caused the server to be listed in a major block list. As a result visitors who use Malwarebytes may see a warning when visiting sites hosted on opal12.

We're working with the block list operator to have the server delisted and expect to have this resolved within the next couple of days.

In the meantime, you may be able to work around the problem by adding your site domain and/or server IP 207.244.121.250 to your Malwarebytes exception list.

Past Incidents

18th March 2024

Dashboard Control panel processing delays

At this time there is a log backlog of pending operations in the control panel. We're working to clear the backlog and will update this post when the issue is resolved.

  • The backlog of pending items is now clear.

    • 17th March 2024

    No incidents reported

    16th March 2024

    No incidents reported

    15th March 2024

    No incidents reported

    14th March 2024

    No incidents reported

    13th March 2024

    No incidents reported

    12th March 2024

    Dashboard DNS issue for opalstack.com causing control panel delays and other issues

    At this time there is a delay in processing new items and changes in the control panel at https://my.opalstack.com/. We're looking into it and will follow up as soon as possible.

  • DNS has propagated on our end and the backlog of pending control panel changes is now clear.

    If you have DNS problems like "host not found" when accessing any Opalstack systems then please try flushing your local DNS cache: https://www.wikihow.com/Flush-DNS

    For further assistance please email the Opalstack support team.

  • We've identified the problem as 2 name servers which were failing to return records for opalstack.com hostnames. We've removed those name servers from our pool and are monitoring while the DNS change propagates.