Home
%3CLINGO-SUB%20id%3D%22lingo-sub-810356%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Access%20issue%20in%20Azure%20Portal%20for%20Log%20Analytics%20-%2008%2F19%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-810356%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%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%2019%20August%202019%2009%3A19%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%2F19%2C%2007%3A15%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2008%2F19%2C%2005%3A50%20UTC%20and%20that%20during%20the%201%20hour%2025%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%2015%25%20of%20customers%20in%20South%20Central%20US%2C%20France%20Central%20and%20North%20Europe%20regions%20experienced%20data%20access%20issues%20in%20the%20Azure%20Portal%20and%20degraded%20performance%20when%20queried%20through%20API.%20%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%3CFONT%20face%3D%22%26quot%3BHelvetica%20Neue%26quot%3B%2CHelvetica%2CArial%2Csans-serif%22%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%26nbsp%3B%201%20hours%2025%20minutes%20-%2008%2F19%2C%2005%3A50%20UTC%20through%2008%2F19%2C%2007%3A15%20UTC%3C%2FFONT%3E%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.%3C%2FDIV%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CBR%20%2F%3E-Anmol%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%20Monday%2C%2019%20August%202019%2006%3A49%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSPAN%20style%3D%22text-align%3A%20left%3B%20color%3A%20rgb(51%2C%2051%2C%2051)%3B%20text-transform%3A%20none%3B%20text-indent%3A%200px%3B%20letter-spacing%3A%20normal%3B%20font-size%3A%2014px%3B%20font-style%3A%20normal%3B%20font-variant%3A%20normal%3B%20font-weight%3A%20300%3B%20text-decoration%3A%20none%3B%20word-spacing%3A%200px%3B%20display%3A%20inline%20!important%3B%20white-space%3A%20normal%3B%20orphans%3A%202%3B%20float%3A%20none%3B%20-webkit-text-stroke-width%3A%200px%3B%20background-color%3A%20rgb(255%2C%20255%2C%20255)%3B%22%3E%3CFONT%20face%3D%22Helvetica%22%3EWe%20are%20aware%20of%20issues%20within%20Log%20Analytics%20and%20Log%20Search%20alert%20and%20are%20actively%20investigating.%20Some%20customers%20in%20South%20Central%20US%20may%20experience%20data%20access%20issue%20in%20the%20azure%20portal%20and%20when%20queried%20through%20API.%3C%2FFONT%3E%3C%2FSPAN%3E%3C%2FDIV%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CUL%3E%3CLI%3E%3CFONT%20face%3D%22Helvetica%22%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2008%2F19%2009%3A00%20UTC%3C%2FFONT%3E%3C%2FLI%3E%3C%2FUL%3E%3CFONT%20face%3D%22Helvetica%22%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.-Anmol%3C%2FFONT%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-810356%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, 19 August 2019 09:19 UTC

We've confirmed that all systems are back to normal with no customer impact as of 08/19, 07:15 UTC. Our logs show the incident started on 08/19, 05:50 UTC and that during the 1 hour 25 minutes that it took to resolve the issue 15% of customers in South Central US, France Central and North Europe regions 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:  1 hours 25 minutes - 08/19, 05:50 UTC through 08/19, 07:15 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.

-Anmol

Initial Update: Monday, 19 August 2019 06:49 UTC

We are aware of issues within Log Analytics and Log Search alert and are actively investigating. Some customers in South Central US may experience data access issue in the azure portal and when queried through API.
  • Next Update: Before 08/19 09:00 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Anmol