%3CLINGO-SUB%20id%3D%22lingo-sub-1456395%22%20slang%3D%22en-US%22%3EExperiencing%20Alerting%20failure%20for%20Log%20Alerts%20-%2006%2F11%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1456395%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%20Thursday%2C%2011%20June%202020%2012%3A48%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%2F11%2C%2012%3A26%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2006%2F09%2C%2008%3A26%20UTC%20and%20that%20during%20the%202%20days%204%20hours%20that%20it%20took%20to%20resolve%20the%20issue%20some%20the%20of%20customers%20experienced%20missing%20alerts%20in%20azure%20portal%20globally.%3CBR%20%2F%3E%3CUL%3E%0A%20%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20one%20our%20back%20end%20services.%3C%2FLI%3E%0A%20%20%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%202%20days%204%20Hours%20-%2006%2F09%2C%2008%3A26%20UTC%20through%2006%2F11%2C%2012%3A26%20UTC%3CBR%20%2F%3E%3C%2FLI%3E%0A%3C%2FUL%3EWe%20understand%20that%20customers%20rely%20on%20Log%20Alerts%20as%20a%20critical%20service%20and%20apologize%20for%20any%20impact%20this%20incident%20caused.%3CBR%20%2F%3E-Syed%3CBR%20%2F%3E%3C%2FDIV%3E%3CHR%20style%3D%22border-top-color%3Alightgray%22%20%2F%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1456395%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ELog%20Alerts%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Thursday, 11 June 2020 12:48 UTC

We've confirmed that all systems are back to normal with no customer impact as of 06/11, 12:26 UTC. Our logs show the incident started on 06/09, 08:26 UTC and that during the 2 days 4 hours that it took to resolve the issue some the of customers experienced missing alerts in azure portal globally.
  • Root Cause: The failure was due to one our back end services.
  • Incident Timeline: 2 days 4 Hours - 06/09, 08:26 UTC through 06/11, 12:26 UTC
We understand that customers rely on Log Alerts as a critical service and apologize for any impact this incident caused.
-Syed