%3CLINGO-SUB%20id%3D%22lingo-sub-1117922%22%20slang%3D%22en-US%22%3EExperiencing%20Alerting%20failure%20for%20Log%20Search%20Alerts%20-%2001%2F20%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1117922%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%20Monday%2C%2020%20January%202020%2011%3A35%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2001%2F20%2C%2010%3A40%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2001%2F20%2C%2009%3A55%20UTC%20and%20that%20during%20the%2045%20minutes%20that%20it%20took%20to%20resolve%20the%20issue.%20Some%20customers%20may%20have%20experienced%20missed%20or%20delayed%20Log%20Search%20alerts%20in%20South%20UK%20region.%3CBR%20%2F%3E%3CUL%3E%0A%20%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%26nbsp%3B%3CSPAN%20style%3D%22color%3A%20rgb(51%2C%2051%2C%2051)%3B%20font-family%3A%20SegoeUI%2C%20Lato%2C%20%26quot%3BHelvetica%20Neue%26quot%3B%2C%20Helvetica%2C%20Arial%2C%20sans-serif%3B%22%3E%26nbsp%3BThe%20failure%20was%20due%20to%20an%20issue%20with%20one%20of%20our%20dependent%20service%3C%2FSPAN%3E.%3C%2FLI%3E%0A%20%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%2045%20minutes%20-%2001%2F20%2C%2009%3A55%20UTC%20through%2001%2F20%2C%2010%3A40%20UTC%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-Anusha%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%3CU%3EInitial%20Update%3C%2FU%3E%3A%20Monday%2C%2020%20January%202020%2011%3A21%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20aware%20of%20issues%20within%20Log%20Search%20Alerts%20and%20are%20actively%20investigating.%20Some%20customers%20may%20experience%20missed%20or%20delayed%20Log%20Search%20alerts%20in%20South%20UK%20region.%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%2001%2F20%2015%3A30%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3CBR%20%2F%3E-Anusha%3C%2FDIV%3E%3CHR%20style%3D%22border-top-color%3Alightgray%22%20%2F%3E%3CDIV%20style%3D%22%22%3E%3CDIV%3E%3CBR%20%2F%3E%3C%2FDIV%3E%3CDIV%3E%3CBR%20%2F%3E%3C%2FDIV%3E%3C%2FDIV%3E%3CDIV%20style%3D%22%22%3E%3CSPAN%20style%3D%22font-size%3A%2014px%3B%22%3E%3CU%3E%3C%2FU%3E%3C%2FSPAN%3E%3C%2FDIV%3E%3CHR%20style%3D%22border-top-color%3Alightgray%22%20%2F%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1117922%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ELog%20Search%20Alerts%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Monday, 20 January 2020 11:35 UTC

We've confirmed that all systems are back to normal with no customer impact as of 01/20, 10:40 UTC. Our logs show the incident started on 01/20, 09:55 UTC and that during the 45 minutes that it took to resolve the issue. Some customers may have experienced missed or delayed Log Search alerts in South UK region.
  • Root Cause The failure was due to an issue with one of our dependent service.
  • Incident Timeline: 45 minutes - 01/20, 09:55 UTC through 01/20, 10:40 UTC
We understand that customers rely on Log Search Alerts as a critical service and apologize for any impact this incident caused.

-Anusha

Initial Update: Monday, 20 January 2020 11:21 UTC

We are aware of issues within Log Search Alerts and are actively investigating. Some customers may experience missed or delayed Log Search alerts in South UK region.
  • Work Around: None
  • Next Update: Before 01/20 15:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Anusha