Home
%3CLINGO-SUB%20id%3D%22lingo-sub-804151%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Access%20Issue%20in%20Azure%20portal%20for%20Log%20Analytics%20-%2008%2F14%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-804151%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%20August%202019%2009%3A20%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2008%2F14%2C%2008%3A55%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2008%2F14%2C%2008%3A21%20UTC%20and%20that%20during%20the%2034%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%208%25%20of%20customers%20in%20East%20US%20Region%20experienced%20data%20access%20issues%20in%20the%20Azure%20Portal%20and%20degraded%20performance%20when%20queried%20through%20API.%26nbsp%3B%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%2034%20minutes%20-%2008%2F14%2C%2008%3A21%20UTC%20through%2008%2F14%2C%2008%3A55%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%3CU%3EInitial%20Update%3C%2FU%3E%3A%20Wednesday%2C%2014%20August%202019%2008%3A57%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%20US%20may%20experience%20data%20access%20issue%20in%20the%20Azure%20portal%20and%20degraded%20performance%20when%20querying%20through%20API.%3CUL%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2008%2F14%2012%3A00%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%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-804151%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: Wednesday, 14 August 2019 09:20 UTC

We've confirmed that all systems are back to normal with no customer impact as of 08/14, 08:55 UTC. Our logs show the incident started on 08/14, 08:21 UTC and that during the 34 minutes that it took to resolve the issue 8% of customers in East US Region experienced data access issues in the Azure Portal and degraded performance when queried through API. 
  • Root Cause: The failure was due to an issue with one of our dependent service.
  • Incident Timeline:  34 minutes - 08/14, 08:21 UTC through 08/14, 08:55 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: Wednesday, 14 August 2019 08:57 UTC

We are aware of issues within Log Analytics and Log Search Alerts and are actively investigating. Some customers in East US may experience data access issue in the Azure portal and degraded performance when querying through API.
  • Next Update: Before 08/14 12:00 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Monish