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

21st January 2025

Web: Washington D.C. opal12 not responding

opal12.opalstack.com (washington DC shared hosting) is currenty not responding. We're investigating at this time.

  • The outage was caused by a very heavy spike in system load, itself caused by a brief (but intense) attack from an abusive IP address. The problem has been mitigated and the server has been stable since our previous update.

  • opal12 is back online and stable at this time. The cause of the outage is still under investigation.

    • 20th January 2025

    No incidents reported

    19th January 2025

    No incidents reported

    18th January 2025

    No incidents reported

    17th January 2025

    Web: Frankfurt High load on opal15

    opal15.opalstack.com (Frankfurt shared hosting) is currently experiencing heavy load. We're working to resolve it at this time.

  • We've identified the cause of the problem and have taken measures to mitigate it as of about 3 hours ago. The server has been stable since that time.

  • The high load was caused by heavy CPU usage from the MariaDB service. We're still working to identify the exact cause but the server is stable at this time.

    • 16th January 2025

    Web: Washington D.C. MariaDB down on opal10

    At this time the MariaDB service on opal10 is offline. We're working to restore service and will update this post when more information is available.

  • The recovery is complete and the database service is back online.

  • We've been unable to recover the MariaDB service in-place, so we're restoring the service from the most recent backup which was completed about 13 hours ago at 04:21 UTC.

    The estimated recovery time is 4 hours or less. We'll update this post when more information is available.

  • The MariaDB InnoDB store on opal10 is corrupted. We're still working to recover but do not have an ETA at this time.

    • 15th January 2025

    No incidents reported