%3CLINGO-SUB%20id%3D%22lingo-sub-1279588%22%20slang%3D%22en-US%22%3EExperiencing%20Latency%20and%20Data%20Loss%20issues%20for%20Application%20Insights%20in%20East%20US%20-%2004%2F03%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1279588%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%2003%20April%202020%2017%3A57%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2004%2F03%2C%2017%3A15%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2004%2F03%2C%2016%3A29%20UTC%20and%20that%20during%20the%2046%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20some%20customers%20in%20East%20US%20Region%20may%20have%20experienced%20intermittent%20data%20latency%2C%20data%20gaps%20and%20incorrect%20alert%20activation.%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%20the%20backend%20services.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A46%20minutes%20-%2004%2F03%2C%2016%3A29%20UTC%20through%2004%2F03%2C%2017%3A15%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-Jayadev%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-1279588%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EApplication%20Insights%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Friday, 03 April 2020 17:57 UTC

We've confirmed that all systems are back to normal with no customer impact as of 04/03, 17:15 UTC. Our logs show the incident started on 04/03, 16:29 UTC and that during the 46 minutes that it took to resolve the issue some customers in East US Region may have experienced intermittent data latency, data gaps and incorrect alert activation.
  • Root Cause: The failure was due to an issue in one of the backend services.
  • Incident Timeline:46 minutes - 04/03, 16:29 UTC through 04/03, 17:15 UTC
We understand that customers rely on Application Insights as a critical service and apologize for any impact this incident caused.

-Jayadev