%3CLINGO-SUB%20id%3D%22lingo-sub-2148543%22%20slang%3D%22en-US%22%3EExperiencing%20ITSM%20connectior%20failures%20in%20East%20US%20region%20-%2002%2F19%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2148543%22%20slang%3D%22en-US%22%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CDIV%3E%3CU%3EFinal%20Update%3C%2FU%3E%3A%20Friday%2C%2019%20February%202021%2007%3A44%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2002%2F19%2C%2007%3A16%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2002%2F19%2C%2005%3A19%20UTC%20and%20that%20during%20the%201%20hour%20and%2057%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20some%20customers%20using%20Azure%20Monitor%20Alerts%20who%20may%20have%20experienced%20errors%20when%20using%20ITSM%20connector%20in%20East%20US%20region%20to%20create%20the%20work%20items%20in%20external%20ticketing%20systems.%3C%2FDIV%3E%3CDIV%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20an%20issue%20with%20one%20of%20our%20dependent%20service.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%201%20Hour%20%26amp%3B%2057%20minutes%20-%2002%2F19%2C%2005%3A19%20UTC%20through%2002%2F19%2C%2007%3A16%20UTC%3CBR%20%2F%3E%3C%2FLI%3E%3C%2FUL%3EWe%20understand%20that%20customers%20rely%20on%20Azure%20Monitor%20as%20a%20critical%20service%20and%20apologize%20for%20any%20impact%20this%20incident%20caused.%3CBR%20%2F%3E%3CBR%20%2F%3E-Mohini%3C%2FDIV%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2148543%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EActivity%20Log%20Alerts%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Friday, 19 February 2021 07:44 UTC

We've confirmed that all systems are back to normal with no customer impact as of 02/19, 07:16 UTC. Our logs show the incident started on 02/19, 05:19 UTC and that during the 1 hour and 57 minutes that it took to resolve the issue some customers using Azure Monitor Alerts who may have experienced errors when using ITSM connector in East US region to create the work items in external ticketing systems.
  • Root Cause: The failure was due to an issue with one of our dependent service.
  • Incident Timeline: 1 Hour & 57 minutes - 02/19, 05:19 UTC through 02/19, 07:16 UTC
We understand that customers rely on Azure Monitor as a critical service and apologize for any impact this incident caused.

-Mohini