Experiencing Data Latency for Activity Logs and Activity Log Alerts

Published 06-23-2020 09:53 AM 959 Views
Final Update: Tuesday, 23 June 2020 16:39 UTC

We've confirmed that all systems are back to normal with no customer impact as of 06/23, 06:00 UTC. Our logs show the incident started on 06/18, 18:00 UTC and that during the 4 days and 12 hours that it took to resolve the issue small subset of customers would have experienced delay of data in Activity logs and delays in activity log alerts getting triggered. The Activity logs data being referred is the data generated by the security team.
  • Root Cause: The failure was due to issues with one of the backend services.
  • Incident Timeline: 4 Days & 12 Hours - 06/18, 18:00 UTC through 06/23, 06:00 UTC
We understand that customers rely on Activity Log Alerts as a critical service and apologize for any impact this incident caused.

-Jayadev

%3CLINGO-SUB%20id%3D%22lingo-sub-1484212%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Latency%20for%20Activity%20Logs%20and%20Activity%20Log%20Alerts%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1484212%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%2023%20June%202020%2016%3A39%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2006%2F23%2C%2006%3A00%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2006%2F18%2C%2018%3A00%20UTC%20and%20that%20during%20the%204%20days%20and%2012%20hours%20that%20it%20took%20to%20resolve%20the%20issue%20small%20subset%20of%20customers%20would%20have%20experienced%20delay%20of%20data%20in%20Activity%20logs%20and%20delays%20in%20activity%20log%20alerts%20getting%20triggered.%20The%20Activity%20logs%20data%20being%20referred%20is%20the%20data%20generated%20by%20the%20security%20team.%3CBR%20%2F%3E%3CUL%3E%0A%20%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20issues%20with%20one%20of%20the%20backend%20services.%3C%2FLI%3E%0A%20%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%204%20Days%20%26amp%3B%2012%20Hours%20-%2006%2F18%2C%2018%3A00%20UTC%20through%2006%2F23%2C%2006%3A00%20UTC%3C%2FLI%3E%0A%3C%2FUL%3EWe%20understand%20that%20customers%20rely%20on%20Activity%20Log%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%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1484212%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EActivity%20Log%20Alerts%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Version history
Last update:
‎Jun 23 2020 09:53 AM
Updated by: