Home
%3CLINGO-SUB%20id%3D%22lingo-sub-584005%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Gaps%20issue%20in%20Azure%20Portal%20for%20Many%20Data%20Types%20-%2005%2F17%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-584005%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%2017%20May%202019%2022%3A02%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%205%2F17%2C%2021%3A26%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%205%2F16%2C%2021%3A53%20UTC%20and%20that%20during%20the%2023%20hours%2027%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%203%25%20of%20customers%20ingesting%20data%20with%20non-retrying%20SDK's%20in%20USGov%20Virginia%20region%20might%20have%20experienced%20data%20loss.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20identified%20due%20to%20a%20stuck%20node%20that%20needed%20restart.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%2023%20Hours%20%26amp%3B%2027%20minutes%20-%205%2F16%2C%2021%3A53%20UTC%20through%205%2F17%2C%2021%3A26%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%3CBR%20%2F%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-584005%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EApplication%20Insights%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Friday, 17 May 2019 22:02 UTC

We've confirmed that all systems are back to normal with no customer impact as of 5/17, 21:26 UTC. Our logs show the incident started on 5/16, 21:53 UTC and that during the 23 hours 27 minutes that it took to resolve the issue 3% of customers ingesting data with non-retrying SDK's in USGov Virginia region might have experienced data loss.
  • Root Cause: The failure was identified due to a stuck node that needed restart.
  • Incident Timeline: 23 Hours & 27 minutes - 5/16, 21:53 UTC through 5/17, 21:26 UTC
We understand that customers rely on Application Insights as a critical service and apologize for any impact this incident caused.

-Jayadev