Home
%3CLINGO-SUB%20id%3D%22lingo-sub-1092627%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Access%20Issue%20in%20Azure%20portal%20for%20Log%20Analytics%20in%20East%20US%20-%2001%2F06%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1092627%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%2006%20January%202020%2018%3A53%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2001%2F06%2C%2018%3A35%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2001%2F06%2C16%3A26%20UTC%20and%20that%20during%20the%202%20hours%20and%209%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20some%20customers%20in%20East%20US%20Region%20experienced%20issues%20with%20data%20access%20in%20the%20Azure%20portal%2C%20query%20failures%20for%20Log%20Analytics%20and%20alerting%20failures%20for%20Log%20Search%20Alerts.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20issue%20with%20one%20of%20the%20dependent%20services.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%202%20Hours%20%26amp%3B%209%20minutes%20-%2001%2F06%2C%2016%3A26%20UTC%20through%2001%2F06%2C%2018%3A35%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20understand%20that%20customers%20rely%20on%20Azure%20Log%20Analytics%20as%20a%20critical%20service%20and%20apologize%20for%20any%20impact%20this%20incident%20caused.%3CBR%20%2F%3E%3CBR%20%2F%3E-Jayadev%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%22font-size%3A14px%3B%22%3E%3CU%3EInitial%20Update%3C%2FU%3E%3A%20Monday%2C%2006%20January%202020%2017%3A09%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20aware%20of%20issues%20within%20Log%20Analytics%20and%20are%20actively%20investigating.%20Some%20customers%20in%20East%20US%20Region%20may%20experience%20data%20access%20issue%20in%20Azure%20Portal%2C%20query%20failures%20in%20Log%20Analytics%20and%20alerting%20failures%20for%20Log%20Search%20Alerts.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3EWork%20Around%3C%2FU%3E%3A%3CNONE%20details%3D%22%22%20or%3D%22%22%3E%3C%2FNONE%3E%3C%2FLI%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2001%2F06%2021%3A30%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3CBR%20%2F%3E-Jayadev%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-1092627%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20Log%20Analytics%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ELog%20Search%20Alerts%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Monday, 06 January 2020 18:53 UTC

We've confirmed that all systems are back to normal with no customer impact as of 01/06, 18:35 UTC. Our logs show the incident started on 01/06,16:26 UTC and that during the 2 hours and 9 minutes that it took to resolve the issue some customers in East US Region experienced issues with data access in the Azure portal, query failures for Log Analytics and alerting failures for Log Search Alerts.
  • Root Cause: The failure was due to issue with one of the dependent services.
  • Incident Timeline: 2 Hours & 9 minutes - 01/06, 16:26 UTC through 01/06, 18:35 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.

-Jayadev

Initial Update: Monday, 06 January 2020 17:09 UTC

We are aware of issues within Log Analytics and are actively investigating. Some customers in East US Region may experience data access issue in Azure Portal, query failures in Log Analytics and alerting failures for Log Search Alerts.
  • Work Around:
  • Next Update: Before 01/06 21:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Jayadev