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.

Scheduled downtime for opal6

On 23 May 2025 from 0700 - 1100 UTC opal6.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

16th September 2021

Web: Frankfurt Intermittent high load on opal11

Our shared hosting server opal11.opalstack.com in Frankfurt Germany is experiencing an intermittent high load condition which is impacting system performance. We're working to resolve this and will update this post when the issue is resolved.

  • There have been no further issues on opal11 in the past 24 hours so we consider this to be resolved.

  • We've mitigated most of the abusive traffic that's been driving up high load on opal11 and performance should be much better at this time.

    We are still seeing occasional spikes and will continue to investigate.

  • Our investigation into this issue is ongoing. We'll provide more info when it is available.

    • 15th September 2021

    No incidents reported

    14th September 2021

    No incidents reported

    13th September 2021

    No incidents reported

    12th September 2021

    No incidents reported

    11th September 2021

    No incidents reported

    10th September 2021

    Web: San Francisco opal3 not responding

    Opal3 is currently not responding. We're investigating.

  • We've positively identified the cause of the memory spike and have mitigated it.

  • The root cause was a massive spike in system load due to a runaway customer process using most of the available system RAM. We'll work with the customer to ensure it doesn't happen again.

  • Opal3 is back online at this time. We'll continue to monitor.

  • We're rebooting opal3 at this time.