%3CLINGO-SUB%20id%3D%22lingo-sub-1298477%22%20slang%3D%22en-US%22%3EExperiencing%20Latency%20and%20Data%20Loss%20issue%20in%20Azure%20Portal%20for%20Many%20Data%20Types%20-%2004%2F10%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1298477%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%2010%20April%202020%2016%3A38%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%204%2F10%2C%2015%3A29%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%204%2F10%2C%2015%3A01%20UTC%20and%20that%20during%20the%2028%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%2C%20customers%20may%20have%20experienced%20data%20latency%20and%20data%20loss%20for%20Application%20Insights%20resources%20in%20West%20Europe.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20a%20back%20end%20service%20that%20became%20unhealthy.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%2028%20minutes%20-%204%2F10%2C%2015%3A01%20UTC%20through%204%2F10%2C%2015%3A29%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20understand%20that%20customers%20rely%20on%20Application%20Insights%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-1298477%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EApplication%20Insights%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Friday, 10 April 2020 16:38 UTC

We've confirmed that all systems are back to normal with no customer impact as of 4/10, 15:29 UTC. Our logs show the incident started on 4/10, 15:01 UTC and that during the 28 minutes that it took to resolve the issue, customers may have experienced data latency and data loss for Application Insights resources in West Europe.
  • Root Cause: The failure was due to a back end service that became unhealthy.
  • Incident Timeline: 28 minutes - 4/10, 15:01 UTC through 4/10, 15:29 UTC
We understand that customers rely on Application Insights as a critical service and apologize for any impact this incident caused.

-Ian