%3CLINGO-SUB%20id%3D%22lingo-sub-353899%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Access%20issue%20for%20Many%20Data%20Types%20for%20Log%20Analytics%20in%20SUK%20-%2002%2F20%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-353899%22%20slang%3D%22en-US%22%3E%3CDIV%20style%3D%22font-size%3A%2014px%3B%22%3E%0A%3CDIV%20style%3D%22font-size%3A%2014px%3B%22%3E%3CFONT%20face%3D%22%26quot%3BHelvetica%20Neue%26quot%3B%2CHelvetica%2CArial%2Csans-serif%22%3EFinal%20Update%3A%20Monday%2C%2018%20February%202019%2016%3A07%20UTC%3C%2FFONT%3E%3C%2FDIV%3E%0A%3CDIV%20style%3D%22font-size%3A%2014px%3B%22%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2002%2F18%2C%2013%3A57%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2002%2F18%2C%2013%3A11%20UTC%20and%20that%20during%20the%2046%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%2C%205%25%20of%20customers%20in%20SUK%20may%20have%20experienced%20data%20access%20and%20data%20latency%20issues.%3CBR%20%2F%3E%3CUL%3E%0A%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20issue%20with%20one%20of%20our%20backend%20service.%3C%2FLI%3E%0A%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%2046%20minutes%20-%2002%2F18%2C%2013%3A11%20UTC%20through%2002%2F18%2C%2013%3A57%20UTC%3C%2FLI%3E%0A%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%3C%2FDIV%3E%0A%3CDIV%3E%3CHR%20%2F%3E%3C%2FDIV%3E%0A%3CDIV%3E%3CFONT%20face%3D%22%26quot%3BHelvetica%20Neue%26quot%3B%2CHelvetica%2CArial%2Csans-serif%22%3EInitial%20Update%3A%20Monday%2C%2018%20February%202019%2014%3A21%20UTC%3C%2FFONT%3E%3C%2FDIV%3E%0A%3CDIV%20style%3D%22font-size%3A%2014px%3B%22%3E%3CBR%20%2F%3EWe%20are%20aware%20of%20issues%20within%20Log%20Analytics%20and%20are%20actively%20investigating.%20Some%20customers%20in%20SUK%20may%20experience%20Data%20Access%20issues.%3C%2FDIV%3E%0A%3CDIV%20style%3D%22font-size%3A%2014px%3B%22%3E%0A%3CUL%3E%0A%3CLI%3E%3CU%3EWork%20Around%3C%2FU%3E%3A%20None%3C%2FLI%3E%0A%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%26nbsp%3BBefore%2002%2F18%2015%3A30%20UTC%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3C%2FDIV%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3CBR%20%2F%3E-Naresh%3CHR%20%2F%3E%0A%3CDIV%20style%3D%22font-size%3A%2014px%3B%22%3E%26nbsp%3B%3C%2FDIV%3E%0A%3CHR%20%2F%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-353899%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EApplication%20Insights%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Monday, 18 February 2019 16:07 UTC

We've confirmed that all systems are back to normal with no customer impact as of 02/18, 13:57 UTC. Our logs show the incident started on 02/18, 13:11 UTC and that during the 46 minutes that it took to resolve the issue, 5% of customers in SUK may have experienced data access and data latency issues.
  • Root Cause: The failure was due to issue with one of our backend service.
  • Incident Timeline: 46 minutes - 02/18, 13:11 UTC through 02/18, 13:57 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: Monday, 18 February 2019 14:21 UTC

We are aware of issues within Log Analytics and are actively investigating. Some customers in SUK may experience Data Access issues.
  • Work Around: None
  • Next Update: Before 02/18 15:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Naresh