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

5th June 2025

No incidents reported

4th June 2025

Web: Dallas heavy load on opal4

opal4.opalstack.com (Dallas shared hosting) is currently experiencing heavy load resulting in very poor performance. We're investigating at this time.

  • The cause of the high load was a compromised customer website. We've locked down the affected site and have notified the site operator of the issue.

  • opal4 is back online. We're still investigating the cause of the high load.

  • We're rebooting opal4 at this time.

    • 3rd June 2025

    No incidents reported

    2nd June 2025

    No incidents reported

    1st June 2025

    Web: Washington D.C. Unexpected reboot of opal12

    opal12.opalstack.com (Washington DC shared hosting) was rebooted unexpectedly on Sunday, 1 June 2025 at around 11:20 UTC. The reboot was caused by a power issue. The server was back online at 11:27 UTC and has been operating normally since

    31st May 2025

    Web: Frankfurt opal5 not responding

    Opal5 (Frankfurt shared hosting) is not responding, so we're rebooting the machine to restore service.

  • The reboot is complete and opal5 is back online. The cause of the outage was high load due to malicious traffic from an abusive network. The network has been blocked.

    • 30th May 2025

    No incidents reported