%3CLINGO-SUB%20id%3D%22lingo-sub-1666122%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Access%20Issue%20in%20Azure%20portal%20for%20Log%20Analytics%20-%2009%2F14%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1666122%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%20Monday%2C%2014%20September%202020%2020%3A28%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%209%2F14%2C%2019%3A59%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%209%2F14%2C%209%3A30%20UTC%20and%20that%20during%20the%2010%20hours%20and%2030%20minutes%20that%20it%20took%20to%20resolve%2C%20customers%20in%20the%20China%20region%20may%20have%20experienced%20data%20latency%20or%20data%20gaps%20that%20could%20have%20caused%20false%20or%20missed%20alerts.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20a%20service%20change%20that%20resulted%20in%20data%20being%20misrouted.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%2010%20Hours%20%26amp%3B%2030%20minutes%20-%209%2F14%2C%2009%3A30%20UTC%20through%209%2F14%2C%2019%3A59%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-Ian%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-1666122%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20Log%20Analytics%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Monday, 14 September 2020 20:28 UTC

We've confirmed that all systems are back to normal with no customer impact as of 9/14, 19:59 UTC. Our logs show the incident started on 9/14, 9:30 UTC and that during the 10 hours and 30 minutes that it took to resolve, customers in the Switzerland North region may have experienced data latency or data gaps that could have caused false or missed alerts.
  • Root Cause: The failure was due to a service change that resulted in data being misrouted.
  • Incident Timeline: 10 Hours & 30 minutes - 9/14, 09:30 UTC through 9/14, 19:59 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.

-Ian