Final Update: Friday, 22 January 2016 22:52 UTC
We've confirmed that all systems are back to normal with no customer impact as of 1/22, 22:45 UTC. Our logs show the incident started on 1/22, 19:55 UTC and that during the 2 hours 50 minutes that it took to resolve the issue customers experienced latency outside of the 2 hour SLA.
We've confirmed that all systems are back to normal with no customer impact as of 1/22, 22:45 UTC. Our logs show the incident started on 1/22, 19:55 UTC and that during the 2 hours 50 minutes that it took to resolve the issue customers experienced latency outside of the 2 hour SLA.
- Root Cause: The failure was due to a deployment issue.
- Incident Timeline: 2 Hours & 50 minutes - 1/22, 19:55 UTC through 1/22, 22:45 UTC
-Application Insights Service Delivery Team
Update: Friday, 22 January 2016 21:53 UTC
Root cause has been isolated to an issue within one of our backend services which was impacting which is causing periods of latency over 2 hours. Current data is no longer latent. To address this issue we have re-deployed our backend service. Current data for multiple data types is now working as expected. Some customers may experience period of data over 2 hours latency and we estimate 3 before all data is no longer latent.
Root cause has been isolated to an issue within one of our backend services which was impacting which is causing periods of latency over 2 hours. Current data is no longer latent. To address this issue we have re-deployed our backend service. Current data for multiple data types is now working as expected. Some customers may experience period of data over 2 hours latency and we estimate 3 before all data is no longer latent.
- Next Update: Before 01/23 02:00 UTC