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

3rd August 2024

No incidents reported

2nd August 2024

No incidents reported

1st August 2024

No incidents reported

31st July 2024

Web: Dallas OPAL4 - MariaDB has crashed.

MariaDB has crashed on OPAL4. We are investigating the cause of the crash and working to restore services.

  • We found and corrected a problem with database permissions and all database users should be able to connect now.

  • We're getting reports that some users still cannot connect to their databases so we are investigating that now.

  • Databases have been restored and should be fully operational.

  • The restore process is at 99% and the last databases are being restored.

  • The database restores are 66% complete.

  • The database restores are 51% complete.

  • The database restores are in progress and are ~25% complete.

  • The InnoDB data corruption is too bad to recover data from the database server. Tables are unreadable causing data dumps or repairs to the tables to be impossible.

    We have started the database repair process from our backups that were 3-5 hours old when the server went offline. We will update this post with our progress.

  • The data corruption on the server is in the innodb data which means there is potentially corrupted data across multiple databases due to how MySQL/MariaDB store data. We are still trying to recover and repair the data in the MariaDB server. If the data is too corrupt to repair we will restore the data from the latest backups. The latest backups were taken between 3 and 5 hours (depending on the dump time) before the database server crashed.

  • 30th July 2024

    No incidents reported

    29th July 2024

    No incidents reported

    28th July 2024

    No incidents reported