%3CLINGO-SUB%20id%3D%22lingo-sub-1453783%22%20slang%3D%22en-US%22%3EExperiencing%20Latency%20and%20Data%20Loss%20issue%20in%20Azure%20Portal%20for%20Many%20Data%20Types%20-%2006%2F10%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1453783%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%20Wednesday%2C%2010%20June%202020%2014%3A29%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3E%3CDIV%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2006%2F10%2C%2014%3A14%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2006%2F10%2C%2012%3A57%20UTC%20and%20that%20during%20the%201%20hour%2017%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20some%20customers%20may%20have%20experienced%20intermittent%20latency%2C%20data%20gap%20issues%20when%20accessing%20application%20data%20in%20EUS2%20region.%20This%20includes%20data%20being%20sent%20by%20non-retrying%20SDKs%20(including%2C%20but%20not%20limited%20to%20JavaScript%20SDKs).%3C%2FDIV%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20an%20issue%20in%20one%20of%20our%20services%20responsible%20for%20ingesting%20data.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%201%20Hour%20%26amp%3B%2017%20minutes%20-%2006%2F10%2C%2012%3A57%20UTC%20through%2006%2F10%2C%2014%3A14%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-Syed%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%22%22%3E%3CU%20style%3D%22font-size%3A%2014px%3B%22%3EInitial%20Update%3C%2FU%3E%3A%20Wednesday%2C%2010%20June%202020%2013%3A54%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3E%3CDIV%20style%3D%22%22%3EWe%20are%20aware%20of%20issues%20within%20Application%20Insights%20and%20are%20actively%20investigating.%20Some%20customers%20may%20be%20experiencing%20intermittent%20latency%2C%20data%20gap%20issues%20when%20accessing%20application%20data%20in%20EUS2%20region.%20This%20includes%20data%20being%20sent%20by%20non-retrying%20SDKs%20(including%2C%20but%20not%20limited%20to%20JavaScript%20SDKs)%3CBR%20%2F%3E%3C%2FDIV%3E%3CUL%20style%3D%22font-size%3A%2014px%3B%22%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%2F10%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-Syed%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-1453783%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EApplication%20Insights%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Wednesday, 10 June 2020 14:29 UTC

We've confirmed that all systems are back to normal with no customer impact as of 06/10, 14:14 UTC. Our logs show the incident started on 06/10, 12:57 UTC and that during the 1 hour 17 minutes that it took to resolve the issue some customers may have experienced intermittent latency, data gap issues when accessing application data in EUS2 region. This includes data being sent by non-retrying SDKs (including, but not limited to JavaScript SDKs).
  • Root Cause: The failure was due to an issue in one of our services responsible for ingesting data.
  • Incident Timeline: 1 Hour & 17 minutes - 06/10, 12:57 UTC through 06/10, 14:14 UTC
We understand that customers rely on Application Insights as a critical service and apologize for any impact this incident caused.

-Syed

Initial Update: Wednesday, 10 June 2020 13:54 UTC

We are aware of issues within Application Insights and are actively investigating. Some customers may be experiencing intermittent latency, data gap issues when accessing application data in EUS2 region. This includes data being sent by non-retrying SDKs (including, but not limited to JavaScript SDKs)
  • Work Around: none
  • Next Update: Before 06/10 18:00 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Syed