%3CLINGO-SUB%20id%3D%22lingo-sub-974886%22%20slang%3D%22en-US%22%3EAlerting%20failure%20for%20Log%20Search%20Alerts%20in%20EUS%2C%20EUS2%20and%20WCUS%20-%2011%2F01%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-974886%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%20Friday%2C%2001%20November%202019%2023%3A36%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2011%2F1%2C%2023%3A36%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2011%2F1%2C%2020%3A15%20UTC%20and%20that%20during%20the%203%20hours%2C%2021%20minutes%20that%20it%20took%20to%20resolve%20some%20customers%20experienced%20latency%20in%20Log%20Search%20Alerts%20in%20East%20US%2C%20West%20Central%20US%20and%20East%20US%202.%3CBR%20%2F%3E%3CUL%3E%0A%20%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20a%20cache%20connection%20failure%2C%20which%20resulted%20in%20an%20internal%20denial%20of%20service%20event.%3C%2FLI%3E%0A%20%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%203%20Hours%20%26amp%3B%2021%20minutes%20-%2011%2F1%2C%2020%3A15%26nbsp%3Bthrough%2011%2F1%2C%2023%3A36%20UTC%3CBR%20%2F%3E%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-Jack%20Cantwell%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%20Friday%2C%2001%20November%202019%2023%3A01%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%20latency%20in%20Log%20Search%20Alerts%20in%20the%20East%20US%20region.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3EWork%20Around%3C%2FU%3E%3A%20none%20at%20this%20time%3C%2FLI%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2011%2F02%2000%3A30%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3CBR%20%2F%3E-Jack%20Cantwell%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-974886%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ELog%20Search%20Alerts%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Friday, 01 November 2019 23:36 UTC

We've confirmed that all systems are back to normal with no customer impact as of 11/1, 23:36 UTC. Our logs show the incident started on 11/1, 20:15 UTC and that during the 3 hours, 21 minutes that it took to resolve some customers experienced latency in Log Search Alerts in East US, West Central US and East US 2.
  • Root Cause: The failure was due to a cache connection failure, which resulted in an internal denial of service event.
  • Incident Timeline: 3 Hours & 21 minutes - 11/1, 20:15 through 11/1, 23:36 UTC
We understand that customers rely on Log Search Alerts as a critical service and apologize for any impact this incident caused.

-Jack Cantwell

Initial Update: Friday, 01 November 2019 23:01 UTC

We are aware of issues within Log Search Alerts and are actively investigating. Some customers may experience latency in Log Search Alerts in the East US region.
  • Work Around: none at this time
  • Next Update: Before 11/02 00:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Jack Cantwell