All systems are operational
Maintenance
US IMAP email server downtime

On 22 July 2026 at 10:00 am US/Central time (UTC -5) one of our US IMAP email servers will be shut down for infrastructure maintenance. The server will be offline during the maintenance and the expected downtime is 6 hours.

Affected customers will be notified individually via email.

No incoming mail will be lost while the server is offline. Mail that arrives during the maintenance will be deferred and delivered once the mail server is back online.

We realize that the timing of this relocation is not ideal. If you have business-critical mailboxes and would like them to be available during the maintenance then please email support@opalstack.com or reply to this message to make arrangements to have your mailboxes migrated to a different IMAP server prior to the scheduled maintenance date.

If you have any questions or concerns regarding this maintenance then please email the Opalstack support team for assistance.

Past Incidents

6th August 2024

No incidents reported

5th August 2024

No incidents reported

4th August 2024

No incidents reported

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.