Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Home
- :
- Azure
- :
- Azure Monitor Status
- :
- Experiencing Latency and Data Loss issue in Azure Portal for Many Data Types - 03/26 - Resolved
Mar 26 2020
07:48 AM
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Email to a Friend
- Printer Friendly Page
- Report Inappropriate Content
Mar 26 2020
07:48 AM
Final Update: Friday, 26 March 2020 22:47 UTC
Issue started happening again after about an hour. We can now confirm that all systems are back to normal with no customer impact as of 03/26, 20:00 UTC. Our logs show that the incident started on 03/26, 12:30 UTC and during the 7 hours and 30 minutes that it took to resolve the issue some customers using Application Insights in East US region may have experienced intermittent data latency, data gaps and incorrect alert activation.
-Jayadev
Issue started happening again after about an hour. We can now confirm that all systems are back to normal with no customer impact as of 03/26, 20:00 UTC. Our logs show that the incident started on 03/26, 12:30 UTC and during the 7 hours and 30 minutes that it took to resolve the issue some customers using Application Insights in East US region may have experienced intermittent data latency, data gaps and incorrect alert activation.
- Root Cause: The failure was due to an issue in one of our dependent services.
- Incident Timeline: 7 Hours 30 minutes - 03/26, 12:30 UTC through 03/26, 20:00 UTC
-Jayadev
Update: Thursday, 26 March 2020 14:38 UTC
We've confirmed that all systems are back to normal with no customer impact as of 03/26, 14:20 UTC. Our logs show that the incident started on 03/26, 12:30 UTC and that during the 1 hours and 50 minutes that it took to resolve the issue some customers in East US region may have experienced intermittent data latency, data gaps and incorrect alert activation.
-Anmol
We've confirmed that all systems are back to normal with no customer impact as of 03/26, 14:20 UTC. Our logs show that the incident started on 03/26, 12:30 UTC and that during the 1 hours and 50 minutes that it took to resolve the issue some customers in East US region may have experienced intermittent data latency, data gaps and incorrect alert activation.
- Root Cause: The failure was due to an issue in one of our dependent services.
- Incident Timeline: 1 hour 50 minutes - 03/26, 12:30 UTC through 03/26, 14:20 UTC
-Anmol
- Tags:
- Application Insights
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.