%3CLINGO-SUB%20id%3D%22lingo-sub-1561333%22%20slang%3D%22en-US%22%3EExperiencing%20Alerting%20failure%20for%20Activity%20Log%20Alerts%20in%20USGov%20cloud%20-%2008%2F02%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1561333%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%20Sunday%2C%2002%20August%202020%2015%3A37%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2007%2F31%2C%2000%3A24%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2007%2F30%2C%2020%3A40%20UTC%20and%20that%20during%20the%20~4%20hours%20that%20it%20took%20to%20resolve%20the%20issue%20some%20customers%20in%20USGov%20experienced%20failure%20in%20triggering%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%20incorrect%20deployment.%3C%2FLI%3E%0A%20%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%204%20Hours%20-%20M%2FD%2C%2007%2F30%2C%2020%3A40%20UTC%26nbsp%3Bthrough%26nbsp%3B%26nbsp%3B07%2F31%2C%2000%3A24%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-Anupama%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-1561333%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EActivity%20Log%20Alerts%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Sunday, 02 August 2020 15:37 UTC

We've confirmed that all systems are back to normal with no customer impact as of 07/31, 00:24 UTC. Our logs show the incident started on 07/30, 20:40 UTC and that during the ~4 hours that it took to resolve the issue some customers in USGov experienced failure in triggering Activity Log alerts.
  • Root Cause: The failure was due to incorrect deployment.
  • Incident Timeline: 4 Hours - M/D, 07/30, 20:40 UTC through  07/31, 00:24 UTC
We understand that customers rely on Activity Log Alerts as a critical service and apologize for any impact this incident caused.

-Anupama