%3CLINGO-SUB%20id%3D%22lingo-sub-862693%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Access%20Issue%20in%20Azure%20portal%20for%20Log%20Analytics%20-%2009%2F19%20-%20Investigating%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-862693%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%3EUpdate%3C%2FU%3E%3A%20Friday%2C%2020%20September%202019%2008%3A46%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20continue%20to%20investigate%20issues%20within%20Log%20Analytics.%20Root%20cause%20is%20not%20fully%20understood%20at%20this%20time.%20Some%20customers%20continue%20to%20experience%20issues%20while%20accessing%20their%20data%20in%20the%20Azure%20Portal%20in%20West%20Central%20US%20and%20Australia%20South%20East%20regions.%20Query%20performance%20may%20also%20be%20degraded.%20Customers%20who%20have%20created%20Log%20Search%20Alerts%20in%20those%20regions%20could%20also%20have%20experienced%20alerting%20failures.%20We%20currently%20have%20no%20estimate%20for%20resolution.%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%2009%2F20%2015%3A00%20UTC%3C%2FLI%3E%3C%2FUL%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%3EUpdate%3C%2FU%3E%3A%20Friday%2C%2020%20September%202019%2004%3A28%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20continue%20to%20investigate%20issues%20within%20Log%20Analytics.%20Root%20cause%20is%20not%20fully%20understood%20at%20this%20time.%20Some%20customers%20continue%20to%20experience%20issues%20while%20accessing%20their%20data%20in%20the%20Azure%20Portal%20in%20the%20West%20Central%20US%20region.%20Query%20performance%20may%20also%20be%20degraded.%20Customers%20who%20have%20created%20Log%20Search%20Alerts%20in%20this%20region%20could%20also%20have%20experienced%20alerting%20failures.%26nbsp%3BWe%20currently%20have%20no%20estimate%20for%20resolution.%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%2009%2F20%2010%3A30%20UTC%3C%2FLI%3E%3C%2FUL%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%3EUpdate%3C%2FU%3E%3A%20Thursday%2C%2019%20September%202019%2016%3A01%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20continue%20to%20investigate%20issues%20within%20Log%20Analytics.%20Root%20cause%20is%20not%20fully%20understood%20at%20this%20time.%20Some%20customers%20continue%20to%20experience%20issues%20while%20accessing%20their%20data%20in%20the%20Azure%20Portal%20in%20the%20West%20Central%20US%20region.%20Query%20performance%20may%20also%20be%20degraded.%20Customers%20who%20have%20created%20Log%20Search%20Alerts%20in%20this%20region%20could%20also%20have%20experienced%20alerting%20failures.%26nbsp%3B%26nbsp%3BWe%20are%20working%20to%20establish%20the%20start%20time%20for%20the%20issue%2C%20initial%20findings%20indicate%20that%20the%20problem%20began%20at%2009%2F19%2005%3A30%20UTC.%20We%20currently%20have%20no%20estimate%20for%20resolution.%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%2009%2F19%2020%3A30%20UTC%3C%2FLI%3E%3C%2FUL%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%3EUpdate%3C%2FU%3E%3A%20Thursday%2C%2019%20September%202019%2012%3A46%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20continue%20to%20investigate%20issues%20within%20Log%20Analytics.%20Root%20cause%20is%20not%20fully%20understood%20at%20this%20time.%20Some%20customers%20continue%20to%20experience%20issues%20while%20accessing%20their%20data%20in%20the%20Azure%20Portal%20in%20the%20West%20Central%20US%20region.%20Query%20performance%20may%20also%20be%20degraded.%20We%20are%20working%20to%20establish%20the%20start%20time%20for%20the%20issue%2C%20initial%20findings%20indicate%20that%20the%20problem%20began%20at%2009%2F19%20~06%3A00%20UTC.%20We%20currently%20have%20no%20estimate%20for%20resolution.%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%2009%2F19%2017%3A00%20UTC%3C%2FLI%3E%3C%2FUL%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%20Thursday%2C%2019%20September%202019%2008%3A24%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20aware%20of%20issues%20within%20Log%20Analytics%20and%20are%20actively%20investigating.%20Some%20customers%20may%20experience%20data%20access%20issues%20in%20West%20Central%20US.%20Query%20performance%20could%20also%20be%20degraded%20in%20this%20region.%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%2009%2F19%2012%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%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-862693%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20Log%20Analytics%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Friday, 20 September 2019 10:04 UTC

We've confirmed that all systems are back to normal with no customer impact as of 09/20, 09:30 UTC. Our logs show the incident started on 09/19 05:30 UTC and that during the 28 hours that it took to resolve the issue some customers experienced would have experienced issues while accessing their data in the Azure Portal in West Central US and Australia South East regions. Query performance may also be degraded. Customers who have created Log Search Alerts in those regions could also have experienced alerting failures..
  • Root Cause: The failure was due to an issue in one of our back-end components.
  • Incident Timeline for West Central US: 28 Hours - 09/19, 05:30 UTC through 09/20, 09:30 UTC
  • Incident Timeline for South East Australia: 3 Hours - 09/20, 06:00 UTC through 09/20, 09:00 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.

-Varun

Update: Friday, 20 September 2019 08:46 UTC

We continue to investigate issues within Log Analytics. Root cause is not fully understood at this time. Some customers continue to experience issues while accessing their data in the Azure Portal in West Central US and Australia South East regions. Query performance may also be degraded. Customers who have created Log Search Alerts in those regions could also have experienced alerting failures. We currently have no estimate for resolution.
  • Work Around: None
  • Next Update: Before 09/20 15:00 UTC
-Varun

Update: Friday, 20 September 2019 04:28 UTC

We continue to investigate issues within Log Analytics. Root cause is not fully understood at this time. Some customers continue to experience issues while accessing their data in the Azure Portal in the West Central US region. Query performance may also be degraded. Customers who have created Log Search Alerts in this region could also have experienced alerting failures. We currently have no estimate for resolution.
  • Work Around: None
  • Next Update: Before 09/20 10:30 UTC
-Varun

Update: Thursday, 19 September 2019 16:01 UTC

We continue to investigate issues within Log Analytics. Root cause is not fully understood at this time. Some customers continue to experience issues while accessing their data in the Azure Portal in the West Central US region. Query performance may also be degraded. Customers who have created Log Search Alerts in this region could also have experienced alerting failures.  We are working to establish the start time for the issue, initial findings indicate that the problem began at 09/19 05:30 UTC. We currently have no estimate for resolution.
  • Work Around: None
  • Next Update: Before 09/19 20:30 UTC
-Varun

Update: Thursday, 19 September 2019 12:46 UTC

We continue to investigate issues within Log Analytics. Root cause is not fully understood at this time. Some customers continue to experience issues while accessing their data in the Azure Portal in the West Central US region. Query performance may also be degraded. We are working to establish the start time for the issue, initial findings indicate that the problem began at 09/19 ~06:00 UTC. We currently have no estimate for resolution.
  • Work Around: None
  • Next Update: Before 09/19 17:00 UTC
-Varun

Initial Update: Thursday, 19 September 2019 08:24 UTC

We are aware of issues within Log Analytics and are actively investigating. Some customers may experience data access issues in West Central US. Query performance could also be degraded in this region.
  • Work Around: None
  • Next Update: Before 09/19 12:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Varun