Home
%3CLINGO-SUB%20id%3D%22lingo-sub-776083%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Access%20Issue%20in%20Azure%20portal%20for%20Log%20Analytics%20-%2007%2F27%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-776083%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%20Saturday%2C%2027%20July%202019%2010%3A38%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2007%2F27%2C%2009%3A45%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2007%2F27%2C%2008%3A00%20UTC%20and%20that%20during%20the%201%20hour%2045%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20some%20of%20customers%20experienced%20data%20access%20issues.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20issues%20with%20one%20of%20our%20backend%20services%20which%20went%20in%20to%20unhealthy%20state.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%201%20Hour%20%26amp%3B%2045%20minutes%20-%2007%2F27%2C%2008%3A00%20UTC%20through%2007%2F27%2C%2009%3A45%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-naresh%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%20Saturday%2C%2027%20July%202019%2010%3A03%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20aware%20of%20issues%20within%20Log%20Analytics%20and%20are%20actively%20investigating.%20Some%20customers%20may%20experience%20issue%20using%20Log%20Analytics%20in%20West%20Europe%20region.%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%2007%2F27%2011%3A30%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3CBR%20%2F%3E-Naresh%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-776083%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: Saturday, 27 July 2019 10:38 UTC

We've confirmed that all systems are back to normal with no customer impact as of 07/27, 09:45 UTC. Our logs show the incident started on 07/27, 08:00 UTC and that during the 1 hour 45 minutes that it took to resolve the issue some of customers experienced data access issues.
  • Root Cause: The failure was due to issues with one of our backend services which went in to unhealthy state.
  • Incident Timeline: 1 Hour & 45 minutes - 07/27, 08:00 UTC through 07/27, 09:45 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.

-naresh

Initial Update: Saturday, 27 July 2019 10:03 UTC

We are aware of issues within Log Analytics and are actively investigating. Some customers may experience issue using Log Analytics in West Europe region.
  • Work Around: None.
  • Next Update: Before 07/27 11:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Naresh