Issue impacting Aura instance operations

All fixes have been deployed and issue is now marked as resolved.

All identified instances have been fix, continuing to monitor. Contact customer support for any further issues.

We are continuing to monitor for any further issues.

We are continuing to monitor the situation closely for any further issues.

We are continuing to monitor the situation closely for any further issues.

We are continuing to monitor for any further issues.

We are continuing to monitor for any further issues.

We continue to fix a small subset of Free instances that are still impacted.

We addressed the issue in all AuraDB Professional instances. Aura Free can still be affected. We will continue to monitor and fix the remaining databases.

We continue to fix a small subset of instances that are still impacted under the AuraDB Professional and Free tiers.

We continue to fix a subset of instances that are still impacted for AuraDB Professional and Free

We continue to resolve the subset of instances that are still impacted for AuraDB Professional and Free

We continue to resolve the subset of instances that are still impacted for AuraDB Professional and Free.

We continue to resolve the subset of instances which are still impacted for AuraDB Professional and Free.

AuraDB Virtual Dedicated Cloud and AuraDB Business Critical should all now be fixed. We continue to resolve the subset of instances which are still impacted for AuraDB Professional and Free.

We continue to resolve the subset of instances which are still impacted.

We continue to resolve the subset of instances which are still impacted.

We are continuing to resolve the subset of instances still impacted.

We are continuing to resolve the subset of instances still impacted.

We are continuing to resolve the subset of instances still impacted.

With the configuration fix deployed, we are continuing to resolve the subset of instances still impacted.

We have deployed a configuration fix and are now working to resolve the subset of instances impacted.

We have identified the subset of instances impacted and continue to deploy the fix at this time.

We are deploying the first part of the fix and continue actively working on rolling out the full solution. We expect an ETA in the order of 1hour from now.

We have identified the cause of the current issue and are actively working on the fix currently.

We are working with engineering teams and continuing to make progress with the investigations at the current time.

We are working with engineering teams and making progress with the investigations at the current time.

We are currently investigating an issue at this time.