This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Tech Community.
Final Update: Sunday, 26 April 2020 15:09 UTC
We've confirmed that all systems are back to normal with no customer impact as of 04/26, 14:10 UTC. Our logs show the incident started on 04/26, 12:35 UTC and that during the 1 hours and 35 minutes that it took to resolve the issue some customers may have experienced ingestion delays or alerting failure issues in Central US region.
-Madhuri
We've confirmed that all systems are back to normal with no customer impact as of 04/26, 14:10 UTC. Our logs show the incident started on 04/26, 12:35 UTC and that during the 1 hours and 35 minutes that it took to resolve the issue some customers may have experienced ingestion delays or alerting failure issues in Central US region.
- Root Cause: The failure was due to an issue in one of our dependent services.
- Incident Timeline: 1 Hours & 35 minutes - 04/26, 12:35 UTC through 04/26, 14:10 UTC
-Madhuri