Home
%3CLINGO-SUB%20id%3D%22lingo-sub-567236%22%20slang%3D%22en-US%22%3EExperiencing%20issues%20with%20Application%20Insights%20service%20to%20send%20alert%20notifications%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-567236%22%20slang%3D%22en-US%22%3E%3CDIV%20style%3D%22font-size%3A%2014px%3B%22%3E%0A%3CDIV%20style%3D%22font-size%3A%2014px%3B%22%3E%3CU%3EFinal%20Update%3C%2FU%3E%3A%20Wednesday%2C%2015%20May%202019%2004%3A24%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20running%20as%20expected%20since%20issue%20has%20been%20mitigated.%20Our%20logs%20show%20the%20issue%20started%20on%2005%2F02%2019%3A30%20UTC%20and%20ended%20by%2005%2F15%2001%3A08%20UTC.%20During%20the%20duration%20of%20the%20issue%20up%20to%2010%25%20of%20alert%20notifications%20for%20Classic%20Alerts%20for%20Application%20Insights%20customers%20might%20not%20have%20delivered.%20We%20understand%20the%20issue%20completely%20and%20additional%20steps%20have%20been%20taken%20to%20assure%20that%20we%20do%20not%20see%20similar%20occurrence%20in%20future.%3CBR%20%2F%3E%3CUL%3E%0A%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20root%20cause%20has%20been%20isolated%20to%20a%20single%20service%20instance%20which%20was%20not%20serving%20the%20traffic%20as%20expected.%3C%2FLI%3E%0A%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%2005%2F02%2019%3A30%20UTC%20through%2005%2F15%2001%3A08%20UTC%3C%2FLI%3E%0A%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%3C%2FDIV%3E%0A%3CHR%20%2F%3E%0A%3CDIV%20style%3D%22font-size%3A%2014px%3B%22%3E%0A%3CDIV%20style%3D%22font-size%3A%2014px%3B%22%3E%3CU%3EInitial%20Update%3C%2FU%3E%3A%20Wednesday%2C%2015%20May%202019%2000%3A01%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%20notifications%20not%20being%20delivered.%3C%2FDIV%3E%0A%3CDIV%20style%3D%22font-size%3A%2014px%3B%22%3E%26nbsp%3B%3C%2FDIV%3E%0A%3CDIV%20style%3D%22font-size%3A%2014px%3B%22%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3C%2FDIV%3E%0A%3CDIV%20style%3D%22font-size%3A%2014px%3B%22%3E%3CBR%20%2F%3E-Jayadev%3C%2FDIV%3E%0A%3CHR%20%2F%3E%3C%2FDIV%3E%0A%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-567236%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EApplication%20Insights%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Wednesday, 15 May 2019 04:24 UTC

We've confirmed that all systems are running as expected since issue has been mitigated. Our logs show the issue started on 05/02 19:30 UTC and ended by 05/15 01:08 UTC. During the duration of the issue up to 10% of alert notifications for Classic Alerts for Application Insights customers might not have delivered. We understand the issue completely and additional steps have been taken to assure that we do not see similar occurrence in future.
  • Root Cause: The root cause has been isolated to a single service instance which was not serving the traffic as expected.
  • Incident Timeline: 05/02 19:30 UTC through 05/15 01:08 UTC
We understand that customers rely on Application Insights as a critical service and apologize for any impact this incident caused.

-Jayadev

Initial Update: Wednesday, 15 May 2019 00:01 UTC

We are aware of issues within Application Insights and are actively investigating. Some customers may experience issues with notifications not being delivered.
 
We are working hard to resolve this issue and apologize for any inconvenience.

-Jayadev