%3CLINGO-SUB%20id%3D%22lingo-sub-965568%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Access%20issue%20in%20Application%20Insights%20-%2010%2F30%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-965568%22%20slang%3D%22en-US%22%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CU%3EFinal%20Update%3C%2FU%3E%3A%20Wednesday%2C%2030%20October%202019%2015%3A32%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2010%2F30%2C%2013%3A52%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2010%2F30%2C%2010%3A17%20UTC%20and%20that%20during%20the%203%20hours%20%26amp%3B%2035%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20some%20of%20customers%20might%20have%20experienced%20issues%20with%20Data%20Access%20and%20connecting%20to%20resources%20hosted%20in%20West%20Europe%20region.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20an%20issue%20in%20one%20of%20our%20backend%20service.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%203%20Hours%20%26amp%3B%2035%20minutes%20-%2010%2F30%2C%2010%3A17%20UTC%20through%2010%2F30%2C%2013%3A52%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20understand%20that%20customers%20rely%20on%20Application%20Insights%20as%20a%20critical%20service%20and%20apologize%20for%20any%20impact%20this%20incident%20caused.%3CBR%20%2F%3E%3CBR%20%2F%3E-Naresh%3CBR%20%2F%3E%3C%2FDIV%3E%3CHR%20style%3D%22border-top-color%3Alightgray%22%20%2F%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CU%3EInitial%20Update%3C%2FU%3E%3A%20Wednesday%2C%2030%20October%202019%2013%3A00%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20aware%20of%20issues%20within%20Application%20Insights%20and%20are%20actively%20investigating.%20Some%20customers%20may%20experience%20issues%20with%26nbsp%3B%20Data%20Access%20in%20West%20Europe%20region.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3EWork%20Around%3C%2FU%3E%3A%20None%3C%2FLI%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2010%2F30%2017%3A00%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3CBR%20%2F%3E-Naresh%3C%2FDIV%3E%3CHR%20style%3D%22border-top-color%3Alightgray%22%20%2F%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-965568%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EApplication%20Insights%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Wednesday, 30 October 2019 15:32 UTC

We've confirmed that all systems are back to normal with no customer impact as of 10/30, 13:52 UTC. Our logs show the incident started on 10/30, 10:17 UTC and that during the 3 hours & 35 minutes that it took to resolve the issue some of customers might have experienced issues with Data Access and connecting to resources hosted in West Europe region.
  • Root Cause: The failure was due to an issue in one of our backend service.
  • Incident Timeline: 3 Hours & 35 minutes - 10/30, 10:17 UTC through 10/30, 13:52 UTC
We understand that customers rely on Application Insights as a critical service and apologize for any impact this incident caused.

-Naresh

Initial Update: Wednesday, 30 October 2019 13:00 UTC

We are aware of issues within Application Insights and are actively investigating. Some customers may experience issues with  Data Access in West Europe region.
  • Work Around: None
  • Next Update: Before 10/30 17:00 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Naresh