Home
%3CLINGO-SUB%20id%3D%22lingo-sub-378056%22%20slang%3D%22en-US%22%3EExperiencing%20Alerting%20failure%20issue%20in%20Azure%20Portal%20for%20Many%20Data%20Types%20-%2003%2F21%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-378056%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%20March%202019%2005%3A05%20UTC%3C%2FDIV%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CBR%20%2F%3E%3C%2FDIV%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%203%2F21%2C%2002%3A24%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%203%2F21%2C%2002%3A38%20UTC%20and%20that%20during%20the%2014%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20customers%20would%20have%20experienced%20misfiring%20alerts.%3C%2FDIV%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CBR%20%2F%3ERoot%20Cause%3A%20The%20failure%20was%20due%20to%20a%20short%20internal%20downstream%20service%20availability%20problem%3CBR%20%2F%3EIncident%20Timeline%3A%2014%20minutes%20-%203%2F21%2C%2002%3A24%20UTC%20through%203%2F21%2C%2002%3A38%20UTC%3C%2FDIV%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CBR%20%2F%3EWe%20understand%20that%20customers%20rely%20on%20Application%20Insights%20as%20a%20critical%20service%20and%20apologize%20for%20any%20impact%20this%20incident%20caused.%3C%2FDIV%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E-Jeff%20Miller%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-378056%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EApplication%20Insights%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Thursday, 21 March 2019 05:05 UTC

We've confirmed that all systems are back to normal with no customer impact as of 3/21, 02:24 UTC. Our logs show the incident started on 3/21, 02:38 UTC and that during the 14 minutes that it took to resolve the issue customers would have experienced misfiring alerts.

Root Cause: The failure was due to a short internal downstream service availability problem
Incident Timeline: 14 minutes - 3/21, 02:24 UTC through 3/21, 02:38 UTC

We understand that customers rely on Application Insights as a critical service and apologize for any impact this incident caused.
-Jeff Miller