Home
%3CLINGO-SUB%20id%3D%22lingo-sub-850562%22%20slang%3D%22en-US%22%3EExperiencing%20Latency%20Issue%20or%20missing%20Alerts%20for%20Log%20Search%20Alert%20in%20EUS%20region%20-%2009%2F12%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-850562%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%2012%20September%202019%2006%3A56%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2009%2F12%2C%2004%3A30%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2009%2F12%2C%2002%3A40%20UTC%20and%20that%20during%20the%201%20hour%20and%2050%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%2023%25%20of%20customers%20in%20EUS%20region%20may%20have%20experienced%20delay%20in%20receiving%20the%20Log%20Alerts%20or%20missing%20alerts.%3CBR%20%2F%3E%3CUL%3E%0A%20%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20high%20traffic%20volume%20which%20caused%20throttling%20from%20dependent%20service.%3C%2FLI%3E%0A%20%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%201%20Hour%20%26amp%3B%2050%20minutes%20-%2009%2F12%2C%2002%3A40%20UTC%20through%2009%2F12%2C%2004%3A30%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%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-850562%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ELog%20Search%20Alerts%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Thursday, 12 September 2019 06:56 UTC

We've confirmed that all systems are back to normal with no customer impact as of 09/12, 04:30 UTC. Our logs show the incident started on 09/12, 02:40 UTC and that during the 1 hour and 50 minutes that it took to resolve the issue 23% of customers in EUS region may have experienced delay in receiving the Log Alerts or missing alerts.
  • Root Cause: The failure was due to high traffic volume which caused throttling from dependent service.
  • Incident Timeline: 1 Hour & 50 minutes - 09/12, 02:40 UTC through 09/12, 04:30 UTC
We understand that customers rely on Log Search Alerts as a critical service and apologize for any impact this incident caused.

-Mohini