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

6th May 2020

No incidents reported

5th May 2020

No incidents reported

4th May 2020

No incidents reported

3rd May 2020

No incidents reported

2nd May 2020

No incidents reported

1st May 2020

No incidents reported

30th April 2020

Web: Dallas Opal4 not responding

Opal4 is not responding. We're looking into the cause.

  • We believe this latest issue was caused by a DNS reflection attack.

    We're consulting with our upstream provider to see what they can do to protect the server and network from future attacks.

  • Opal4 is back online, investigation is ongoing.

  • Web: Dallas Apache was not responding on Opal4

    Apache was once again not responding on Opal4 after hitting its configured ServerLimit. The underlying cause appears to have been a high number of PHP-FPM processes being re-spawned for one customer site. We've adjusted the PHP-FPM configuration for that site to avoid the problem in the future.