%3CLINGO-SUB%20id%3D%22lingo-sub-1887699%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Access%20Issue%20in%20Azure%20portal%20for%20Log%20Analytics%20-%2011%2F15%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1887699%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%20Sunday%2C%2015%20November%202020%2002%3A03%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2011%2F15%2C%2001%3A35%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2011%2F15%2C%2000%3A20%20UTC%20and%20that%20during%20the%201%20hour%20and%2015%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20s%3CSPAN%20style%3D%22color%3A%20rgb(51%2C%2051%2C%2051)%3B%22%3Eome%20customers%20may%20experience%20issues%20with%20missed%2C%20delayed%20or%20wrongly%20fired%20alerts%20or%20experience%20difficulties%20accessing%20data%20for%20resources%20hosted%20in%20West%20US2%20and%20North%20Europe.%3C%2FSPAN%3E%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%20backend%20services.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%26nbsp%3B%201%20hour%2015%20minutes%20-%2011%2F15%2C%2000%3A20%20UTC%20through%2011%2F15%2C%2001%3A35%20UTC%3CBR%20%2F%3E%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-Eric%20Singleton%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%20Sunday%2C%2015%20November%202020%2001%3A18%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20aware%20of%20issues%20within%20Log%20Analytics%20and%20are%20actively%20investigating.%26nbsp%3B%3CSPAN%20style%3D%22color%3A%20rgb(51%2C%2051%2C%2051)%3B%20font-family%3A%20SegoeUI%2C%20Lato%2C%20%22%20helvetica%3D%22%22%20neue%3D%22%22%3ESome%20customers%20may%20experience%20issues%20with%20missed%2C%20delayed%20or%20wrongly%20fired%20alerts%20or%20experience%20difficulties%20accessing%20data%20for%20resources%20hosted%20in%20West%20US2%20and%20North%20Europe.%26nbsp%3B%3C%2FSPAN%3E.%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%2011%2F15%2003%3A30%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3CBR%20%2F%3E-Eric%20Singleton%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-1887699%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: Sunday, 15 November 2020 02:03 UTC

We've confirmed that all systems are back to normal with no customer impact as of 11/15, 01:35 UTC. Our logs show the incident started on 11/15, 00:20 UTC and that during the 1 hour and 15 minutes that it took to resolve the issue some customers may experience issues with missed, delayed or wrongly fired alerts or experience difficulties accessing data for resources hosted in West US2 and North Europe.
  • Root Cause: The failure was due to an issue with one of our backend services.
  • Incident Timeline:  1 hour 15 minutes - 11/15, 00:20 UTC through 11/15, 01:35 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.

-Eric Singleton

Initial Update: Sunday, 15 November 2020 01:18 UTC

We are aware of issues within Log Analytics and are actively investigating. Some customers may experience issues with missed, delayed or wrongly fired alerts or experience difficulties accessing data for resources hosted in West US2 and North Europe. .
  • Work Around: None
  • Next Update: Before 11/15 03:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Eric Singleton