%3CLINGO-SUB%20id%3D%22lingo-sub-1864967%22%20slang%3D%22en-US%22%3EExperienced%20Data%20Latency%20Issue%20for%20Log%20Search%20Alerts%20in%20West%20Europe%20Region%20-%2011%2F08%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1864967%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%3E%3CU%3EFinal%20Update%3C%2FU%3E%3A%20Sunday%2C%2008%20November%202020%2014%3A41%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2011%2F08%2C%2013%3A14%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2011%2F08%2C%2012%3A14%20UTC%20and%20that%20during%20the%201%20hours%20that%20it%20took%20to%20resolve%20the%20issue%20some%20of%20customers%20experienced%20intermittent%20data%20latency%20and%20incorrect%20alert%20activation%20in%20West%20Europe%20region.%3C%2FDIV%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20one%20of%20the%20backend%20dependent%20service.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%201%20Hours%26nbsp%3B%20-%2011%2F08%2C%2012%3A14%20UTC%20through%2011%2F08%2C%2013%3A14%20UTC%3CBR%20%2F%3E%3C%2FLI%3E%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-Madhav%3C%2FDIV%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-1864967%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ELog%20Search%20Alerts%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Sunday, 08 November 2020 14:41 UTC

We've confirmed that all systems are back to normal with no customer impact as of 11/08, 13:14 UTC. Our logs show the incident started on 11/08, 12:14 UTC and that during the 1 hours that it took to resolve the issue some of customers experienced intermittent data latency and incorrect alert activation in West Europe region.
 
  • Root Cause: The failure was due to one of the backend dependent service.
  • Incident Timeline: 1 Hours  - 11/08, 12:14 UTC through 11/08, 13:14 UTC
We understand that customers rely on Log Search Alerts as a critical service and apologize for any impact this incident caused.

-Madhav