Home
%3CLINGO-SUB%20id%3D%22lingo-sub-663079%22%20slang%3D%22en-US%22%3EExperiencing%20Latency%20and%20Data%20Gaps%20issue%20in%20Azure%20Portal%20for%20Many%20Data%20Types%20-%2006%2F02%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-663079%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%2002%20June%202019%2007%3A18%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2006%2F02%2C%2007%3A12%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2006%2F01%2C%2022%3A32%20UTC%20and%20that%20during%20the%208%20hours%2042%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%201%25%20of%20customers%20in%20West%20Europe%20region%20may%20have%20experienced%20data%20latency%20and%20data%20gaps%20issues.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20issue%20in%20backend%20service.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%26nbsp%3B%208%20Hours%20%26amp%3B%2042%20minutes%20-%2006%2F01%2C%2022%3A32%20UTC%20through%2006%2F02%2C%2007%3A12%20UTC%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-Naresh%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%20Sunday%2C%2002%20June%202019%2006%3A28%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20continue%20to%20investigate%20issues%20within%20Application%20Insights.%20Root%20cause%20is%20not%20fully%20understood%20at%20this%20time.%20Some%20customers%20continue%20to%20experience%20data%20latency%20and%20data%20gaps.%20We%20are%20working%20to%20establish%20the%20start%20time%20for%20the%20issue%2C%20initial%20findings%20indicate%20that%20the%20problem%20began%20at%2006%2F01%20~22%3A32%20UTC.%20We%20currently%20have%20no%20estimate%20for%20resolution.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3EWork%20Around%3C%2FU%3E%3A%3CNONE%20details%3D%22%22%20or%3D%22%22%3E%3C%2FNONE%3E%3C%2FLI%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2006%2F02%2008%3A30%20UTC%3C%2FLI%3E%3C%2FUL%3E-Naresh%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%20Sunday%2C%2002%20June%202019%2005%3A22%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20continue%20to%20investigate%20issues%20within%20Application%20Insights.%20Root%20cause%20is%20not%20fully%20understood%20at%20this%20time.%20Some%20customers%20continue%20to%20experience%20data%20latency%20and%20data%20gaps.%20We%20are%20working%20to%20establish%20the%20start%20time%20for%20the%20issue%2C%20initial%20findings%20indicate%20that%20the%20problem%20began%20at%2006%2F02%20~01%3A14%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%2006%2F02%2006%3A30%20UTC%3C%2FLI%3E%3C%2FUL%3E-Naresh%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%3CDIV%20style%3D%22font-size%3A14px%3B%22%3EInitial%20Update%3A%20Sunday%2C%2002%20June%202019%2002%3A13%20UTC%3C%2FDIV%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CBR%20%2F%3E%3C%2FDIV%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3EWe%20are%20aware%20of%20issues%20within%20Application%20Insights%20and%20are%20actively%20investigating.%20Some%20customers%20in%20West%20Europe%20region%20may%20experience%20Latency%20and%20Data%20Gaps.%3CBR%20%2F%3EWork%20Around%3A%20None%3CBR%20%2F%3ENext%20Update%3A%20Before%2006%2F02%2004%3A30%20UTC%3C%2FDIV%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CBR%20%2F%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3C%2FDIV%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CBR%20%2F%3E-Sindhu%3CBR%20%2F%3E%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-663079%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EApplication%20Insights%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Sunday, 02 June 2019 07:18 UTC

We've confirmed that all systems are back to normal with no customer impact as of 06/02, 07:12 UTC. Our logs show the incident started on 06/01, 22:32 UTC and that during the 8 hours 42 minutes that it took to resolve the issue 1% of customers in West Europe region may have experienced data latency and data gaps issues.
  • Root Cause: The failure was due to issue in backend service.
  • Incident Timeline:  8 Hours & 42 minutes - 06/01, 22:32 UTC through 06/02, 07:12 UTC
We understand that customers rely on Application Insights as a critical service and apologize for any impact this incident caused.

-Naresh

Update: Sunday, 02 June 2019 06:28 UTC

We continue to investigate issues within Application Insights. Root cause is not fully understood at this time. Some customers continue to experience data latency and data gaps. We are working to establish the start time for the issue, initial findings indicate that the problem began at 06/01 ~22:32 UTC. We currently have no estimate for resolution.
  • Work Around:
  • Next Update: Before 06/02 08:30 UTC
-Naresh

Update: Sunday, 02 June 2019 05:22 UTC

We continue to investigate issues within Application Insights. Root cause is not fully understood at this time. Some customers continue to experience data latency and data gaps. We are working to establish the start time for the issue, initial findings indicate that the problem began at 06/02 ~01:14 UTC. We currently have no estimate for resolution.
  • Work Around: None
  • Next Update: Before 06/02 06:30 UTC
-Naresh

Initial Update: Sunday, 02 June 2019 02:13 UTC

We are aware of issues within Application Insights and are actively investigating. Some customers in West Europe region may experience Latency and Data Gaps.
Work Around: None
Next Update: Before 06/02 04:30 UTC

We are working hard to resolve this issue and apologize for any inconvenience.

-Sindhu