Home
%3CLINGO-SUB%20id%3D%22lingo-sub-905161%22%20slang%3D%22en-US%22%3EExperiencing%20Alerting%20failure%20for%20Log%20Search%20Alerts%20-%2010%2F10%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-905161%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%2010%20October%202019%2014%3A21%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%2F10%2C%2013%3A53%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2010%2F10%2C%2011%3A10%20UTC%20and%20that%20during%20the%202%20hours%2043%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20some%20of%20the%20customers%20in%20Central%20Canada%20experienced%20latency%20in%20Alerts%20firing.%3CUL%3E%0A%20%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%202%20Hours%20%26amp%3B%2043%20minutes%20-%2010%2F10%2C%2011%3A10%20UTC%20through%20M%2FD%2C%2013%3A53%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-Monish%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%2010%20October%202019%2012%3A23%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20aware%20of%20issues%20within%20Log%20Search%20Alerts%20and%20are%20actively%20investigating.%20Some%20customers%20in%20Central%20Canada%20may%20experience%20alerting%20delays%20and%20alerting%20failure.%3CUL%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2010%2F10%2015%3A30%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3CBR%20%2F%3E-Monish%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-905161%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ELog%20Search%20Alerts%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Thursday, 10 October 2019 14:21 UTC

We've confirmed that all systems are back to normal with no customer impact as of 10/10, 13:53 UTC. Our logs show the incident started on 10/10, 11:10 UTC and that during the 2 hours 43 minutes that it took to resolve the issue some of the customers in Central Canada experienced latency in Alerts firing.
  • Incident Timeline: 2 Hours & 43 minutes - 10/10, 11:10 UTC through 10/10, 13:53 UTC
We understand that customers rely on Log Search Alerts as a critical service and apologize for any impact this incident caused.

-Monish

Initial Update: Thursday, 10 October 2019 12:23 UTC

We are aware of issues within Log Search Alerts and are actively investigating. Some customers in Central Canada may experience alerting delays and alerting failure.
  • Next Update: Before 10/10 15:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Monish