Home
%3CLINGO-SUB%20id%3D%22lingo-sub-695868%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Access%20Issue%20in%20Azure%20portal%20for%20Log%20Analytics%20-%2006%2F17%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-695868%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%20June%202019%2012%3A51%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2006%2F17%2C%2012%3A05%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2006%2F17%2C%2011%3A20%20UTC%20and%20that%20during%20the%2045%20mins%20that%20it%20took%20to%20resolve%20the%20issue%20some%20of%20the%20customers%20in%20East%20Japan%20experienced%20data%20access%20issue%20in%20the%20Azure%20Portal%20and%20degradation%20in%20query%20performance.%3C%2FDIV%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CBR%20%2F%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%26nbsp%3B%2045%20minutes%20-%2006%2F17%2C%2011%3A20%20UTC%20through%2006%2F17%2C%2012%3A05%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20understand%20that%20customers%20rely%20on%20Azure%20Log%20Analytics%20and%20Log%20Search%20Alerts%20as%20a%20critical%20service%20and%20apologize%20for%20any%20impact%20this%20incident%20caused.%3CBR%20%2F%3E%3CBR%20%2F%3E-Monish%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%22font-size%3A14px%3B%22%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CU%3EInitial%20Update%3C%2FU%3E%3A%20Monday%2C%2017%20June%202019%2012%3A06%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20aware%20of%20issues%20within%20Log%20Analytics%20and%20Log%20Search%20alerts%20and%20are%20actively%20investigating.%20Some%20customers%20in%20East%20Japan%20may%20experience%20Data%20access%20issue%20in%20the%20azure%20portal.%3CUL%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2006%2F17%2014%3A30%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3CBR%20%2F%3E-Monish%3C%2FDIV%3E%3CHR%20style%3D%22border-top-color%3Alightgray%22%20%2F%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%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%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-695868%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20Log%20Analytics%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ELog%20Search%20Alerts%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Monday, 17 June 2019 12:51 UTC

We've confirmed that all systems are back to normal with no customer impact as of 06/17, 12:05 UTC. Our logs show the incident started on 06/17, 11:20 UTC and that during the 45 mins that it took to resolve the issue some of the customers in East Japan experienced data access issue in the Azure Portal and degradation in query performance.

  • Root Cause: The failure was due to an issue with one of our dependent service.
  • Incident Timeline:  45 minutes - 06/17, 11:20 UTC through 06/17, 12:05 UTC
We understand that customers rely on Azure Log Analytics and Log Search Alerts as a critical service and apologize for any impact this incident caused.

-Monish

Initial Update: Monday, 17 June 2019 12:06 UTC

We are aware of issues within Log Analytics and Log Search alerts and are actively investigating. Some customers in East Japan may experience Data access issue in the azure portal.
  • Next Update: Before 06/17 14:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Monish