Home
%3CLINGO-SUB%20id%3D%22lingo-sub-1103977%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Access%20Issue%20for%20Log%20Analytics%20in%20North%20Europe%20-%2001%2F13%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1103977%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%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%2013%20January%202020%2003%3A21%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%2F13%2C%2002%3A35%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2001%2F13%2C%2002%3A10%20UTC%20and%20that%20during%20the%2025%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20customers%20in%20North%20Europe%20may%20have%20experienced%20issues%20with%20data%20access%20from%20Azure%20Portal%2C%20query%20failures%20in%20Azure%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%20issues%20with%20one%20of%20the%20dependent%20services.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%2025%20minutes%20-%2001%2F13%2C%2002%3A10%20UTC%20through%2001%2F13%2C%2002%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%2013%20January%202020%2002%3A45%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20aware%20of%20issues%20within%20Log%20Analytics%20and%20are%20actively%20investigating.%20Some%20customers%20in%20North%20Europe%20Region%20may%20experience%20issues%20with%20data%20access%20from%20Azure%20Portal%20and%20query%20failures%20in%20Azure%20Log%20Analytics.%3CUL%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2001%2F13%2007%3A00%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%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1103977%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, 13 January 2020 03:21 UTC

We've confirmed that all systems are back to normal with no customer impact as of 01/13, 02:35 UTC. Our logs show the incident started on 01/13, 02:10 UTC and that during the 25 minutes that it took to resolve the issue customers in North Europe may have experienced issues with data access from Azure Portal, query failures in Azure Log Analytics and delayed or missed alerts in Log Search Alerts.
  • Root Cause: The failure was due to issues with one of the dependent services.
  • Incident Timeline: 25 minutes - 01/13, 02:10 UTC through 01/13, 02: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, 13 January 2020 02:45 UTC

We are aware of issues within Log Analytics and are actively investigating. Some customers in North Europe Region may experience issues with data access from Azure Portal and query failures in Azure Log Analytics.
  • Next Update: Before 01/13 07:00 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Jayadev