This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Tech Community.
Final Update: Thursday, 03 February 2022 08:16 UTC
We've confirmed that all systems are back to normal with no customer impact as of 02/03, 05:30 UTC. Our logs show the incident started on 02/02, 23:30 UTC and that during the 6 hours that it took to resolve the issue, some customers may have experienced issues with delayed alerts globally.
-Srikanth
We've confirmed that all systems are back to normal with no customer impact as of 02/03, 05:30 UTC. Our logs show the incident started on 02/02, 23:30 UTC and that during the 6 hours that it took to resolve the issue, some customers may have experienced issues with delayed alerts globally.
- Root Cause: The failure was due to one of our backend service.
- Incident Timeline: 6 hours - 02/02, 23:30 UTC through 02/03, 05:30 UTC
-Srikanth