%3CLINGO-SUB%20id%3D%22lingo-sub-1198050%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Access%20Issue%20in%20Azure%20portal%20for%20Log%20Analytics%20-%2002%2F27%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1198050%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%2027%20February%202020%2011%3A35%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2002%2F27%2C%2010%3A00%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2002%2F27%2C%2008%3A57%20UTC%20and%20that%20during%20the%201%20hour%2003%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20some%20customers%20in%20Central%20US%20region%20might%20have%20experienced%20data%20access%20issue%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%2001%20Hours%20%26amp%3B%2003%20minutes%20-%2002%2F27%2C%2008%3A57%20UTC%20through%2002%2F27%2C%2010%3A00%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-Syed%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%2027%20February%202020%2010%3A08%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20aware%20of%20issues%20within%20Log%20Analytics%20and%20are%20actively%20investigating.%20Some%20customers%20in%20Central%20US%20may%20experience%20data%20access%20issue%20and%20failures%20when%20query%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%2002%2F27%2012%3A08%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3CBR%20%2F%3E-Syed%3C%2FDIV%3E%3CHR%20style%3D%22border-top-color%3Alightgray%22%20%2F%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CBR%20%2F%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1198050%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20Log%20Analytics%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Thursday, 27 February 2020 11:35 UTC

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

-Syed

Initial Update: Thursday, 27 February 2020 10:08 UTC

We are aware of issues within Log Analytics and are actively investigating. Some customers in Central US may experience data access issue and failures when query through API.
  • Work Around: none
  • Next Update: Before 02/27 12:08 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Syed