Home
%3CLINGO-SUB%20id%3D%22lingo-sub-868679%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Gaps%20issue%20in%20Azure%20Portal%20for%20Many%20Data%20Types%20-%2009%2F21%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-868679%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%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CU%3EFinal%20Update%3C%2FU%3E%3A%20Saturday%2C%2021%20September%202019%2012%3A35%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2009%2F21%2C%2010%3A36%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2009%2F21%2C%2010%3A08%20UTC%26nbsp%3Band%20that%20during%20the%2028%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20some%20customers%20using%20non-retrying%20SDK's%20in%20SouthEast%20Asia%20region%20could%20have%20experienced%20data%20gaps%20while%20accessing%20their%20data.%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%20services%20responsible%20for%20ingesting%20data.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%2028%20minutes%20-%2009%2F21%2C%2010%3A08%20UTC%26nbsp%3Bthrough%2009%2F21%2C%2010%3A36%20UTC%3CBR%20%2F%3E%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-Varun%3CBR%20%2F%3E%3C%2FDIV%3E%3CHR%20style%3D%22border-top-color%3Alightgray%22%20%2F%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-868679%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EApplication%20Insights%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Saturday, 21 September 2019 12:35 UTC

We've confirmed that all systems are back to normal with no customer impact as of 09/21, 10:36 UTC. Our logs show the incident started on 09/21, 10:08 UTC and that during the 28 minutes that it took to resolve the issue some customers using non-retrying SDK's in SouthEast Asia region could have experienced data gaps while accessing their data.
  • Root Cause: The failure was due to an issue in one of our services responsible for ingesting data.
  • Incident Timeline: 28 minutes - 09/21, 10:08 UTC through 09/21, 10:36 UTC
We understand that customers rely on Application Insights as a critical service and apologize for any impact this incident caused.

-Varun