All systems are operational
Maintenance
Scheduled US IMAP email server downtime

On 26 August 2026 at between 11:00 am and 4:00 pm US/Pacific time our network team will be performing infrastructure maintenance. During this 5-hour window, network connectivity to one of our US IMAP/POP3 email servers will be interrupted for up to 1 hour.

As a result, some customer mailboxes will be unavailable for up to 1 hour during the network interruption. Customers who will be impacted by the interruption have been emailed directly.

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

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 contact the Opalstack support team.

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