Home
%3CLINGO-SUB%20id%3D%22lingo-sub-1107491%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Latency%20issue%20in%20Azure%20Portal%20for%20Many%20Data%20Types%20-%2001%2F14%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1107491%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%20Tuesday%2C%2014%20January%202020%2015%3A33%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2001%2F14%2C%2015%3A10%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2001%2F14%2C%2008%3A30%20UTC%20and%20that%20during%20the%206%20hours%2040%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20some%20of%20the%20customers%20in%20East%20US%20and%20North%20Europe%20experienced%20data%20latency%20and%20unavailability%20of%20fresh%20data%20for%20Application%20Insights%20and%20false%20alerts%20for%20Log%20Search%20Alerts.%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%20service.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%206%20Hours%20%26amp%3B%2040%20minutes%20-%2001%2F14%2C%2008%3A30%20UTC%20through%2001%2F14%2C%2015%3A10%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20understand%20that%20customers%20rely%20on%20Application%20Insights%20and%20Log%20Search%20Alerts%20as%20critical%20services%20and%20apologize%20for%20any%20impact%20this%20incident%20caused.%3CBR%20%2F%3E%3CBR%20%2F%3E-Monish%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%20Tuesday%2C%2014%20January%202020%2014%3A35%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20aware%20of%20issues%20within%20Application%20Insights%20and%20are%20actively%20investigating.%20Some%20customers%20in%20East%20US%20and%20North%20Europe%20may%20experience%20Data%20Latency.%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%2001%2F14%2018%3A00%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3CBR%20%2F%3E-Monish%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-1107491%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EApplication%20Insights%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ELog%20Search%20Alerts%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Tuesday, 14 January 2020 15:33 UTC

We've confirmed that all systems are back to normal with no customer impact as of 01/14, 15:10 UTC. Our logs show the incident started on 01/14, 08:30 UTC and that during the 6 hours 40 minutes that it took to resolve the issue some of the customers in East US and North Europe experienced data latency and unavailability of fresh data for Application Insights and false alerts for Log Search Alerts.
  • Root Cause: The failure was due to an issue with one of our backend service.
  • Incident Timeline: 6 Hours & 40 minutes - 01/14, 08:30 UTC through 01/14, 15:10 UTC
We understand that customers rely on Application Insights and Log Search Alerts as critical services and apologize for any impact this incident caused.

-Monish

Initial Update: Tuesday, 14 January 2020 14:35 UTC

We are aware of issues within Application Insights and are actively investigating. Some customers in East US and North Europe may experience Data Latency.
  • Work Around: None
  • Next Update: Before 01/14 18:00 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Monish