%3CLINGO-SUB%20id%3D%22lingo-sub-942490%22%20slang%3D%22en-US%22%3EExperiencing%20Alerting%20failure%20for%20Log%20Search%20Alerts%20in%20West%20Europe%20region%20-%2010%2F24%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-942490%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%20Thursday%2C%2024%20October%202019%2010%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%2010%2F24%2C%2010%3A26%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2010%2F24%2C%2006%3A26%20UTC%20and%20that%20during%20the%204%20hours%20that%20it%20took%20to%20resolve%20the%20issue%20~10%25%20of%20customers%20from%20West%20Europe%20region%20may%20have%20experienced%20failures%20while%20performing%20log%20search%20operations%20and%20possible%20missed%20alerts%20for%20resources%20hosted%20in%20this%20region.%3CBR%20%2F%3E%3CUL%3E%0A%20%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20issue%20with%20one%20of%20our%20dependent%20service.%3C%2FLI%3E%0A%20%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%204%20Hours%26nbsp%3B%20-%2010%2F24%2C%2006%3A26%20UTC%20through%2010%2F24%2C%2010%3A26%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-Mohini%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%20Thursday%2C%2024%20October%202019%2007%3A40%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%20alerting%20failure%20in%20West%20Europe%20region.%3CBR%20%2F%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%2010%2F24%2011%3A00%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3CBR%20%2F%3E-Rama%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-942490%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ELog%20Search%20Alerts%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Thursday, 24 October 2019 10:22 UTC

We've confirmed that all systems are back to normal with no customer impact as of 10/24, 10:26 UTC. Our logs show the incident started on 10/24, 06:26 UTC and that during the 4 hours that it took to resolve the issue ~10% of customers from West Europe region may have experienced failures while performing log search operations and possible missed alerts for resources hosted in this region.
  • Root Cause: The failure was due to issue with one of our dependent service.
  • Incident Timeline: 4 Hours  - 10/24, 06:26 UTC through 10/24, 10:26 UTC
We understand that customers rely on Log Search Alerts as a critical service and apologize for any impact this incident caused.

-Mohini

Initial Update: Thursday, 24 October 2019 07:40 UTC

We are aware of issues within Log Search Alerts and are actively investigating. Some customers may experience alerting failure in West Europe region.
  • Work Around: None
  • Next Update: Before 10/24 11:00 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Rama