Home
%3CLINGO-SUB%20id%3D%22lingo-sub-784600%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Gaps%20issue%20in%20Azure%20Portal%20for%20Many%20Data%20Types%20in%20East%20US%20-%2008%2F01%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-784600%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%3CDIV%20style%3D%22%22%3E%3CDIV%20style%3D%22%22%3E%3CDIV%20style%3D%22%22%3E%3CP%20class%3D%22MsoNormal%22%20style%3D%22margin-bottom%3A%2012pt%3B%22%3E%3CU%20style%3D%22font-size%3A%2014px%3B%22%3E%3CSPAN%20style%3D%22font-size%3A%2010.5pt%3B%20font-family%3A%20Helvetica%2C%20sans-serif%3B%20background-image%3A%20initial%3B%20background-position%3A%20initial%3B%20background-size%3A%20initial%3B%20background-repeat%3A%20initial%3B%20background-attachment%3A%20initial%3B%20background-origin%3A%20initial%3B%20background-clip%3A%20initial%3B%22%3EFinal%20Update%3C%2FSPAN%3E%3C%2FU%3E%3CSPAN%20style%3D%22font-size%3A%2010.5pt%3B%20font-family%3A%20Helvetica%2C%20sans-serif%3B%20background-image%3A%20initial%3B%20background-position%3A%20initial%3B%20background-size%3A%20initial%3B%20background-repeat%3A%20initial%3B%20background-attachment%3A%20initial%3B%20background-origin%3A%20initial%3B%20background-clip%3A%20initial%3B%22%3E%3A%20Thursday%2C%2001%20August%202019%2018%3A39%20UTC%3C%2FSPAN%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSPAN%20style%3D%22background-image%3A%20initial%3B%20background-position%3A%20initial%3B%20background-size%3A%20initial%3B%20background-repeat%3A%20initial%3B%20background-attachment%3A%20initial%3B%20background-origin%3A%20initial%3B%20background-clip%3A%20initial%3B%22%3E%3CSPAN%20style%3D%22font-family%3A%20Helvetica%2C%20sans-serif%3B%22%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20as%20of%2008%2F01%2018%3A39%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2008%2F01%2017%3A39%20UTC%20and%20during%20the%2038%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20customers%20publishing%20telemetry%20in%20East%20Us%20region%20using%20Javascript%20SDKs%20and%20other%20SDKs%20that%20don't%20retry%20would%20experience%20data%20gaps%20in%20various%20reports.%20As%20this%20data%20didn't%20make%20to%20our%20ingestion%20system%20so%20they%20would%20continue%20to%20see%20missing%20telemetry%20for%20impacted%20duration.%20We%20apologize%20for%20any%20impact%20this%20incident%20has%20caused.%3C%2FSPAN%3E%3CSPAN%20style%3D%22font-family%3A%20Helvetica%2C%20sans-serif%3B%20font-size%3A%2010.5pt%3B%22%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3C%2FP%3E%3CP%3E%3C%2FP%3E%3CUL%20type%3D%22disc%22%20style%3D%22font-size%3A%2014px%3B%22%3E%3CLI%20class%3D%22MsoNormal%22%20style%3D%22background-image%3A%20initial%3B%20background-position%3A%20initial%3B%20background-size%3A%20initial%3B%20background-repeat%3A%20initial%3B%20background-attachment%3A%20initial%3B%20background-origin%3A%20initial%3B%20background-clip%3A%20initial%3B%22%3E%3CU%3E%3CSPAN%20style%3D%22font-size%3A%2010.5pt%3B%20font-family%3A%20Helvetica%2C%20sans-serif%3B%22%3ERoot%20Cause%3C%2FSPAN%3E%3C%2FU%3E%3CSPAN%20style%3D%22font-size%3A%2010.5pt%3B%20font-family%3A%20Helvetica%2C%20sans-serif%3B%22%3E%3A%20The%20failure%20was%20due%20to%20issue%20in%20one%20of%20our%20dependent%20services.%3CP%3E%3C%2FP%3E%3C%2FSPAN%3E%3C%2FLI%3E%3CLI%20class%3D%22MsoNormal%22%20style%3D%22background-image%3A%20initial%3B%20background-position%3A%20initial%3B%20background-size%3A%20initial%3B%20background-repeat%3A%20initial%3B%20background-attachment%3A%20initial%3B%20background-origin%3A%20initial%3B%20background-clip%3A%20initial%3B%22%3E%3CU%3E%3CSPAN%20style%3D%22font-size%3A%2010.5pt%3B%20font-family%3A%20Helvetica%2C%20sans-serif%3B%22%3EIncident%20Timeline%3C%2FSPAN%3E%3C%2FU%3E%3CSPAN%20style%3D%22font-size%3A%2010.5pt%3B%20font-family%3A%20Helvetica%2C%20sans-serif%3B%22%3E%3A%2038%20minutes%20-%2008%2F01%2C%2017%3A39%20UTC%20through%2008%2F01%2C%2018%3A17%20UTC%3CP%3E%3C%2FP%3E%3C%2FSPAN%3E%3C%2FLI%3E%3C%2FUL%3E%3CP%20class%3D%22MsoNormal%22%20style%3D%22font-size%3A%2014px%3B%22%3E%3CSPAN%20style%3D%22font-size%3A%2010.5pt%3B%20font-family%3A%20Helvetica%2C%20sans-serif%3B%20background-image%3A%20initial%3B%20background-position%3A%20initial%3B%20background-size%3A%20initial%3B%20background-repeat%3A%20initial%3B%20background-attachment%3A%20initial%3B%20background-origin%3A%20initial%3B%20background-clip%3A%20initial%3B%22%3EWe%20understand%20that%20customers%20rely%20on%20Application%20Insights%20as%20a%20critical%20service%20and%20apologize%20for%20any%20impact%20this%20incident%20caused.%3C%2FSPAN%3E%3CSPAN%20style%3D%22font-size%3A%2010.5pt%3B%20font-family%3A%20Helvetica%2C%20sans-serif%3B%22%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSPAN%20style%3D%22background-image%3A%20initial%3B%20background-position%3A%20initial%3B%20background-size%3A%20initial%3B%20background-repeat%3A%20initial%3B%20background-attachment%3A%20initial%3B%20background-origin%3A%20initial%3B%20background-clip%3A%20initial%3B%22%3E-Sindhu%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%3CDIV%20style%3D%22font-size%3A%2014px%3B%22%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%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-784600%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EApplication%20Insights%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E

Final Update: Thursday, 01 August 2019 18:39 UTC

We've confirmed that all systems are back to normal as of 08/01 18:39 UTC. Our logs show the incident started on 08/01 17:39 UTC and during the 38 minutes that it took to resolve the issue customers publishing telemetry in East Us region using Javascript SDKs and other SDKs that don't retry would experience data gaps in various reports. As this data didn't make to our ingestion system so they would continue to see missing telemetry for impacted duration. We apologize for any impact this incident has caused. 

  • Root Cause: The failure was due to issue in one of our dependent services.

  • Incident Timeline: 38 minutes - 08/01, 17:39 UTC through 08/01, 18:17 UTC

We understand that customers rely on Application Insights as a critical service and apologize for any impact this incident caused.

-Sindhu