Experiencing Latency and Data Loss issue in Azure Portal for Many Data Types - 06/05 - Resolved

Published Jun 04 2021 07:40 PM 954 Views
Final Update: Saturday, 05 June 2021 03:06 UTC

We've confirmed that all systems are back to normal with no customer impact as of 6/5, 02:45 UTC. Our logs show the incident started on 6/5, 00:25 UTC and that during the two hours and twenty minutes that it took to resolve the issue approximately 4000 customers may have experienced data latency, data loss and latent or misfired alerts.
  • Root Cause: The failure was due to faulty configuration of a backend service.
  • Incident Timeline: 2 Hours & 20 minutes - 6/5, 00:25 UTC through 6/5, 02:45 UTC
We understand that customers rely on Application Insights as a critical service and apologize for any impact this incident caused.

-Jack

Initial Update: Saturday, 05 June 2021 02:39 UTC

We are aware of issues within Application Insights data ingestion in the East Japan region and are actively investigating. Some customers may experience delayed or missed Log Search Alerts and Latency and Data Loss.
  • Next Update: Before 06/05 04:00 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Jack

%3CLINGO-SUB%20id%3D%22lingo-sub-2418187%22%20slang%3D%22en-US%22%3EExperiencing%20Latency%20and%20Data%20Loss%20issue%20in%20Azure%20Portal%20for%20Many%20Data%20Types%20-%2006%2F05%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2418187%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%20Saturday%2C%2005%20June%202021%2003%3A06%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%206%2F5%2C%2002%3A45%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%206%2F5%2C%2000%3A25%20UTC%20and%20that%20during%20the%20two%20hours%20and%20twenty%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20approximately%204000%20customers%20may%20have%20experienced%20data%20latency%2C%20data%20loss%20and%20latent%20or%20misfired%20alerts.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20faulty%20configuration%20of%20a%20backend%20service.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%202%20Hours%20%26amp%3B%2020%20minutes%20-%206%2F5%2C%2000%3A25%20UTC%20through%206%2F5%2C%2002%3A45%20UTC%3CBR%20%2F%3E%3C%2FLI%3E%3C%2FUL%3EWe%20understand%20that%20customers%20rely%20on%20Application%20Insights%20as%20a%20critical%20service%20and%20apologize%20for%20any%20impact%20this%20incident%20caused.%3CBR%20%2F%3E%3CBR%20%2F%3E-Jack%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%20Saturday%2C%2005%20June%202021%2002%3A39%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20aware%20of%20issues%20within%20Application%20Insights%20data%20ingestion%20in%20the%20East%20Japan%20region%20and%20are%20actively%20investigating.%20Some%20customers%20may%20experience%20delayed%20or%20missed%20Log%20Search%20Alerts%20and%20Latency%20and%20Data%20Loss.%3CUL%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2006%2F05%2004%3A00%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3CBR%20%2F%3E-Jack%3C%2FDIV%3E%3CHR%20style%3D%22border-top-color%3Alightgray%22%20%2F%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E
Version history
Last update:
‎Jun 04 2021 08:09 PM
Updated by: