Home
%3CLINGO-SUB%20id%3D%22lingo-sub-357625%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Access%20Issue%20in%20Azure%20portal%20for%20Log%20Analytics%20-%2002%2F27%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-357625%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%2027%20February%202019%2022%3A18%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%2F27%2C%2022%3A18%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2002%2F27%2C%2012%3A30%20UTC%20and%20that%20during%20the%20~9hr%2035m%20hours%20that%20it%20took%20to%20resolve%20the%20issue%20most%20of%20the%20USGov%20customers%20would%20have%20experienced%20Data%20Access%20issues%20in%20Azure%20Log%20analytics.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20one%20of%20our%20internal%20services%20impacted%20due%20to%20the%20Network%20outage%20happened%20in%20Fairfax%20this%20morning.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%209%20Hours%20%26amp%3B%2035%20minutes%20-%2002%2F27%2C%2012%3A30%20UTC%26nbsp%3Bthrough%26nbsp%3B%2002%2F27%2C%2022%3A05%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-Vishal%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%3EUpdate%3C%2FU%3E%3A%20Wednesday%2C%2027%20February%202019%2021%3A43%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3ERoot%20cause%20has%20been%20isolated%20to%20one%20of%20our%20internal%20service%20which%20is%20impacting%20Data%20access%2FQuerying%20in%20Azure%20Log%20analytics.%20To%20address%20this%20issue%20we%20are%20fixing%20this%20through%20a%20deployment.%20Most%20of%20US%20Gov%20customers%20may%20experience%20data%20access%2Fquerying%20data%20in%20Azure%20Log%20analytics%20and%20we%20estimate%20in%20next%20~1hour%20before%20all%20USGov%20users%20Data%20Access%20issues%20in%20Azure%20Log%20Analytics%20would%20be%20addressed.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3EWork%20Around%3C%2FU%3E%3A%20NA%3C%2FLI%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2002%2F28%2000%3A00%20UTC%3C%2FLI%3E%3C%2FUL%3E-Vishal%3CBR%20%2F%3E%3C%2FDIV%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%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%2027%20February%202019%2014%3A19%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20aware%20of%20issues%20within%20Log%20Analytics%20and%20are%20actively%20investigating.%20Initial%20investigation%20points%20to%20ongoing%20outage%26nbsp%3B%26nbsp%3Brelated%20to%20virtual%20machines%20in%20USGov%20Virginia%20region.%20Some%20customers%20in%20USGov%20Virginia%20region%20may%20experience%20Data%20Access%20issues%20in%20azure%20portal.%3C%2FDIV%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%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%2002%2F27%2016%3A30%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3CBR%20%2F%3E-Rama%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-357625%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20Log%20Analytics%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Wednesday, 27 February 2019 22:18 UTC

We've confirmed that all systems are back to normal with no customer impact as of 02/27, 22:18 UTC. Our logs show the incident started on 02/27, 12:30 UTC and that during the ~9hr 35m hours that it took to resolve the issue most of the USGov customers would have experienced Data Access issues in Azure Log analytics.
  • Root Cause: The failure was due to one of our internal services impacted due to the Network outage happened in Fairfax this morning.
  • Incident Timeline: 9 Hours & 35 minutes - 02/27, 12:30 UTC through  02/27, 22:05 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.

-Vishal

Update: Wednesday, 27 February 2019 21:43 UTC

Root cause has been isolated to one of our internal service which is impacting Data access/Querying in Azure Log analytics. To address this issue we are fixing this through a deployment. Most of US Gov customers may experience data access/querying data in Azure Log analytics and we estimate in next ~1hour before all USGov users Data Access issues in Azure Log Analytics would be addressed.
  • Work Around: NA
  • Next Update: Before 02/28 00:00 UTC
-Vishal

Initial Update: Wednesday, 27 February 2019 14:19 UTC

We are aware of issues within Log Analytics and are actively investigating. Initial investigation points to ongoing outage  related to virtual machines in USGov Virginia region. Some customers in USGov Virginia region may experience Data Access issues in azure portal.
  • Work Around: None
  • Next Update: Before 02/27 16:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Rama