%3CLINGO-SUB%20id%3D%22lingo-sub-1177326%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Gaps%20in%20Azure%20portal%20for%20Log%20Analytics%20in%20SUK%20region%20-%2002%2F17%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1177326%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%2017%20February%202020%2015%3A01%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%2F17%2C%2012%3A30%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2002%2F15%2C%2015%3A00%20UTC%20and%20that%20during%20the%26nbsp%3B%2045%20hours%20%26amp%3B%2030%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20Some%20customers%20may%20have%20experienced%20data%20loss%20issue%20in%20azure%20portal%20for%20some%20data%20types%20in%20South%20UK%20region.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20issues%20with%20one%20of%20our%20dependent%20service.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%2045%20Hours%20%26amp%3B%2030%20minutes%20-%2002%2F15%2C%2015%3A00%20UTC%20through%2002%2F17%2C%2012%3A30%20UTC%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-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%3CDIV%20style%3D%22%22%3E%3CU%20style%3D%22font-size%3A%2014px%3B%22%3EUpdate%3C%2FU%3E%3A%20Monday%2C%2017%20February%202020%2012%3A00%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3E%3CDIV%20style%3D%22%22%3EWe%20continue%20to%20investigate%20issues%20within%20Log%20Analytics.%20Root%20cause%20is%20not%20fully%20understood%20at%20this%20time.%20Some%20customers%20may%20experience%20data%20loss%20issue%20in%20azure%20portal%20for%20some%20data%20types%20in%20South%20UK%20region.%20We%20are%20working%20to%20establish%20the%20start%20time%20for%20the%20issue%2C%20initial%20findings%20indicate%20that%20the%20problem%20began%20at%2002%2F15%26nbsp%3B%2015%3A00%20UTC.%20We%20currently%20have%20no%20estimate%20for%20resolution.%3C%2FDIV%3E%3CUL%20style%3D%22font-size%3A%2014px%3B%22%3E%3CLI%3E%3CU%3EWork%20Around%3C%2FU%3E%3A%20None%3C%2FLI%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2002%2F17%2016%3A00%20UTC%3C%2FLI%3E%3C%2FUL%3E-Anusha%3CBR%20%2F%3E%3C%2FDIV%3E%3CHR%20style%3D%22border-top-color%3Alightgray%22%20%2F%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1177326%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20Log%20Analytics%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Monday, 17 February 2020 15:01 UTC

We've confirmed that all systems are back to normal with no customer impact as of 02/17, 12:30 UTC. Our logs show the incident started on 02/15, 15:00 UTC and that during the  45 hours & 30 minutes that it took to resolve the issue Some customers may have experienced data loss issue in azure portal for some data types in South UK region.
  • Root Cause: The failure was due issues with one of our dependent service.
  • Incident Timeline: 45 Hours & 30 minutes - 02/15, 15:00 UTC through 02/17, 12:30 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.

-Anusha

Update: Monday, 17 February 2020 12:00 UTC

We continue to investigate issues within Log Analytics. Root cause is not fully understood at this time. Some customers may experience data loss issue in azure portal for some data types in South UK region. We are working to establish the start time for the issue, initial findings indicate that the problem began at 02/15  15:00 UTC. We currently have no estimate for resolution.
  • Work Around: None
  • Next Update: Before 02/17 16:00 UTC
-Anusha