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

4th June 2024

No incidents reported

3rd June 2024

No incidents reported

2nd June 2024

No incidents reported

1st June 2024

No incidents reported

31st May 2024

DNS outage (resolved)

About 1 hour ago a failed DNS sync with our alternate DNS provider caused an outage in our DNS servers. The outage lasted approximately 1 hour during which customers may have experience trouble accessing Opalstack systems.

The problem has been resolved and all DNS services are working normally at this time, however there may be lingering effects due to global DNS propagation. These issues will resolve themselves over the next few hours. You may be able to resolve them sooner for yourself by flushing your DNS and/or by power-cycling your devices.

30th May 2024

Web: San Francisco Intermittent high load on opal14

At this time we are tracking an high load condition on opal14.opalstack.com (San Francisco shared hosting) which has been causing the server to become unresponsive on an intermittent basis. The problem appears to be caused by high memory usage by the system Apache service.

We're working to identify the customer site that is causing the high memory usage and will work with them to resolve the issue once we've identified it.

  • We believe we identified the customer site that has been causing these issues and have taken action to mitigate it. We will continue to monitor a couple more days.

    • 29th May 2024

    No incidents reported