Final Update: Thursday, 06 August 2020 13:30 UTC
We've confirmed that all systems are back to normal with no customer impact as of 8/6, 13:00 UTC. Our logs show the incident started on 8/06, 10:00 UTC and that during the 3 hours that it took to resolve the issue customers could have experienced a delay in alerting.
We've confirmed that all systems are back to normal with no customer impact as of 8/6, 13:00 UTC. Our logs show the incident started on 8/06, 10:00 UTC and that during the 3 hours that it took to resolve the issue customers could have experienced a delay in alerting.
- Root Cause: The failure was due to some backend dependencies.
- Incident Timeline:3 Hours - 8/06, 10:00 UTC through 8/06, 13:00 UTC
-Eric Singleton
Published Aug 06, 2020
Version 1.0