Incident History

This incident has been resolved.

This incident has been resolved.

Throughout this incident, customer applications, deployments, the Cloud CLI, and the API remained fully operational. The disruption was isolated entirely to the Cloud Control Panel.

This incident has been fully resolved. We sincerely apologise for the inconvenience caused by this internal routing issue.

We have identified affected users and our teams will be getting in touch to let you know how we will be rectifying the issue whilst this small number of database clusters were unavailable. There is no need to contact our Support team in advance.

If you are experiencing any further issues, please do contact our Support Team who are ready to assist you.

This incident has been resolved.

This incident has been resolved.

This incident has been resolved.

This incident has been resolved.

The configuration issue affecting FPM worker counts on larger compute sizes has been resolved. Monitoring confirms the fix is working as expected for new deployments.

We have identified all environments that were potentially impacted and are reaching out to those customers directly with details and next steps. If you have not been contacted, your environment was not affected.

If you were affected and want to apply the fix immediately, redeploying your application will pick up the corrected configuration. You can verify worker counts on your environment's Metrics page under the Web workers graph.

Thanks for your patience while we worked through this.

We are not seeing any remaining impacted resources.

This incident has been resolved.