%3CLINGO-SUB%20id%3D%22lingo-sub-2117464%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Access%20issue%20in%20Azure%20Portal%20for%20Many%20Data%20Types%20-%2002%2F08%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2117464%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%20Monday%2C%2008%20February%202021%2010%3A46%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2002%2F08%2C%2009%3A00%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2002%2F08%2C%2008%3A00%20UTC%20and%20that%20during%20the%201%20hour%20that%20it%20took%20to%20resolve%20the%20issue%20some%20customers%20may%20experience%20data%20access%20issue%20and%20issues%20with%20missed%20or%20delayed%20Log%20Search%20alerts%20in%20East%20US%20region%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20issue%20in%20one%20of%20our%20backend%20service.%26nbsp%3B%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%201%20Hour%20-%2002%2F08%2C%2008%3A00%20UTC%20through%2002%2F08%2C%2009%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-Deepika%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%3CDIV%20style%3D%22%22%3E%3CU%20style%3D%22font-size%3A%2014px%3B%22%3EInitial%20Update%3C%2FU%3E%3A%20Monday%2C%2008%20February%202021%2009%3A06%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20aware%20of%20issues%20within%20Application%20Insights%20and%26nbsp%3B%20Azure%20Log%20Analytics%20and%20are%20actively%20investigating.%20Some%20customers%20may%20experience%20data%20access%20issue%20and%20issues%20with%20missed%20or%20delayed%20Log%20Search%20alerts%20in%20East%20US%20region%3CUL%20style%3D%22font-size%3A%2014px%3B%22%3E%3CLI%3E%3CU%3EWork%20Around%3C%2FU%3E%3A%20NA%3C%2FLI%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2002%2F08%2012%3A30%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3CBR%20%2F%3E-Deepika%3C%2FDIV%3E%3CHR%20style%3D%22font-size%3A%2014px%3B%20border-top-color%3A%20lightgray%3B%22%20%2F%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2117464%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EApplication%20Insights%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EAzure%20Log%20Analytics%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Monday, 08 February 2021 10:46 UTC

We've confirmed that all systems are back to normal with no customer impact as of 02/08, 09:00 UTC. Our logs show the incident started on 02/08, 08:00 UTC and that during the 1 hour that it took to resolve the issue some customers may experience data access issue and issues with missed or delayed Log Search alerts in East US region
  • Root Cause: The failure was due to issue in one of our backend service. 
  • Incident Timeline: 1 Hour - 02/08, 08:00 UTC through 02/08, 09:00 UTC
We understand that customers rely on Application Insights as a critical service and apologize for any impact this incident caused.

-Deepika

Initial Update: Monday, 08 February 2021 09:06 UTC

We are aware of issues within Application Insights and  Azure Log Analytics and are actively investigating. Some customers may experience data access issue and issues with missed or delayed Log Search alerts in East US region
  • Work Around: NA
  • Next Update: Before 02/08 12:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Deepika