%3CLINGO-SUB%20id%3D%22lingo-sub-1569906%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Access%20Issue%20in%20Azure%20portal%20for%20Log%20Analytics%20-%2008%2F06%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1569906%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%2006%20August%202020%2006%3A26%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%208%2F6%2C%2006%3A03%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%208%2F05%2C%2021%3A41%20UTC%20and%20that%20during%20the%208%20hours%2022%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%2C%20customers%20using%20the%20AUDIT_LOG_REST_API%20in%20the%20Australia%20Southeast%20Region%20could%20have%20experienced%20a%20delay%20with%20ingested%20data.%3C%2FDIV%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20a%20bad%20deployment.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%208%20Hours%20%26amp%3B%2022%20minutes%20-%208%2F05%2C%2021%3A41%20UTC%20through%208%2F06%2C%2006%3A03%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-Eric%20Singleton%3CBR%20%2F%3E%3C%2FDIV%3E%3CHR%20style%3D%22border-top-color%3Alightgray%22%20%2F%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1569906%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20Log%20Analytics%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Thursday, 06 August 2020 06:26 UTC

We've confirmed that all systems are back to normal with no customer impact as of 8/6, 06:03 UTC. Our logs show the incident started on 8/05, 21:41 UTC and that during the 8 hours 22 minutes that it took to resolve the issue, customers using the AUDIT_LOG_REST_API in the Australia Southeast Region could have experienced a delay with ingested data.

  • Root Cause: The failure was due to a bad deployment.
  • Incident Timeline: 8 Hours & 22 minutes - 8/05, 21:41 UTC through 8/06, 06:03 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.

-Eric Singleton