%3CLINGO-SUB%20id%3D%22lingo-sub-1777772%22%20slang%3D%22en-US%22%3EData%20Latency%20and%20Possible%20Data%20Loss%20in%20East%20US%20region%20for%20Log%20Analytics%20-%2010%2F13%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1777772%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%20Wednesday%2C%2014%20October%202020%2000%3A02%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2010%2F13%2C%2023%3A43%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2010%2F13%2C%2023%3A07%20UTC%20and%20that%20during%20the%2036%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20many%20customers%20in%20the%20East%20US%20region%20experienced%20data%20latency%20and%20possible%20data%20loss.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20a%20failed%20upgrade%20to%20a%20backend%20service%20and%20was%20fixed%20when%20the%20upgrade%20was%20rolled%20back.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%2037%20minutes%20-%2010%2F13%2C%2023%3A07%26nbsp%3BUTC%20through%2010%2F13%2C%2023%3A43%26nbsp%3BUTC%3CBR%20%2F%3E%3C%2FLI%3E%3C%2FUL%3EWe%20understand%20that%20customers%20rely%20on%20Azure%20Log%20Analytics%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%20Tuesday%2C%2013%20October%202020%2023%3A27%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20aware%20of%20issues%20within%20Log%20Analytics%20and%20are%20actively%20investigating.%20Some%20customers%20may%20experience%20data%20latency%20or%20data%20loss.%3CUL%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2010%2F14%2000%3A30%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3C%2FDIV%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%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-1777772%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20Log%20Analytics%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Wednesday, 14 October 2020 00:02 UTC

We've confirmed that all systems are back to normal with no customer impact as of 10/13, 23:43 UTC. Our logs show the incident started on 10/13, 23:07 UTC and that during the 36 minutes that it took to resolve the issue many customers in the East US region experienced data latency and possible data loss.
  • Root Cause: The failure was due to a failed upgrade to a backend service and was fixed when the upgrade was rolled back.
  • Incident Timeline: 37 minutes - 10/13, 23:07 UTC through 10/13, 23:43 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.

-Jack Cantwell

Initial Update: Tuesday, 13 October 2020 23:27 UTC

We are aware of issues within Log Analytics and are actively investigating. Some customers may experience data latency or data loss.
  • Next Update: Before 10/14 00:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.

-Jack Cantwell