Experiencing Alerting Latency for Activity Log Alerts - 09/30 - Resolved

Published Sep 30 2021 08:22 AM 735 Views
Final Update: Thursday, 30 September 2021 15:54 UTC

We've confirmed that all systems are back to normal with no customer impact as of 09/30, 15:30 UTC. Our logs show the incident started on 09/30, 13:00 UTC and that during the 2 hours & 30 minutes that it took to resolve some customers may have experienced delayed Activity Log Alerts.
  • Root Cause: The failure was due to one of our dependent service.
  • Incident Timeline: 2 Hours & 30 minutes - 09/30, 13:00 UTC through 09/30, 15:30 UTC
We understand that customers rely on Activity Log Alerts as a critical service and apologize for any impact this incident caused.

-Deepika

Initial Update: Thursday, 30 September 2021 15:15 UTC

We are aware of issues within Activity Log Alerts and are actively investigating. Some customers may experience delayed activity Log Alerts.
  • Work Around: None
  • Next Update: Before 09/30 19:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Deepika

%3CLINGO-SUB%20id%3D%22lingo-sub-2799678%22%20slang%3D%22en-US%22%3EExperiencing%20Alerting%20Latency%20for%20Activity%20Log%20Alerts%20-%2009%2F30%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2799678%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%2030%20September%202021%2015%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%2009%2F30%2C%2015%3A30%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2009%2F30%2C%2013%3A00%20UTC%20and%20that%20during%20the%202%20hours%20%26amp%3B%2030%20minutes%20that%20it%20took%20to%20resolve%20some%20customers%20may%20have%20experienced%20delayed%20Activity%20Log%20Alerts.%3CBR%20%2F%3E%3CUL%3E%0A%20%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20one%20of%20our%20dependent%20service.%3C%2FLI%3E%0A%20%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%202%20Hours%20%26amp%3B%2030%20minutes%20-%2009%2F30%2C%2013%3A00%20UTC%20through%2009%2F30%2C%2015%3A30%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-Deepika%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%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CU%3EInitial%20Update%3C%2FU%3E%3A%20Thursday%2C%2030%20September%202021%2015%3A15%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20aware%20of%20issues%20within%20Activity%20Log%20Alerts%20and%20are%20actively%20investigating.%20Some%20customers%20may%20experience%20delayed%20activity%20Log%20Alerts.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3EWork%20Around%3C%2FU%3E%3A%20None%3C%2FLI%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2009%2F30%2019%3A30%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3CBR%20%2F%3E-Deepika%3C%2FDIV%3E%3CHR%20style%3D%22border-top-color%3Alightgray%22%20%2F%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E
Version history
Last update:
‎Sep 30 2021 08:58 AM
Updated by: