Final Update: Monday, 13 June 2022 23:04 UTC
We've confirmed that all systems are back to normal with no customer impact as of 6/13, 22:15 UTC. Our logs show the incident started on 6/13, 21:00 UTC and that during the 1 hour that it took to resolve the issue 100% of customers experienced data loss when publishing logs to their Log Analytics workspace
-Srikanth
We've confirmed that all systems are back to normal with no customer impact as of 6/13, 22:15 UTC. Our logs show the incident started on 6/13, 21:00 UTC and that during the 1 hour that it took to resolve the issue 100% of customers experienced data loss when publishing logs to their Log Analytics workspace
- Root Cause: The failure was due to a configuration change which was rolled back.
- Incident Timeline: 1 Hours & 15 minutes - 6/13, 21:00 UTC through 6/13, 22:15 UTC
-Srikanth
Final Update: Monday, 13 June 2022 23:04 UTC
We've confirmed that all systems are back to normal with no customer impact as of 6/13, 22:15 UTC. Our logs show the incident started on 6/13, 21:00 UTC and that during the 1 hour that it took to resolve the issue 100% of customers experienced data loss when publishing logs to their Log Analytics workspace
-Robin Paul
We've confirmed that all systems are back to normal with no customer impact as of 6/13, 22:15 UTC. Our logs show the incident started on 6/13, 21:00 UTC and that during the 1 hour that it took to resolve the issue 100% of customers experienced data loss when publishing logs to their Log Analytics workspace
- Root Cause: The failure was due to a configuration change which was rolled back.
- Incident Timeline: 1 Hours & 15 minutes - 6/13, 21:00 UTC through 6/13, 22:15 UTC
-Robin Paul
Updated Jun 14, 2022
Version 2.0