%3CLINGO-SUB%20id%3D%22lingo-sub-2116003%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Latency%20Issue%20in%20Azure%20Portal%20for%20Log%20Analytics%20-%2002%2F05%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2116003%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%20Friday%2C%2005%20February%202021%2021%3A32%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%2F05%2C%2021%3A16%20UTC.%20Our%20logs%20show%20that%20the%20incident%20started%20on%2002%2F05%2C%2020%3A51%20UTC%20and%20that%20during%20the%2025%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20some%20customers%20ingesting%20telemetry%20in%20West%20US%202%20region%20might%20have%20experienced%20intermittent%20data%20latency%2C%20data%20gaps%20and%20incorrect%20alert%20activation.%26nbsp%3B%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20issues%20with%20one%20of%20the%20backend%20services.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%2020%20minutes%20-%2002%2F05%2C%2020%3A51%20UTC%20through%2002%2F05%2C%2021%3A16%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-Saika%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-2116003%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20Log%20Analytics%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Friday, 05 February 2021 21:32 UTC

We've confirmed that all systems are back to normal with no customer impact as of 02/05, 21:16 UTC. Our logs show that the incident started on 02/05, 20:51 UTC and that during the 25 minutes that it took to resolve the issue some customers ingesting telemetry in West US 2 region might have experienced intermittent data latency, data gaps and incorrect alert activation. 
  • Root Cause: The failure was due to issues with one of the backend services.
  • Incident Timeline: 20 minutes - 02/05, 20:51 UTC through 02/05, 21:16 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.

-Saika