%3CLINGO-SUB%20id%3D%22lingo-sub-770519%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Gaps%20issue%20in%20Azure%20Portal%20for%20Application%20Insights%20-%2007%2F23%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-770519%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%20Tuesday%2C%2023%20July%202019%2020%3A18%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3E%3CP%20class%3D%22MsoNormal%22%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2007%2F23%2C%2020%3A18%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2007%2F23%2C%2017%3A00%20UTC%20and%20that%20during%20the%201%20hour%20that%20it%20took%20to%20resolve%20the%20issue%20some%20customers%20in%20US%20gov%20region%20have%20experienced%20a%20gap%20in%20data%20of%20up%20to%2010%25%20of%20ingested%20metrics.%3C%2FP%3E%3CP%3E%3C%2FP%3E%3CP%3E%3C%2FP%3E%3CP%20class%3D%22MsoNormal%22%3ERoot%20Cause%3A%20The%20failure%20was%20due%20to%20an%20issue%20in%20one%20of%20our%20dependent%20services.%3C%2FP%3E%3CP%3E%3C%2FP%3E%3CP%3E%3C%2FP%3E%3CP%20class%3D%22MsoNormal%22%3EIncident%20Timeline%3A%201%20Hours%20%26amp%3B%200%20minutes%20-%2007%2F23%2C%2017%3A00%20UTC%20through%2007%2F23%2C%2018%3A00%20UTC%3C%2FP%3E%3CP%3E%3C%2FP%3E%3CP%3E%3C%2FP%3E%3CP%20class%3D%22MsoNormal%22%3EWe%20understand%20that%20customers%20rely%20on%20Application%20Insights%20as%20a%20critical%20service%20and%20apologize%20for%20any%20impact%20this%20incident%20caused.%3C%2FP%3E%3CP%3E%3C%2FP%3E%3CP%3E%3C%2FP%3E%3CP%20class%3D%22MsoNormal%22%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3C%2FP%3E%3CP%20class%3D%22MsoNormal%22%3E-Subhash%3C%2FP%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-770519%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EApplication%20Insights%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Tuesday, 23 July 2019 20:18 UTC

We've confirmed that all systems are back to normal with no customer impact as of 07/23, 20:18 UTC. Our logs show the incident started on 07/23, 17:00 UTC and that during the 1 hour that it took to resolve the issue some customers in US gov region have experienced a gap in data of up to 10% of ingested metrics.

Root Cause: The failure was due to an issue in one of our dependent services.

Incident Timeline: 1 Hours & 0 minutes - 07/23, 17:00 UTC through 07/23, 18:00 UTC

We understand that customers rely on Application Insights as a critical service and apologize for any impact this incident caused.

 

-Subhash