%3CLINGO-SUB%20id%3D%22lingo-sub-928609%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Access%20Issue%20in%20Azure%20portal%20for%20Azure%20Monitor%20-%2010%2F22%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-928609%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%20Tuesday%2C%2022%20October%202019%2022%3A54%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2010%2F22%2C%2022%3A25%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2010%2F22%2C%2022%3A00%20UTC%20and%20during%20the%2025%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%2C%20affected%20Azure%20Monitor%20customers%20in%20all%20regions%20could%20have%20experienced%20issues%20accessing%20data%20through%20the%20Azure%20portal%2C%20API%2C%20or%20received%20an%20incorrect%20or%20latent%20alert.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20a%20misconfiguration%20in%20a%20backend%20service%20which%20engineers%20reverted.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%200%20Hours%20%26amp%3B%2025%20minutes%20-%2010%2F22%2C%2022%3A00%20UTC%20through%2010%2F22%2C%2022%3A25%20UTC%3CBR%20%2F%3E%3C%2FLI%3E%3C%2FUL%3EWe%20understand%20that%20customers%20rely%20on%20Azure%20monitor%20as%20a%20critical%20service%20and%20apologize%20for%20any%20impact%20this%20incident%20caused.%3CBR%20%2F%3E%3CBR%20%2F%3E-Matt%3CBR%20%2F%3E%3C%2FDIV%3E%3CBR%20%2F%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-928609%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20Log%20Analytics%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Tuesday, 22 October 2019 22:54 UTC

We've confirmed that all systems are back to normal with no customer impact as of 10/22, 22:25 UTC. Our logs show the incident started on 10/22, 22:00 UTC and during the 25 minutes that it took to resolve the issue, affected Azure Monitor customers in all regions could have experienced issues accessing data through the Azure portal, API, or received an incorrect or latent alert.
  • Root Cause: The failure was due to a misconfiguration in a backend service which engineers reverted.
  • Incident Timeline: 0 Hours & 25 minutes - 10/22, 22:00 UTC through 10/22, 22:25 UTC
We understand that customers rely on Azure monitor as a critical service and apologize for any impact this incident caused.

-Matt