All systems are operational
Maintenance
Scheduled downtime for opal4
  • When: October 26, 2026 19:00 - October 27, 2026 03:00 (US/Central)
  • Duration: Up to 8 hours

On October 26, 2026 at 19:00 US/Central time, opal4.opalstack.com will be taken offline and relocated to a new data center. The relocation may take up to 8 hours, but we are hopeful that it will be completed in less time.

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

Your server IP address will not change.

Your email accounts will remain online during the relocation.

If you would like to move to a different server prior to the scheduled downtime, please contact the Opalstack support team. Most managed migrations are completed with only a few minutes of downtime required.

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

Scheduled downtime for imap1.us.opalstack.com
  • When: October 27, 2026 19:00 - October 28, 2026 03:00 (US/Central)
  • Duration: Up to 8 hours

On October 27, 2026 at 19:00 US/Central time, imap1.us.opalstack.com will be taken offline and relocated to a new data center. The relocation may take up to 8 hours, but we are hopeful that it will be completed in less time.

Mailboxes on the server will be unavailable during the relocation. Affected customers have been notified individually.

Websites are hosted on separate infrastructure and will remain online during the relocation.

If you have any questions or concerns regarding this notice then please contact our support team and someone will get back to you.

Scheduled downtime for opal19
  • When: October 28, 2026 19:00 - October 29, 2026 03:00 (US/Central)
  • Duration: Up to 8 hours

On October 28, 2026 at 19:00 US/Central time, opal19.opalstack.com will be taken offline and relocated to a new data center. The relocation may take up to 8 hours, but we are hopeful that it will be completed in less time.

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

Your server IP address will not change.

Your email accounts will remain online during the relocation.

If you would like to move to a different server prior to the scheduled downtime, please contact the Opalstack support team. Most managed migrations are completed with only a few minutes of downtime required.

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

Past Incidents

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.

  • 30th July 2024

    No incidents reported