%3CLINGO-SUB%20id%3D%22lingo-sub-1247721%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Access%20issues%20for%20Application%20Insights%20in%20East%20US%20Region%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1247721%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%20Monday%2C%2023%20March%202020%2020%3A50%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2003%2F23%2C%2019%3A50%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2003%2F23%2C%2018%3A35%20UTC%20and%20that%20during%20the%201%20hour%20and%2015%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20some%20customers%20in%20East%20US%20Region%20experienced%20issues%20with%20query%20failures%20and%20possible%20misfired%20alerts.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20issues%20with%20one%20of%20the%20backend%20services.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%201%20Hour%20%26amp%3B%2015%20minutes%20-%2003%2F23%2C%2018%3A35%20UTC%20through%2003%2F23%2C%2019%3A50%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-Jayadev%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%20Monday%2C%2023%20March%202020%2019%3A42%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20aware%20of%20issues%20within%20Application%20Insights%20and%20are%20actively%20investigating.%20Some%20customers%20may%20experience%20query%20failures%2C%20Issues%20with%20false%2Fincorrect%20alerts%20in%20East%20US%20region.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3EWork%20Around%3C%2FU%3E%3A%3CNONE%20details%3D%22%22%20or%3D%22%22%3E%3C%2FNONE%3E%3C%2FLI%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2003%2F24%2000%3A00%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3CBR%20%2F%3E-Jayadev%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-1247721%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EApplication%20Insights%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Monday, 23 March 2020 20:50 UTC

We've confirmed that all systems are back to normal with no customer impact as of 03/23, 19:50 UTC. Our logs show the incident started on 03/23, 18:35 UTC and that during the 1 hour and 15 minutes that it took to resolve the issue some customers in East US Region experienced issues with query failures and possible misfired alerts.
  • Root Cause: The failure was due to issues with one of the backend services.
  • Incident Timeline: 1 Hour & 15 minutes - 03/23, 18:35 UTC through 03/23, 19:50 UTC
We understand that customers rely on Application Insights as a critical service and apologize for any impact this incident caused.

-Jayadev

Initial Update: Monday, 23 March 2020 19:42 UTC

We are aware of issues within Application Insights and are actively investigating. Some customers may experience query failures, Issues with false/incorrect alerts in East US region.
  • Work Around:
  • Next Update: Before 03/24 00:00 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Jayadev