Resolved -
All fixes have been deployed and issue is now marked as resolved.
Jul 24, 15:56 UTC
Update -
All identified instances have been fix, continuing to monitor. Contact customer support for any further issues.
Jul 24, 12:59 UTC
Update -
We are continuing to monitor for any further issues.
Jul 24, 08:30 UTC
Update -
We are continuing to monitor the situation closely for any further issues.
Jul 24, 06:00 UTC
Update -
We are continuing to monitor the situation closely for any further issues.
Jul 24, 02:56 UTC
Update -
We are continuing to monitor for any further issues.
Jul 24, 01:02 UTC
Update -
We are continuing to monitor for any further issues.
Jul 23, 22:28 UTC
Update -
We continue to fix a small subset of Free instances that are still impacted.
Jul 23, 19:39 UTC
Update -
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.
Jul 23, 18:07 UTC
Update -
We continue to fix a small subset of instances that are still impacted under the AuraDB Professional and Free tiers.
Jul 23, 17:31 UTC
Update -
We continue to fix a subset of instances that are still impacted for AuraDB Professional and Free
Jul 23, 17:01 UTC
Update -
We continue to resolve the subset of instances that are still impacted for AuraDB Professional and Free
Jul 23, 16:32 UTC
Update -
We continue to resolve the subset of instances that are still impacted for AuraDB Professional and Free.
Jul 23, 15:57 UTC
Update -
We continue to resolve the subset of instances which are still impacted for AuraDB Professional and Free.
Jul 23, 15:29 UTC
Update -
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.
Jul 23, 15:03 UTC
Monitoring -
We continue to resolve the subset of instances which are still impacted.
Jul 23, 14:44 UTC
Update -
We continue to resolve the subset of instances which are still impacted.
Jul 23, 14:27 UTC
Update -
We are continuing to resolve the subset of instances still impacted.
Jul 23, 14:07 UTC
Update -
We are continuing to resolve the subset of instances still impacted.
Jul 23, 13:35 UTC
Update -
We are continuing to resolve the subset of instances still impacted.
Jul 23, 13:09 UTC
Update -
With the configuration fix deployed, we are continuing to resolve the subset of instances still impacted.
Jul 23, 12:49 UTC
Update -
We have deployed a configuration fix and are now working to resolve the subset of instances impacted.
Jul 23, 12:32 UTC
Update -
We have identified the subset of instances impacted and continue to deploy the fix at this time.
Jul 23, 12:11 UTC
Update -
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.
Jul 23, 11:53 UTC
Identified -
We have identified the cause of the current issue and are actively working on the fix currently.
Jul 23, 11:38 UTC
Update -
We are working with engineering teams and continuing to make progress with the investigations at the current time.
Jul 23, 11:24 UTC
Update -
We are working with engineering teams and making progress with the investigations at the current time.
Jul 23, 11:08 UTC
Investigating -
We are currently investigating an issue at this time.
Jul 23, 10:52 UTC