%3CLINGO-SUB%20id%3D%22lingo-sub-1243010%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Access%20issue%20in%20Azure%20Portal%20for%20Many%20Data%20Types%20-%2003%2F20%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1243010%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%2020%20March%202020%2023%3A49%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%2F20%2C%2018%3A28%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2003%2F12%2C%2022%3A00%20UTC%20and%20that%20during%20the%207%20days%2C%2020%20hours%20and%2028%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20customers%20using%20Live%20Metrics%20Stream%20might%20have%20received%20partial%20data%20regarding%20their%20instances.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20a%20bad%20deployment%20with%20the%20service.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%207%20days%2C%2020%20Hours%20%26amp%3B%2028%20minutes%20-%2003%2F12%2C%2022%3A00%20UTC%20through%2003%2F20%2C%2018%3A28%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-Eric%20Singleton%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-1243010%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EApplication%20Insights%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Friday, 20 March 2020 23:49 UTC

We've confirmed that all systems are back to normal with no customer impact as of 03/20, 18:28 UTC. Our logs show the incident started on 03/12, 22:00 UTC and that during the 7 days, 20 hours and 28 minutes that it took to resolve the issue customers using Live Metrics Stream might have received partial data regarding their instances.
  • Root Cause: The failure was due to a bad deployment with the service.
  • Incident Timeline: 7 days, 20 Hours & 28 minutes - 03/12, 22:00 UTC through 03/20, 18:28 UTC
We understand that customers rely on Application Insights as a critical service and apologize for any impact this incident caused.

-Eric Singleton