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

8th January 2022

No incidents reported

7th January 2022

No incidents reported

6th January 2022

No incidents reported

5th January 2022

No incidents reported

4th January 2022

No incidents reported

3rd January 2022

Email: Germany German SMTP blocked by Microsoft

On January 3 2022 at 20:47 UTC Microsoft began blocking mail sent from to domains that use the Microsoft 365 email system.

Microsoft's own IP reputation and junk mail reporting systems indicate that there are no problems with so we've reached out to them for answers.

We'll update this post as soon as more information is available.

In the interim as a possible workaround customers may create a new mailbox on our US mail server and use that temporarily for their outgoing email authentication.

  • It's been over a week and we've seen no blocks of the new server IP by MIcrosoft, so we consider this to be resolved.

  • We informed Microsoft of our findings and the corrective action we've taken but we've still received no further communication from them.

    To work around this we've moved to a new IP address. Customers do not need to change any settings - the DNS change should propagate automatically within the hour.

    After the DNS change has propagated, customers should be able to send mail to email addresses that are hosted by Microsoft.

    We'll leave this incident open and will continue to monitor.

  • We've still not heard from Microsoft but we believe we've identified the activity that triggered the block and are taking action to mitigate it at this time.

    We'll notify Microsoft of the actions we're taking and continue to hold on for a response.

  • We're still awaiting a response from Microsoft and have reached out to them as a reminder.

  • 2nd January 2022

    No incidents reported