%3CLINGO-SUB%20id%3D%22lingo-sub-2075967%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Latency%20issue%20in%20Azure%20Portal%20for%20Many%20Data%20Types%20-%2001%2F19%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2075967%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%20Tuesday%2C%2019%20January%202021%2018%3A57%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%201%2F19%2C%2017%3A53%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%201%2F19%2C%2017%3A26%20UTC%20and%20that%20during%20the%2027%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20impacted%20customers%20experienced%20ingested%20data%20latency%20and%20possible%20alerts%20misfiring%20due%20to%20latent%20data.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20a%20large%20unexpected%20ingress%20of%20data%20to%20a%20scale%20unit.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%2027%20minutes%20-%201%2F19%2C%2017%3A26%20UTC%20through%201%2F19%2C%2017%3A53%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-Jeff%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%2019%20January%202021%2018%3A32%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%20region%20may%20experience%20delayed%20or%20missed%20Log%20Search%20Alerts%20and%20Data%20Latency.%3CUL%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2001%2F19%2020%3A00%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3CBR%20%2F%3E-Jeff%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-2075967%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EApplication%20Insights%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Tuesday, 19 January 2021 18:57 UTC

We've confirmed that all systems are back to normal with no customer impact as of 1/19, 17:53 UTC. Our logs show the incident started on 1/19, 17:26 UTC and that during the 27 minutes that it took to resolve the issue impacted customers experienced ingested data latency and possible alerts misfiring due to latent data.
  • Root Cause: The failure was due to a large unexpected ingress of data to a scale unit.
  • Incident Timeline: 27 minutes - 1/19, 17:26 UTC through 1/19, 17:53 UTC
We understand that customers rely on Application Insights as a critical service and apologize for any impact this incident caused.

-Jeff

Initial Update: Tuesday, 19 January 2021 18:32 UTC

We are aware of issues within Application Insights and are actively investigating. Some customers in East US region may experience delayed or missed Log Search Alerts and Data Latency.
  • Next Update: Before 01/19 20:00 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Jeff