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

10th December 2024

No incidents reported

9th December 2024

No incidents reported

8th December 2024

No incidents reported

7th December 2024

Web: Phoenix OPAL7 MariaDB Server Offline

The MariaDB server on OPAL7 has stopped responding to queries. We're investigating this failure now.

  • The MariaDB recovery is complete and by all indications customer sites should be working normally at this time. If you have a site hosted on opal7 and notice any problems then please contact our support team for further assistance.

  • At this time we are rebooting opal7. The recovery is nearly complete.

  • The restoration process is 80% complete.

  • Databases are still restoring.

  • Databases are continuing to be restored. We do not have an ETA on when the full restore will be finished but we'll keep this post updated.

  • The recovery of MariaDB has been unsuccessful through all of the recovery methods. We will begin restoring the databases from latest backup.

    The latest backup was taken ~4 hours before the MariaDB server went offline.

  • The InnoDB transaction log has been corrupted. We're working to restore service by running in recovery mode.

  • 6th December 2024

    No incidents reported

    5th December 2024

    No incidents reported

    4th December 2024

    No incidents reported