Home
%3CLINGO-SUB%20id%3D%22lingo-sub-574243%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Access%20issue%20in%20Azure%20Portal%20for%20Many%20Data%20Types%20-%2005%2F16%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-574243%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%2016%20May%202019%2010%3A12%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%2F16%2C%2009%3A55%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2005%2F16%2C%2000%3A55%20UTC%20and%20that%20during%20the%20~9%20hours%20that%20it%20took%20to%20resolve%20the%20issue%20some%20customers%20who%20have%20configured%20alerts%20prior%20to%2005%2F16%2C%2000%3A55%20UTC%26nbsp%3Bmight%20not%20have%20received%20alert%20fired%20or%20alert%20resolved%20events%20during%20the%20impacted%20window.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20configuration%20issues%20with%20one%20of%20our%20dependent%20service.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%209%20Hours%20-%2005%2F16%2C%2000%3A55%20UTC%20through%2005%2F16%2C%2009%3A55%20UTC%3CBR%20%2F%3E%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-Mohini%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%22%22%3E%3CU%20style%3D%22font-size%3A%2014px%3B%22%3EUpdate%3C%2FU%3E%3A%20Thursday%2C%2016%20May%202019%2008%3A59%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20continue%20to%20investigate%20issues%20within%20Application%20Insights.%20Some%20customers%20who%20configured%20alerts%20prior%20to%20the%20start%20time%20will%20not%20receive%20alert%20fired%20or%20alert%20resolved%20events%20during%20the%20impact%20window.%20The%20problem%20began%20at%2005%2F15%20~12%3A55%20UTC.%26nbsp%3B%3CBR%20%2F%3E%3CUL%20style%3D%22font-size%3A%2014px%3B%22%3E%3CLI%3E%3CU%3EWork%20Around%3C%2FU%3E%3A%20None%3C%2FLI%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2005%2F16%2010%3A00%20UTC%3C%2FLI%3E%3C%2FUL%3E-Mohini%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-574243%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EApplication%20Insights%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Thursday, 16 May 2019 10:12 UTC

We've confirmed that all systems are back to normal with no customer impact as of 05/16, 09:55 UTC. Our logs show the incident started on 05/16, 00:55 UTC and that during the ~9 hours that it took to resolve the issue some customers who have configured alerts prior to 05/16, 00:55 UTC might not have received alert fired or alert resolved events during the impacted window.
  • Root Cause: The failure was due to configuration issues with one of our dependent service.
  • Incident Timeline: 9 Hours - 05/16, 00:55 UTC through 05/16, 09:55 UTC
We understand that customers rely on Application Insights as a critical service and apologize for any impact this incident caused.

-Mohini

Update: Thursday, 16 May 2019 08:59 UTC

We continue to investigate issues within Application Insights. Some customers who configured alerts prior to the start time will not receive alert fired or alert resolved events during the impact window. The problem began at 05/15 ~12:55 UTC. 
  • Work Around: None
  • Next Update: Before 05/16 10:00 UTC
-Mohini