Home
%3CLINGO-SUB%20id%3D%22lingo-sub-571205%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Gaps%20issue%20in%20Azure%20Portal%20for%20Many%20Data%20Types%20-%2005%2F15%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-571205%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%20Wednesday%2C%2015%20May%202019%2019%3A33%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2003%2F15%2C%2008%3A45%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2003%2F15%2C%2008%3A30%20UTC%20and%20that%20during%2015%20mins%20that%20it%20took%20to%20resolve%20the%20issue%200.3%25%20request%20failing%20for%20the%20customers%20in%20West%20US%20region%20while%20sending%20telemetry%20data%20to%20our%20ingestion%20services%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20backend%20service%20entering%20in%20to%20an%20unhealthy%20state.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%2015%20minutes%20-%2003%2F15%2C%2008%3A30%20UTC%20through%2003%2F15%2C%2008%3A45%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-Deepesh%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-571205%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EApplication%20Insights%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Wednesday, 15 May 2019 19:33 UTC

We've confirmed that all systems are back to normal with no customer impact as of 03/15, 08:45 UTC. Our logs show the incident started on 03/15, 08:30 UTC and that during 15 mins that it took to resolve the issue 0.3% request failing for the customers in West US region while sending telemetry data to our ingestion services
  • Root Cause: The failure was due to backend service entering in to an unhealthy state.
  • Incident Timeline: 15 minutes - 03/15, 08:30 UTC through 03/15, 08:45 UTC
We understand that customers rely on Application Insights as a critical service and apologize for any impact this incident caused.

-Deepesh