All systems are operational
Maintenance
Scheduled network maintenance for opal3 and opal8

On 20 August 2026 between 11:00am and 4:00pm PDT (UTC-7) our data center team will be upgrading the racks that host the following servers:

  • opal3.opalstack.com
  • opal8.opalstack.com

During the 5-hour maintenance window, network connectivity to the affected servers will be interrupted for up to 1 hour during which websites and other services hosted on the servers will be unavailable.

Email and DNS services will not be affected.

The hosting control panel will remain online, but will be unable to apply changes to your services until connectivity to the server is restored.

Affected customers who would like have their services relocated to a different server prior to 20 August 2026 should contact the Opalstack support team to make the necessary arrangements.

Scheduled US IMAP email server downtime

On 26 August 2026 at between 11:00 am and 4:00 pm US/Pacific time our network team will be performing infrastructure maintenance. During this 5-hour window, network connectivity to one of our US IMAP/POP3 email servers will be interrupted for up to 1 hour.

As a result, some customer mailboxes will be unavailable for up to 1 hour during the network interruption. Customers who will be impacted by the interruption have been emailed directly.

No incoming mail will be lost during the interruption. Mail that arrives during the interruption will be deferred and delivered once connectivity to the mail server is restored.

Email forwarding and SMTP services will not be affected, however messages sent via SMTP during the interruption will not be stored as sent mail in IMAP folders on the server.

We'll update our status page at http://status.opalstack.com/ at the beginning of the maintenance window. To be informed of system status updates automatically please subscribe at https://status.opalstack.com/subscribe.

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

Past Incidents

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.

  • 8th March 2025

    No incidents reported

    7th March 2025

    No incidents reported

    6th March 2025

    No incidents reported

    5th March 2025

    No incidents reported

    4th March 2025

    No incidents reported

    3rd March 2025

    Email: Germany DE SMTP blocked by iCloud

    At the present time email sent to @icloud.com addresses via our DE SMTP server is being either deferred or bounced. We're working with Apple to resolve the issue and will update this post when more information is available.

    In the meantime, DE mail customers can work around the issue by using our alternate DE SMTP server in their email client settings. The alternate server is: smtp2.de.opalstack.com

  • The block was cleared as of 14:22 UTC today. Mail sent to iCloud email addresses via our DE SMTP are no longer bouncing.

  • Apple informed us that our SMTP is caught up in a block of a larger IP address range operated by our network provider. Our provider is working with Apple to resolve the issue.

    If you are affected by this you can configure your mail client to use smtp2.de.opalstack.com as its SMTP server as a temporary workaround.

  • Apple informed us that our SMTP is caught up in a block of a larger IP address range operated by our network provider. Our provider is working with Apple to resolve the issue.

    If you are affected by this you can configure your mail client to use smtp2.de.opalstack.com as its SMTP server as a temporary workaround.