Home
%3CLINGO-SUB%20id%3D%22lingo-sub-1100586%22%20slang%3D%22en-US%22%3EExperiencing%20Alerting%20failure%20for%20Log%20Search%20Alerts%20in%20Multiple%20Regions%20-%2001%2F10%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1100586%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%20Friday%2C%2010%20January%202020%2004%3A22%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2001%2F10%2C%2003%3A40%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2001%2F10%2C%2003%3A05%20UTC%20and%20that%20during%20the%2035%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20customers%20experienced%20issues%20with%20delayed%20or%20missed%20alerts%20in%20Log%20Search%20Alerts.%3CBR%20%2F%3E%3CUL%3E%0A%20%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20issue%20in%20one%20of%20our%20backend%20services.%26nbsp%3B%3C%2FLI%3E%0A%20%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%2035%20minutes%20-%2001%2F10%2C%2003%3A05%20UTC%20through%2001%2F10%2C%2003%3A35%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-Jayadev%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-1100586%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ELog%20Search%20Alerts%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Friday, 10 January 2020 04:22 UTC

We've confirmed that all systems are back to normal with no customer impact as of 01/10, 03:40 UTC. Our logs show the incident started on 01/10, 03:05 UTC and that during the 35 minutes that it took to resolve the issue customers experienced issues with delayed or missed alerts in Log Search Alerts.
  • Root Cause: The failure was due to issue in one of our backend services. 
  • Incident Timeline: 35 minutes - 01/10, 03:05 UTC through 01/10, 03:35 UTC
We understand that customers rely on Log Search Alerts as a critical service and apologize for any impact this incident caused.

-Jayadev