Home
%3CLINGO-SUB%20id%3D%22lingo-sub-894950%22%20slang%3D%22en-US%22%3EExperiencing%20Alerting%20failure%20for%20Log%20Search%20Alerts%20-%2010%2F05%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-894950%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%2005%20October%202019%2014%3A54%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%2F5%2C%2014%3A48%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2010%2F5%2C%209%3A15%20UTC%20and%20that%20during%20the%205%20hours%20and%2033%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20some%20customers%20in%20North%20Europe%2C%20South%20Central%20US%20and%20West%20Europe%20region%20might%20have%20experienced%20Alerting%20Failure%20issue.%3CBR%20%2F%3E%3CUL%3E%0A%20%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20an%20issue%20in%20one%20of%20our%20dependent%20services.%3C%2FLI%3E%0A%20%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%205%20Hours%20%26amp%3B%2038%20minutes%20-%2010%2F5%2C%2009%3A15%20UTC%20through%2010%2F5%2C%2014%3A48%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-Madhuri%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%20Saturday%2C%2005%20October%202019%2011%3A31%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%20issue%20in%20North%20Europe%2C%20South%20Central%20US%20and%20West%20Europe%20regions%20.%26nbsp%3B%3C%2FDIV%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CUL%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2010%2F05%2016%3A00%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3CBR%20%2F%3E-Madhuri%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-894950%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ELog%20Search%20Alerts%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Saturday, 05 October 2019 14:54 UTC

We've confirmed that all systems are back to normal with no customer impact as of 10/5, 14:48 UTC. Our logs show the incident started on 10/5, 9:15 UTC and that during the 5 hours and 33 minutes that it took to resolve the issue some customers in North Europe, South Central US and West Europe region might have experienced Alerting Failure issue.
  • Root Cause: The failure was due to an issue in one of our dependent services.
  • Incident Timeline: 5 Hours & 38 minutes - 10/5, 09:15 UTC through 10/5, 14:48 UTC
We understand that customers rely on Log Search Alerts as a critical service and apologize for any impact this incident caused.

-Madhuri

Initial Update: Saturday, 05 October 2019 11:31 UTC

We are aware of issues within Log Search Alerts and are actively investigating. Some customers may experience alerting failure issue in North Europe, South Central US and West Europe regions . 
  • Next Update: Before 10/05 16:00 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Madhuri