Home
%3CLINGO-SUB%20id%3D%22lingo-sub-531995%22%20slang%3D%22en-US%22%3EExperiencing%20Proactive%20Detection%20failure%20issue%20in%20Azure%20Portal-%2005%2F05%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-531995%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%20Sunday%2C%2005%20May%202019%2006%3A15%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2005%2F05%2C%2006%3A00%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2005%2F05%2C%2004%3A00%20UTC%20and%20that%20during%20the%202%20hours%20that%20it%20took%20to%20resolve%20the%20issue%20some%20of%20the%20customers%20in%20South%20Central%20US%20and%20East%20US%20experienced%20failure%20in%20Proactive%20Detection.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20the%20issues%20in%20one%20of%20our%20dependent%20services.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%202%20Hours%26nbsp%3B%20-%2005%2F05%2C%2004%3A00%20UTC%20through%2005%2F05%2C%2006%3A00%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-Monish%3CBR%20%2F%3E%3C%2FDIV%3E%3CHR%20style%3D%22border-top-color%3Alightgray%22%20%2F%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-531995%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EApplication%20Insights%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Sunday, 05 May 2019 06:15 UTC

We've confirmed that all systems are back to normal with no customer impact as of 05/05, 06:00 UTC. Our logs show the incident started on 05/05, 04:00 UTC and that during the 2 hours that it took to resolve the issue some of the customers in South Central US and East US experienced failure in Proactive Detection.
  • Root Cause: The failure was due to the issues in one of our dependent services.
  • Incident Timeline: 2 Hours  - 05/05, 04:00 UTC through 05/05, 06:00 UTC
We understand that customers rely on Application Insights as a critical service and apologize for any impact this incident caused.

-Monish