Home
%3CLINGO-SUB%20id%3D%22lingo-sub-878353%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Access%20Issue%20for%20Log%20Analytics%20in%20South%20Africa%20North%20region%20-%2009%2F27%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-878353%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%2027%20September%202019%2003%3A07%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2009%2F26%2C%2022%3A50%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2009%2F26%2C%2021%3A25%20UTC%20and%20that%20during%20the%201%20hour%20and%2025%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20some%20of%20the%20customers%20experienced%20issues%20with%20data%20access%20in%20South%20Africa%20North%20region%20for%20Log%20Analytics%20and%20also%20issues%20with%20Log%20Alerts%20not%20being%20triggered%20as%20expected.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20overload%20on%20the%20service.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%201%20Hour%20%26amp%3B%2025%20minutes%20-%2009%2F26%2C%2021%3A25%20UTC%20through%2009%2F26%2C%2022%3A50%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-Jayadev%3CBR%20%2F%3E%3C%2FDIV%3E%3CHR%20style%3D%22border-top-color%3Alightgray%22%20%2F%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-878353%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20Log%20Analytics%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Friday, 27 September 2019 03:07 UTC

We've confirmed that all systems are back to normal with no customer impact as of 09/26, 22:50 UTC. Our logs show the incident started on 09/26, 21:25 UTC and that during the 1 hour and 25 minutes that it took to resolve the issue some of the customers experienced issues with data access in South Africa North region for Log Analytics and also issues with Log Alerts not being triggered as expected.
  • Root Cause: The failure was due to overload on the service.
  • Incident Timeline: 1 Hour & 25 minutes - 09/26, 21:25 UTC through 09/26, 22:50 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.

-Jayadev