All systems are operational
Maintenance
Scheduled downtime for opal9

On 20 May 2025 from 0700 - 1100 UTC opal9.opalstack.com (Frankfurt DE shared hosting) will be taken offline and relocated to a new rack within the data center.

Customer websites, files, and databases hosted on the server will be unavailable during the relocation.

Customer email accounts will remain online during the relocation. The server IP address will not change.

The maintenance window is 4 hours but the data center team will do everything possible to minimize the downtime within that period.

If you would like to move to a different server prior to the scheduled downtime, please email the Opalstack support team to request a migration.

We apologize for any inconvenience. If you have any questions or concerns regarding the maintenance then please email our support team and someone will get back to you as soon as possible.

Past Incidents

16th March 2025

No incidents reported

15th March 2025

No incidents reported

14th March 2025

No incidents reported

13th March 2025

No incidents reported

12th March 2025

No incidents reported

11th March 2025

No incidents reported

10th March 2025

No incidents reported

9th March 2025

Web: Dallas OPAL4 MariaDB Outage

MariaDB on OPAL4 has crashed, we're working to identify the cause and solution now.

  • We've seen no further problems since our last update.

  • The issue with database permissions is resolved and the MariaDB service is back online and operating normally. We will continue to monitor.

  • We've discovered that there is still a problem with database permissions. We're working to resolve that at this time.

  • The data restoration has completed and we are continuing to monitor the server as usage increases.

  • The restoration is approximately 75% complete.

  • The data restoration is approximately 50% complete.

  • The MariaDB restore process is still running.

  • The database corruption is unrecoverable so we will proceed with restoring from backups. The most recent valid backups were from 1.5 hours before the server crashed so we'll proceed with the restore from there.

    The restoration process varies in completion time. It may take up to 6 hours or more. We'll keep this post updated.