%3CLINGO-SUB%20id%3D%22lingo-sub-1408686%22%20slang%3D%22en-US%22%3EAlerting%20failure%20issue%20for%20Smart%20Alerts%20in%20Azure%20Portal%20in%20multiple%20regions%20-%2005%2F21%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1408686%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%20Thursday%2C%2021%20May%202020%2014%3A56%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%205%2F21%2C%2013%3A15%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%205%2F21%2C%2012%3A15%20UTC%20and%20that%20during%20the%201%20hour%20that%20it%20took%20to%20resolve%20the%20issue%20some%20of%20customers%20may%20have%20experienced%20Delayed%20or%20Missed%20smart%20alerts%20issues%20in%20multiple%20regions.%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%20dependent%20services.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%201%20Hour%20-%205%2F21%2C%2012%3A15%20UTC%20through%205%2F21%2C%2013%3A15%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-Madhuri%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%20Thursday%2C%2021%20May%202020%2013%3A47%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20aware%20of%20issues%20within%20Application%20Insights%20and%20are%20actively%20investigating.%20Some%20customers%20may%20experience%20Delayed%20or%20missed%20smart%20alerts%20issues%26nbsp%3Bin%20multiple%20regions.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3EWork%20Around%3C%2FU%3E%3A%20None.%26nbsp%3B%3C%2FLI%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2005%2F21%2016%3A00%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3CBR%20%2F%3E-Madhuri%3C%2FDIV%3E%3CHR%20style%3D%22border-top-color%3Alightgray%22%20%2F%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CBR%20%2F%3E%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-1408686%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EApplication%20Insights%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Thursday, 21 May 2020 14:56 UTC

We've confirmed that all systems are back to normal with no customer impact as of 5/21, 13:15 UTC. Our logs show the incident started on 5/21, 12:15 UTC and that during the 1 hour that it took to resolve the issue some of customers may have experienced Delayed or Missed smart alerts issues in multiple regions.
  • Root Cause: The failure was due to an issue in one of our dependent services.
  • Incident Timeline: 1 Hour - 5/21, 12:15 UTC through 5/21, 13:15 UTC
We understand that customers rely on Application Insights as a critical service and apologize for any impact this incident caused.

-Madhuri

Initial Update: Thursday, 21 May 2020 13:47 UTC

We are aware of issues within Application Insights and are actively investigating. Some customers may experience Delayed or missed smart alerts issues in multiple regions.
  • Work Around: None. 
  • Next Update: Before 05/21 16:00 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Madhuri