Final Update: Tuesday, 17 November 2015 18:21 UTC
We've confirmed that all systems are back to normal with no customer impact as of 11/17, 18:20 UTC. Our logs show the incident started on 11/17, 17:30 UTC and that during the 1 hour that it took to resolve the issue.
-Application Insights Service Delivery Team
We've confirmed that all systems are back to normal with no customer impact as of 11/17, 18:20 UTC. Our logs show the incident started on 11/17, 17:30 UTC and that during the 1 hour that it took to resolve the issue.
- Root Cause: The failure was due to errors talking to a dependent service.
- Lessons Learned: We are actively investigating the issue and working on a long term fix to avoid this in the future.
- Incident Timeline: 50 minutes - 11/17, 17:30 UTC through 11/17, 18:20 UTC
-Application Insights Service Delivery Team
Update: Tuesday, 17 November 2015 17:18 UTC
Root cause has been isolated to errors while calling into a dependent service which was impacting multiple data types. We have done mitigation steps to stop the issue from occuring. However, customers will continue to see latency above 2 hours during the time period of 11/17/2015 15:30 UTC to 11/17/2015 16:00. This data is actively being processed by our backlog processing.
Root cause has been isolated to errors while calling into a dependent service which was impacting multiple data types. We have done mitigation steps to stop the issue from occuring. However, customers will continue to see latency above 2 hours during the time period of 11/17/2015 15:30 UTC to 11/17/2015 16:00. This data is actively being processed by our backlog processing.
- Work Around: None
- Next Update: Before 11/17 21:30 UTC