Home
%3CLINGO-SUB%20id%3D%22lingo-sub-810664%22%20slang%3D%22en-US%22%3EExperiencing%20Alerting%20failure%20for%20Log%20Search%20Alerts%20-%2008%2F19%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-810664%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%20Monday%2C%2019%20August%202019%2012%3A32%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2008%2F19%2C%2012%3A30%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2008%2F19%2C%2009%3A30%20UTC%20and%20that%20during%20the%203%20hours%20that%20it%20took%20to%20resolve%20the%20issue%20All%20customers%20using%20Log%20alerts%20which%20are%20configured%20in%20West%20Central%20US%20region%20might%20have%20experienced%20Alerting%20failure%20issues.%3CBR%20%2F%3E%3CUL%3E%0A%20%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20issues%20in%20one%20of%20our%20backend%20services.%3C%2FLI%3E%0A%20%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%203%20Hours%20-%208%2F19%2C%2009%3A30%20UTC%20through%208%2F19%2C%2012%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-Anmol%3CBR%20%2F%3E%3C%2FDIV%3E%3CHR%20style%3D%22border-top-color%3Alightgray%22%20%2F%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CU%3EInitial%20Update%3C%2FU%3E%3A%20Monday%2C%2019%20August%202019%2011%3A36%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20aware%20of%20issues%20within%20Log%20Search%20Alerts%20and%20are%20actively%20investigating.%20Some%20customers%20in%20West%20Central%20US%20region%20may%20experience%20intermittent%20alerting%20failures.%3C%2FDIV%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CUL%3E%3CLI%3E%3CU%3EWork%20Around%3C%2FU%3E%3A%20None%3C%2FLI%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2008%2F19%2014%3A00%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3CBR%20%2F%3E-Anmol%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-810664%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ELog%20Search%20Alerts%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Monday, 19 August 2019 12:32 UTC

We've confirmed that all systems are back to normal with no customer impact as of 08/19, 12:30 UTC. Our logs show the incident started on 08/19, 09:30 UTC and that during the 3 hours that it took to resolve the issue All customers using Log alerts which are configured in West Central US region might have experienced Alerting failure issues.
  • Root Cause: The failure was due to issues in one of our backend services.
  • Incident Timeline: 3 Hours - 8/19, 09:30 UTC through 8/19, 12:30 UTC
We understand that customers rely on Log Search Alerts as a critical service and apologize for any impact this incident caused.

-Anmol

Initial Update: Monday, 19 August 2019 11:36 UTC

We are aware of issues within Log Search Alerts and are actively investigating. Some customers in West Central US region may experience intermittent alerting failures.
  • Work Around: None
  • Next Update: Before 08/19 14:00 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Anmol