All systems are operational
Upcoming change to Apache/PHP-CGI apps

On 31 January 2022 we'll begin a phased rollout of a change to our Apache/PHP-CGI setup to transition from PHP-CGI to PHP-FPM.

This change will improve the performance of all Apache/PHP applications hosted at Opalstack. There are a high number of these apps installed throughout the platform, so this change should also improve the overall performance of our servers for all customers.

We do not anticipate any disruptions related to this change.

We'll update this maintenance item when the rollout begins and as it progresses.

If you have any questions or concerns regarding this change then please email them to

2022-02-05 14:18 UTC - we've been rolling out these changes slowly across a small number of customer VPS and so far no problems have been noted. We'll be ramping up the rollout over the coming week.

2022-05-09 14:00 UTC - all VPS have been updated to use the Apache/PHP-FPM stack. We've also deployed the changes on 1 shared server (opal14, SFO shared) as of 2022-05-09 0300 UTC and will monitor that server for a couple of days before moving on to the other shared servers.

2022-05-22 11:00 UTC opal1 and opal12 have been updated to use the Apache/PHP-FPM stack.

Past Incidents

14th May 2022

No incidents reported

13th May 2022

Email: USA US SMTP blacklisted

Our US SMTP service is currently blacklisted. We're working with the blacklist operators to identify the cause and will have it corrected as soon as possible.

  • We've identified and shut down several websites with insecure contact forms which were sending spam. The site operators have been notified and the US SMTP is no longer blacklisted.

  • 12th May 2022

    No incidents reported

    11th May 2022

    No incidents reported

    10th May 2022

    No incidents reported

    9th May 2022

    No incidents reported

    8th May 2022

    No incidents reported

    7th May 2022

    Web: Washington D.C. Opal12 was offline

    Opal12 (Washington DC shared hosting) was offline for approximately 25 minutes beginning at 18:53 UTC due to an interruption in network connectivity.

    We rebooted the server approximately 10 minutes later.

    The server is back online and we're working with our data center team to determine the cause of the problem.

  • We've confirmed that the maintenance is complete and there are no further issues at this time.

  • Opal12 is back online and we're awaiting confirmation from the data center that the maintenance is complete.

  • Opal12 is now offline for scheduled maintenance.

  • Opal12 will be going offline for troubleshooting and repair in approximately 50 minutes at 9PM US/Eastern time.

  • We've scheduled maintenance downtime on opal12 to correct the issue with the network controller. Details are at

  • We suspect that the server's network controller is failing. We're now working with the data center team to have the problem corrected.