We have continued to monitor everything whilst completing internal work to ensure all systems have been returned to full functionality. We are confident that everything has returned to normal and the incident is fully resolved.

We will be following up with a full post mortem soon.

Normal service has been restored. All sites are online and functioning normally.

We will continue to monitor systems very closely for some time before declaring the incident fully resolved.

The deployment is taking much longer than expected. We've begun the process of switching to new infrastructure instead. Our engineers are still working on resolving this as quickly as possible.

A fix is being deployed for the root cause of the incident. This should take a further 30minutes to complete, at which point, we should be able to bring sites back online much faster than we have been able to.

We have determined a root cause for the incident and are working to understand and resolve the underlying problem.

Meanwhile sites are continuing to come back online and work on additional infrastructure is still underway.

Sites are continuing to come back online. Work to deploy additional infrastructure as a contingency is also continuing. We're bringing more engineers online to ensure we can continue to work on this as fast as possible.

Sites are continuing to come back online, and we're in the process of deploying additional infrastructure as a contingency should we need it. Our engineers are working as quickly as they can to resume normal service

Our fix has been implemented and sites are now starting to come back online in batches. Thanks for your patience

We're making progress, and still working on deploying configuration changes to resolve the ongoing database connection issues. We are temporarily placing a number of sites into maintenance mode to help bring them back online.

We've identified the cause of persistent database locks, and we've brought more engineers online who are working on deploying a change to our configuration to resolve the issue.

We've seen some small improvement and recovery as a result of mitigation work, but our DB cluster is still struggling. The team is still working on it and we'll continue to share updates as we make progress.

The team is still working hard on mitigating the issues we're experiencing with the database cluster. We'll continue to share updates here as we make progress

We're continuing to see high levels of load on one of our primary database clusters, and the team is working as quickly as they can to mitigate the issue.

We're continuing to investigate the cause of the intermittent issues impacting our database cluster. We'll update when we have more in the next 30 minutes.

We've identified a performance issue on one of our database clusters which is causing intermittent issues for some customers. The team is actively working on a fix