Home
%3CLINGO-SUB%20id%3D%22lingo-sub-390776%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Access%20Issue%20in%20Azure%20portal%20for%20Log%20Analytics%20-%2003%2F29%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-390776%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%2029%20March%202019%2013%3A49%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2003%2F29%2C%2018%3A30%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2003%2F29%2C%2017%3A50%20UTC%20and%20that%20during%20the%2040%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20some%20customers%20in%20South%20East%20Asia%20would%20had%20experienced%20data%20access%20issues%20in%20the%20Azure%20Portal.%20Queries%20in%20the%20Portal%20and%20API%20calls%20would%20also%20have%20been%20degraded.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20the%20issues%20in%20one%20of%20our%20dependency%20service.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%2040%20minutes%20-%2003%2F29%2C%2017%3A50%20UTC%20through%2003%2F29%2C%2018%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-Varun%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%2029%20March%202019%2013%3A04%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20aware%20of%20issues%20within%20Log%20Analytics%20and%20are%20actively%20investigating.%20Some%20customers%20may%20experience%20issues%20while%20accessing%20their%20data%20on%20the%20Azure%20portal.%20Query%20performance%20and%20API's%20will%20also%20be%20affected.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3EWork%20Around%3C%2FU%3E%3A%20None%3C%2FLI%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2003%2F29%2015%3A30%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3CBR%20%2F%3E-Varun%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-390776%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20Log%20Analytics%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Friday, 29 March 2019 13:49 UTC

We've confirmed that all systems are back to normal with no customer impact as of 03/29, 18:30 UTC. Our logs show the incident started on 03/29, 17:50 UTC and that during the 40 minutes that it took to resolve the issue some customers in South East Asia would had experienced data access issues in the Azure Portal. Queries in the Portal and API calls would also have been degraded.
  • Root Cause: The failure was due to the issues in one of our dependency service.
  • Incident Timeline: 40 minutes - 03/29, 17:50 UTC through 03/29, 18:30 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.

-Varun

Initial Update: Friday, 29 March 2019 13:04 UTC

We are aware of issues within Log Analytics and are actively investigating. Some customers may experience issues while accessing their data on the Azure portal. Query performance and API's will also be affected.
  • Work Around: None
  • Next Update: Before 03/29 15:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Varun