%3CLINGO-SUB%20id%3D%22lingo-sub-1504239%22%20slang%3D%22en-US%22%3EExperiencing%20alerting%20failure%20for%20Log%20Search%20Alerts%20-%2007%2F03%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1504239%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%20Saturday%2C%2004%20July%202020%2000%3A16%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%207%2F4%2C%2001%3A11%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%207%2F4%2C%2000%3A16%20UTC%20and%20that%20during%20the%2055%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20100%25%20of%20customers%20in%20the%20West%20Central%20US%20region%20experienced%20possible%20alert%20misfires%20and%2For%20missing%20alerts.%3CBR%20%2F%3E%3CUL%3E%0A%20%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20an%20outage%20in%20the%20back-end%20compute%20systems%20that%20support%20Log%20Search%20Alerts.%3C%2FLI%3E%0A%20%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%2055%20minutes%20-%207%2F4%2C%2000%3A16%20UTC%20through%207%2F4%2C%2001%3A11%20UTC%3CBR%20%2F%3E%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-Jack%20Cantwell%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%20Friday%2C%2003%20July%202020%2023%3A45%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20aware%20of%20issues%20within%20Log%20Search%20Alerts%20and%20are%20actively%20investigating.%20Some%20customers%20may%20experience%20missing%20or%20mis-fired%20alerts.%3CUL%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2007%2F04%2001%3A00%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3C%2FDIV%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CBR%20%2F%3E-Jack%20Cantwell%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-1504239%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ELog%20Search%20Alerts%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Saturday, 04 July 2020 00:16 UTC

We've confirmed that all systems are back to normal with no customer impact as of 7/4, 01:11 UTC. Our logs show the incident started on 7/4, 00:16 UTC and that during the 55 minutes that it took to resolve the issue 100% of customers in the West Central US region experienced possible alert misfires and/or missing alerts.
  • Root Cause: The failure was due to an outage in the back-end compute systems that support Log Search Alerts.
  • Incident Timeline: 55 minutes - 7/4, 00:16 UTC through 7/4, 01:11 UTC
We understand that customers rely on Log Search Alerts as a critical service and apologize for any impact this incident caused.

-Jack Cantwell

Initial Update: Friday, 03 July 2020 23:45 UTC

We are aware of issues within Log Search Alerts and are actively investigating. Some customers may experience missing or mis-fired alerts.
  • Next Update: Before 07/04 01:00 UTC
We are working hard to resolve this issue and apologize for any inconvenience.

-Jack Cantwell