Home
%3CLINGO-SUB%20id%3D%22lingo-sub-1099763%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Access%20Issue%20for%20Log%20Analytics%20in%20West%20Europe%20-%2001%2F09%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1099763%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%2009%20January%202020%2020%3A13%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%2F09%2C%2019%3A18%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2001%2F09%2C%2018%3A30%20UTC%20and%20that%20during%20the%2048%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20some%20customers%20in%20West%20Europe%20may%20experienced%20issues%20with%20data%20access%20in%20Azure%20portal%2C%20Query%20failures%20for%20Log%20Analytics%20and%20delayed%20or%20missed%20alerts%20in%20Log%20Search%20Alerts.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20issue%20in%20one%20of%20the%20backend%20services.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%26nbsp%3B%2046%20minutes%20-%2001%2F09%2C%2018%3A30%20UTC%20through%2001%2F09%2C%2019%3A18%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%20Thursday%2C%2009%20January%202020%2019%3A14%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20aware%20of%20issues%20within%20Log%20Analytics%20and%20are%20actively%20investigating.%20Some%20customers%20in%20West%20Europe%20may%20experience%20issues%20with%20data%20access%20from%20portal%20or%20query%20failures%20in%20Azure%20Log%20Analytics.%3CUL%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2001%2F09%2023%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-1099763%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: Thursday, 09 January 2020 20:13 UTC

We've confirmed that all systems are back to normal with no customer impact as of 01/09, 19:18 UTC. Our logs show the incident started on 01/09, 18:30 UTC and that during the 48 minutes that it took to resolve the issue some customers in West Europe may experienced issues with data access in Azure portal, Query failures for Log Analytics and delayed or missed alerts in Log Search Alerts.
  • Root Cause: The failure was due to issue in one of the backend services.
  • Incident Timeline:  46 minutes - 01/09, 18:30 UTC through 01/09, 19:18 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: Thursday, 09 January 2020 19:14 UTC

We are aware of issues within Log Analytics and are actively investigating. Some customers in West Europe may experience issues with data access from portal or query failures in Azure Log Analytics.
  • Next Update: Before 01/09 23:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Jayadev