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

2nd April 2024

Email: USA Delays in US incoming mail

At this time there is a high load condition on one of our US IMAP servers which is a variety of issues for some US mail customers including:

  • Delays in the receipt of incoming mail
  • Slow performance in IMAP mail clients
  • Slow performance in the Opalstack US webmail system

We're working to mitigate the problem at this time and will update this post when more information is available.

  • All pending incoming US mail has been delivered.

  • The high load condition is resolved and the backlog of pending mail is being delivered.

    • 1st April 2024

    No incidents reported

    31st March 2024

    No incidents reported

    30th March 2024

    Web: San Francisco Opal14 not responding

    Opal14 (SFO shared hosting) is currently not responding. We're investigating at this time.

  • There was a second incident of the same type of problem but on a different site operated by the same customer. We've mitigated the problem to prevent it from occurring again and the server is stable at this time.

  • Opal14 is back online. The cause of the issue was high Apache RAM usage which resulted from a bad rewrite rule in a customer site. We've isolated the site and are working with the customer to correct the problem. We'll continue to monitor.

    • 29th March 2024

    No incidents reported

    28th March 2024

    No incidents reported

    27th March 2024

    No incidents reported