Home
%3CLINGO-SUB%20id%3D%22lingo-sub-1091823%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Access%20Issue%20in%20Azure%20portal%20for%20Log%20Analytics%20-%2001%2F06%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1091823%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%2009%3A25%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%2008%3A48%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2001%2F06%2C%2007%3A00%20UTC%20and%20that%20during%20the%201%20hours%2048%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%202.4%20%25%20of%20customers%20in%20West%20Europe%20region%20experienced%20data%20access%20issue%20in%20the%20Azure%20portal%20and%20failures%20when%20queried%20through%20API.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20an%20issue%20with%20one%20of%20our%20dependent%20service.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%201%20Hours%20%26amp%3B%2048%20minutes%20-%2001%2F06%2C%2007%3A00%20UTC%20through%2001%2F06%2C%2008%3A48%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-Monish%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%2007%3A51%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%20data%20access%20issue%20in%20the%20Azure%20portal%20and%20failure%20when%20queried%20through%20API..%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3EWork%20Around%3C%2FU%3E%3A%20None%3C%2FLI%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2001%2F06%2011%3A00%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3CBR%20%2F%3E-Monish%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-1091823%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20Log%20Analytics%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Monday, 06 January 2020 09:25 UTC

We've confirmed that all systems are back to normal with no customer impact as of 01/06, 08:48 UTC. Our logs show the incident started on 01/06, 07:00 UTC and that during the 1 hours 48 minutes that it took to resolve the issue 2.4 % of customers in West Europe region experienced data access issue in the Azure portal and failures when queried through API.
  • Root Cause: The failure was due to an issue with one of our dependent service.
  • Incident Timeline: 1 Hours & 48 minutes - 01/06, 07:00 UTC through 01/06, 08:48 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.

-Monish

Initial Update: Monday, 06 January 2020 07:51 UTC

We are aware of issues within Log Analytics and are actively investigating. Some customers in West Europe may experience data access issue in the Azure portal and failure when queried through API..
  • Work Around: None
  • Next Update: Before 01/06 11:00 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Monish