%3CLINGO-SUB%20id%3D%22lingo-sub-1210829%22%20slang%3D%22en-US%22%3EExperiencing%20Alerting%20failure%20for%20Log%20Search%20Alerts%20-%2003%2F05%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1210829%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%2005%20March%202020%2008%3A57%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%2F05%2C%2008%3A30%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2003%2F05%2C%2007%3A30%20UTC%20and%20that%20during%20the%201%20hour%20that%20it%20took%20to%20resolve%20the%20issue%20some%20of%20customers%20may%20have%20experienced%20missed%20or%20delayed%20alerts%20in%20North%20Central%20US%20Region.%3CBR%20%2F%3E%3CUL%3E%0A%20%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20one%20of%20the%20back%20end%20services.%26nbsp%3B%3C%2FLI%3E%0A%20%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%201%20Hour%20-%2003%2F05%2C%2007%3A30%20UTC%20through%2003%2F05%2C%2008%3A30%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-Satya%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-1210829%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ELog%20Search%20Alerts%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Thursday, 05 March 2020 08:57 UTC

We've confirmed that all systems are back to normal with no customer impact as of 03/05, 08:30 UTC. Our logs show the incident started on 03/05, 07:30 UTC and that during the 1 hour that it took to resolve the issue some of customers may have experienced missed or delayed alerts in North Central US Region.
  • Root Cause: The failure was due to one of the back end services. 
  • Incident Timeline: 1 Hour - 03/05, 07:30 UTC through 03/05, 08:30 UTC
We understand that customers rely on Log Search Alerts as a critical service and apologize for any impact this incident caused.

-Satya