%3CLINGO-SUB%20id%3D%22lingo-sub-1237375%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Latency%20and%20Data%20gap%20Issue%20in%20Azure%20portal%20for%20Log%20Analytics%20-%2003%2F19%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1237375%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%2019%20March%202020%2008%3A30%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2003%2F19%2C%2006%3A00%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2003%2F19%2C%2006%3A20%20UTC%20and%20that%20during%20the%2020%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20some%20customers%20may%20have%20experienced%20intermittent%20data%20access%2C%20data%20gaps%2C%20data%20latency%20and%20incorrect%20alert%20activation%20issues%20in%20West%20US2%20region.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20an%20issue%20in%20one%20of%20our%20dependent%20services.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%2020%20minutes%20-%2003%2F19%2C%2006%3A00%20UTC%20through%2003%2F19%2C%2006%3A20%26nbsp%3BUTC%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-Madhuri%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-1237375%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20Log%20Analytics%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Thursday, 19 March 2020 08:30 UTC

We've confirmed that all systems are back to normal with no customer impact as of 03/19, 06:00 UTC. Our logs show the incident started on 03/19, 06:20 UTC and that during the 20 minutes that it took to resolve the issue some customers may have experienced intermittent data access, data gaps, data latency and incorrect alert activation issues in West US2 region.
  • Root Cause: The failure was due to an issue in one of our dependent services.
  • Incident Timeline: 20 minutes - 03/19, 06:00 UTC through 03/19, 06:20 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.

-Madhuri