Home
%3CLINGO-SUB%20id%3D%22lingo-sub-1091042%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Access%20Issue%20in%20Azure%20portal%20for%20Log%20Analytics%20-%2001%2F05%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1091042%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%3CU%3EFinal%20Update%3C%2FU%3E%3A%20Sunday%2C%2005%20January%202020%2004%3A37%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3E%3CDIV%20style%3D%22box-sizing%3A%20border-box%3B%20font-family%3A%20%26quot%3BSegoe%20UI%26quot%3B%2C%20%26quot%3BHelvetica%20Neue%26quot%3B%2C%20%26quot%3BApple%20Color%20Emoji%26quot%3B%2C%20%26quot%3BSegoe%20UI%20Emoji%26quot%3B%2C%20Helvetica%2C%20Arial%2C%20sans-serif%3B%20font-size%3A%2014px%3B%20font-style%3A%20normal%3B%20font-variant-ligatures%3A%20normal%3B%20font-variant-caps%3A%20normal%3B%20font-weight%3A%20400%3B%20letter-spacing%3A%20normal%3B%20orphans%3A%202%3B%20text-align%3A%20start%3B%20text-indent%3A%200px%3B%20text-transform%3A%20none%3B%20white-space%3A%20normal%3B%20widows%3A%202%3B%20word-spacing%3A%200px%3B%22%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2001%2F05%2C%2002%3A00%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2001%2F05%2C%2000%3A30%20UTC%20and%20that%20during%20the%201%20hour%20and%2030%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20some%20customers%20in%20Australia%20South%20East%20experienced%20issues%20with%20alerts%20being%20delayed%20or%20experienced%20difficulties%20accessing%20data%20for%20resources%20hosted%20in%20the%20region.%3C%2FDIV%3E%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%20the%20backend%20services.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%201%20Hours%20%26amp%3B%2030%20minutes%20-%2001%2F05%2C%2000%3A30%20UTC%20through%2001%2F05%2C%2002%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-chandar%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%20Sunday%2C%2005%20January%202020%2001%3A38%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20aware%20of%20issues%20within%20Log%20Analytics%20and%20are%20actively%20investigating.%20Some%20customers%20may%20experience%20issues%20with%20data%20access%20and%20Log%20Analytics%20queries%20in%20Australia%20south%20East%20Region%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3EWork%20Around%3C%2FU%3E%3A%3CNONE%20details%3D%22%22%20or%3D%22%22%3E%3C%2FNONE%3E%3C%2FLI%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2001%2F05%2006%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%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1091042%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: Sunday, 05 January 2020 04:37 UTC

We've confirmed that all systems are back to normal with no customer impact as of 01/05, 02:00 UTC. Our logs show the incident started on 01/05, 00:30 UTC and that during the 1 hour and 30 minutes that it took to resolve the issue some customers in Australia South East experienced issues with alerts being delayed or experienced difficulties accessing data for resources hosted in the region.

  • Root Cause: The failure was due to an issue with one of the backend services.
  • Incident Timeline: 1 Hours & 30 minutes - 01/05, 00:30 UTC through 01/05, 02:00 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.

-chandar

Initial Update: Sunday, 05 January 2020 01:38 UTC

We are aware of issues within Log Analytics and are actively investigating. Some customers may experience issues with data access and Log Analytics queries in Australia south East Region
  • Work Around:
  • Next Update: Before 01/05 06:00 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Jayadev