All systems are operational
Maintenance
Scheduled downtime for opal9

On 20 May 2025 from 0700 - 1100 UTC opal9.opalstack.com (Frankfurt DE shared hosting) will be taken offline and relocated to a new rack within the data center.

Customer websites, files, and databases hosted on the server will be unavailable during the relocation.

Customer email accounts will remain online during the relocation. The server IP address will not change.

The maintenance window is 4 hours but the data center team will do everything possible to minimize the downtime within that period.

If you would like to move to a different server prior to the scheduled downtime, please email the Opalstack support team to request a migration.

We apologize for any inconvenience. If you have any questions or concerns regarding the maintenance then please email our support team and someone will get back to you as soon as possible.

Past Incidents

24th January 2025

No incidents reported

23rd January 2025

No incidents reported

22nd January 2025

No incidents reported

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.