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

15th July 2021

No incidents reported

14th July 2021

No incidents reported

13th July 2021

No incidents reported

12th July 2021

Web: Frankfurt opal5 offline

Opal5 (shared hosting in Frankfurt) is offline. We're investigating at this time.

  • The null route has been removed and opal5 is back online.

  • The problem seems to be a network null route due to an abuse issue that has been mis-handled by an upstream provider. We're working on restoring service now.

  • 11th July 2021

    No incidents reported

    10th July 2021

    No incidents reported

    9th July 2021

    Web: San Francisco Apache was down on Opal8

    The system Apache httpd service on was briefly offline due to a problem with its configured system resource limits.

    During the incident customers visiting the Apache-powered sites may have seen a "502 bad gateway" error message.

    The problem has been corrected and the service is working normally at this time.