Home
%3CLINGO-SUB%20id%3D%22lingo-sub-1093352%22%20slang%3D%22en-US%22%3EExperiencing%20Alerting%20failure%20for%20Log%20Search%20Alerts%20in%20West%20Europe%20-%2001%2F06%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1093352%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%20Tuesday%2C%2007%20January%202020%2000%3A17%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%2F06%2C%2023%3A40%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2001%2F06%2C%2022%3A00%20UTC%20and%20that%20during%20the%201%20hour%20and%2040%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20some%20customers%20in%20West%20Europe%20experienced%20issues%20with%20delays%20in%20receiving%20alerts%20or%20might%20not%20have%20received%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%20due%20to%20issue%20in%20one%20of%20the%20backend%20services.%26nbsp%3B%3C%2FLI%3E%0A%20%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%201%20Hours%20%26amp%3B%2040%20minutes%20-%2001%2F06%2C%2022%3A00%20UTC%20through%2001%2F06%2C%2023%3A40%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%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%2006%20January%202020%2023%3A01%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20aware%20of%20issues%20within%20Log%20Search%20Alerts%20and%20are%20actively%20investigating.%20Customers%20in%20West%20Europe%20may%20experience%20alerting%20failures%20or%20delay%20in%20receiving%20alerts.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3EWork%20Around%3C%2FU%3E%3A%3CNONE%20details%3D%22%22%20or%3D%22%22%3E%3C%2FNONE%3E%3C%2FLI%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2001%2F07%2003%3A30%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3CBR%20%2F%3E-Jayadev%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-1093352%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ELog%20Search%20Alerts%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Tuesday, 07 January 2020 00:17 UTC

We've confirmed that all systems are back to normal with no customer impact as of 01/06, 23:40 UTC. Our logs show the incident started on 01/06, 22:00 UTC and that during the 1 hour and 40 minutes that it took to resolve the issue some customers in West Europe experienced issues with delays in receiving alerts or might not have received Log Search Alerts.
  • Root Cause: The failure was due to due to issue in one of the backend services. 
  • Incident Timeline: 1 Hours & 40 minutes - 01/06, 22:00 UTC through 01/06, 23:40 UTC
We understand that customers rely on Log Search Alerts as a critical service and apologize for any impact this incident caused.

-Jayadev

Initial Update: Monday, 06 January 2020 23:01 UTC

We are aware of issues within Log Search Alerts and are actively investigating. Customers in West Europe may experience alerting failures or delay in receiving alerts.
  • Work Around:
  • Next Update: Before 01/07 03:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Jayadev