Final Update: Thursday, 06 August 2020 06:26 UTC
We've confirmed that all systems are back to normal with no customer impact as of 8/6, 06:03 UTC. Our logs show the incident started on 8/05, 21:41 UTC and that during the 8 hours 22 minutes that it took to resolve the issue, customers using the AUDIT_LOG_REST_API in the Australia Southeast Region could have experienced a delay with ingested data.
We've confirmed that all systems are back to normal with no customer impact as of 8/6, 06:03 UTC. Our logs show the incident started on 8/05, 21:41 UTC and that during the 8 hours 22 minutes that it took to resolve the issue, customers using the AUDIT_LOG_REST_API in the Australia Southeast Region could have experienced a delay with ingested data.
- Root Cause: The failure was due to a bad deployment.
- Incident Timeline: 8 Hours & 22 minutes - 8/05, 21:41 UTC through 8/06, 06:03 UTC
-Eric Singleton
Published Aug 06, 2020
Version 1.0