%3CLINGO-SUB%20id%3D%22lingo-sub-1692030%22%20slang%3D%22en-US%22%3EExperiencing%20Alerting%20failure%20Issue%20in%20Azure%20portal%20for%20Log%20Search%20Alerts%20-%2009%2F21%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1692030%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%22%22%3E%3CU%20style%3D%22font-size%3A%2014px%3B%22%3EFinal%20Update%3C%2FU%3E%3A%20Monday%2C%2021%20September%202020%2014%3A37%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2009%2F21%2C%2014%3A37%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2009%2F21%2C%2012%3A55%20UTC%20and%20that%20during%20the%201%20hour%20and%205%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20some%20customers%20may%20have%20experienced%20missed%20or%20delayed%20Log%20Search%20alerts%20in%20Australia%20Southeast%20region.%3C%2FDIV%3E%3CDIV%20style%3D%22%22%3E%3CBR%20%2F%3E%3CUL%20style%3D%22font-size%3A%2014px%3B%22%3E%0A%20%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20issue%20in%20one%20of%20our%20dependent%20service.%3C%2FLI%3E%0A%20%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%201%20Hours%20%26amp%3B%205%20minutes%20-%209%2F21%2C%2012%3A55%20UTC%20through%209%2F21%2C%2014%3A00%20UTC%3C%2FLI%3E%0A%3C%2FUL%3EWe%20understand%20that%20customers%20rely%20on%20Log%20Search%20Alerts%20as%20a%20critical%20service%20and%20apologize%20for%20any%20impact%20this%20incident%20caused.%3CBR%20%2F%3E%3CBR%20%2F%3E-Sandeep%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-1692030%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ELog%20Search%20Alerts%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Monday, 21 September 2020 14:37 UTC

We've confirmed that all systems are back to normal with no customer impact as of 09/21, 14:37 UTC. Our logs show the incident started on 09/21, 12:55 UTC and that during the 1 hour and 5 minutes that it took to resolve the issue some customers may have experienced missed or delayed Log Search alerts in Australia Southeast region.

  • Root Cause: The failure was due to issue in one of our dependent service.
  • Incident Timeline: 1 Hours & 5 minutes - 9/21, 12:55 UTC through 9/21, 14:00 UTC
We understand that customers rely on Log Search Alerts as a critical service and apologize for any impact this incident caused.

-Sandeep