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

18th November 2020

No incidents reported

17th November 2020

No incidents reported

16th November 2020

Web: Frankfurt Apache down on opal6

The Apache httpd service on opal6 is currently down, we're looking into it.

  • The Opal6 Apache httpd and PHP-FPM services were hitting an open files limit. We've raised the limit and the services are back online.

    • 15th November 2020

    No incidents reported

    14th November 2020

    No incidents reported

    13th November 2020

    Email: USA Forwarding from US MX servers blocked by AT&T

    At this time AT&T is blocking mail forwarded from our US MX servers. We're working with AT&T to resolve the problem.

  • AT&T are no longer blocking mail forwarded from our US MX servers.

  • AT&T says that our US MX servers will be unblocked in 24-48 hours.

    • 12th November 2020

    No incidents reported

    11th November 2020

    Web: Dallas opal4 not responding

    Opal4 in Dallas TX USA is currently not responding to ping, we're looking into it.

  • Opal4 is operating normally.

  • Opal4 is currently under high load and not responding to most requests, we're looking into it.

  • Opal4 just experienced another load spike due to a network attack. We'll continue to monitor.

  • Opal4 has been stable since our last update.

  • The system was once again under heavy load due to a network attack. We'll continue to monitor.

  • Opal4 is responding to ping but the system is under heavy load, we will continue to investigate.

  • Opal4 is back online. The cause was a brief network attack.