All systems are operational
Maintenance
Scheduled network maintenance for opal3 and opal8

On 20 August 2026 between 11:00am and 4:00pm PDT (UTC-7) our data center team will be upgrading the racks that host the following servers:

  • opal3.opalstack.com
  • opal8.opalstack.com

During the 5-hour maintenance window, network connectivity to the affected servers will be interrupted for up to 1 hour during which websites and other services hosted on the servers will be unavailable.

Email and DNS services will not be affected.

The hosting control panel will remain online, but will be unable to apply changes to your services until connectivity to the server is restored.

Affected customers who would like have their services relocated to a different server prior to 20 August 2026 should contact the Opalstack support team to make the necessary arrangements.

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

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.

    29th April 2020

    No incidents reported

    28th April 2020

    No incidents reported