Home
%3CLINGO-SUB%20id%3D%22lingo-sub-821892%22%20slang%3D%22en-US%22%3EExperiencing%20Alerting%20failure%20for%20Log%20Search%20Alerts%20-%2008%2F25%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-821892%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%2025%20August%202019%2014%3A05%20UTC%3C%2FDIV%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CBR%20%2F%3E%3C%2FDIV%3E%3CDIV%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2008%2F25%2C%2013%3A00%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2008%2F25%2C%2012%3A05%20UTC%20and%20that%20during%20the%2055%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20some%20customers%20may%20have%20experienced%20alerting%20failures%20for%20Log%20alerts%20in%20China%20East%202%20region.%3C%2FDIV%3E%3CDIV%3E%3CBR%20%2F%3E%3C%2FDIV%3E%3CDIV%3E%3CUL%3E%3CLI%20style%3D%22font-family%3A%20SegoeUI%2C%20Lato%2C%20%26quot%3BHelvetica%20Neue%26quot%3B%2C%20Helvetica%2C%20Arial%2C%20sans-serif%3B%22%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20issues%20in%20one%20of%20our%20back-end%20services.%26nbsp%3B%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%2055%20minutes%20-%2008%2F25%2C%2012%3A05%20UTC%26nbsp%3Bthrough%2008%2F25%2C%2013%3A00%20UTC%3CBR%20%2F%3E%3C%2FLI%3E%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-Sapna%3CBR%20%2F%3E%3C%2FDIV%3E%3CDIV%3E%3CBR%20%2F%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-821892%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ELog%20Search%20Alerts%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Sunday, 25 August 2019 14:05 UTC

We've confirmed that all systems are back to normal with no customer impact as of 08/25, 13:00 UTC. Our logs show the incident started on 08/25, 12:05 UTC and that during the 55 minutes that it took to resolve the issue some customers may have experienced alerting failures for Log alerts in China East 2 region.

  • Root Cause: The failure was due to issues in one of our back-end services. 
  • Incident Timeline: 55 minutes - 08/25, 12:05 UTC through 08/25, 13:00 UTC
We understand that customers rely on Log Search Alerts as a critical service and apologize for any impact this incident caused.

-Sapna