All systems are operational
Maintenance
Scheduled DE IMAP/POP3 email server downtime

On 24 September 2026 at between 07:00 am and 10:00 am UTC our network team will be relocating one of our mailbox storage servers to a new location within the data center.

The server will be offline during the relocation. As a result, some customer mailboxes will be unavailable for up to 3 hours during the relocation. Affected customers will be notified directly via email.

Affected customers will not be able to check their email for affected mailboxes during the relocation.

No incoming mail will be lost during the relocation. Mail that arrives during the relocation 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 relocation will not be stored as sent mail in IMAP folders on the server.

Customer websites will not be affected by the relocation.

We realize that the timing of this relocation may not be ideal. Customer who would like to have their mailboxes migrated to a different server in advance of the server relocation should contact the Opalstack support team to make the necessary arrangements.

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 email our support team and someone from our team will get back to you as soon as possible.

Past Incidents

9th January 2020

No incidents reported

8th January 2020

Web: Dallas Intermittent outages on opal4

opal4.opalstack.com is experiencing intermittent outages. We're looking into it and will update this item when we have more information.

  • During last week's maintenance our upstream provider updated the server firmware on opal4. We've seen no further issues since that time.

  • The maintenance is complete and Opal4 is back online. We'll continue to monitor.

  • Opal4 is down for the emergency maintenance scheduled earlier today. The total expected downtime is less than one hour.

  • Opal4 will be going down this evening at 9PM US Central (2020-04-01 21:00 UTC-5) for emergency maintenance. The total downtime should be less than one hour.

    The ongoing issue on opal4 has been high system load caused by two separate types of attacks:

    1. High Apache RAM usage due to attacks against common targets like Wordpress sites
    2. High CPU usage by the system firewall under a high volume of SYN packets

    We've resolved the first problem by tuning our application firewall rules and by working with a couple of specific site owners that were receiving the brunt of the attacks.

    The second problem is part of what we're troubleshooting this evening.

    At first glance the SYN packet issue would seem like a common SYN flood attack but other shared servers in our infrastructure receive similar amounts of traffic and don't have any problems mitigating it.

    In the past 24 hours we've discovered key differences in Opal4's hardware compared to the other servers, so we're working with our upstream provider to sort that out.

    Tonight's downtime is at their request to allow them to perform hardware diagnostics in support of that investigation.

  • Opal4 just went through a brief spike in system load during which performance was degraded, but the system is back to normal at this time.

  • We've identified two distinct attack patterns responsible for the intermittent outages on opal4 and are putting measures in place to mitigate them.

  • This intermittent issue on Opal4 has started up again - we will continue to monitor as we work to resolve it.

  • We've seen no further issues in the past several hours.

  • The problem appears to have been caused by temporary high load due to high CPU usage by the system firewall.

    opal4 is stable at this time. We'll continue to monitor.

    • 7th January 2020

    No incidents reported

    6th January 2020

    No incidents reported

    5th January 2020

    No incidents reported

    4th January 2020

    No incidents reported

    3rd January 2020

    No incidents reported