%3CLINGO-SUB%20id%3D%22lingo-sub-1464240%22%20slang%3D%22en-US%22%3EExperiencing%20intermittent%20issue%20querying%20Azure%20Monitor%20Activity%20Logs%20-%2006%2F15%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1464240%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%20Monday%2C%2015%20June%202020%2019%3A26%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2006%2F15%2C%2016%3A00%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2006%2F14%2C%2017%3A00%20UTC%20and%20that%20during%20the%2023%20hours%20that%20it%20took%20to%20resolve%20the%20issue%20some%20small%20subset%20of%20customers%20experienced%20intermittent%20issues%20when%20querying%20Activity%20Logs%20in%20the%20Azure%20Portal.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20one%20of%20the%20dependent%20service%20failure%20.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%2023%20Hours%20%26amp%3B%200%20minutes%20-%2006%2F14%2C%2017%3A00%20UTC%20through%2006%2F15%2C%2016%3A00%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20understand%20that%20customers%20rely%20on%20Azure%20Monitor%26nbsp%3B%3CSPAN%20style%3D%22font-family%3A%20Helvetica%3B%22%3Eas%20a%20critical%20service%20and%20apologize%20for%20any%20impact%20this%20incident%20caused%3C%2FSPAN%3E%3CSPAN%20style%3D%22font-family%3A%20%26quot%3BSegoe%20UI%26quot%3B%2C%20system-ui%2C%20%26quot%3BApple%20Color%20Emoji%26quot%3B%2C%20%26quot%3BSegoe%20UI%20Emoji%26quot%3B%2C%20sans-serif%3B%22%3E.%3C%2FSPAN%3E%3CBR%20%2F%3E%3CBR%20%2F%3E-Subhash%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-1464240%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EApplication%20Insights%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Monday, 15 June 2020 19:26 UTC

We've confirmed that all systems are back to normal with no customer impact as of 06/15, 16:00 UTC. Our logs show the incident started on 06/14, 17:00 UTC and that during the 23 hours that it took to resolve the issue some small subset of customers experienced intermittent issues when querying Activity Logs in the Azure Portal.
  • Root Cause: The failure was due to one of the dependent service failure .
  • Incident Timeline: 23 Hours & 0 minutes - 06/14, 17:00 UTC through 06/15, 16:00 UTC
We understand that customers rely on Azure Monitor as a critical service and apologize for any impact this incident caused.

-Subhash