Experiencing Data Latency issue in Azure Portal for Many Data Types - 02/19 - Resolved

Published Feb 19 2021 01:06 PM 775 Views
Final Update: Friday, 19 February 2021 21:28 UTC

We've confirmed that all systems are back to normal with no customer impact as of 02/19, 21:17 UTC. Our logs show the incident started on 02/19, 20:24 UTC and that during the 53 minutes that it took to resolve the issue customers would have received 503 errors resulting in Data latency and data gaps as well as misfired alerts as a result of the data latency and gaps.
  • Root Cause: The failure was due to a backend component that became unhealthy.
  • Incident Timeline: 53 minutes - 02/19, 20:24 UTC through 02/19, 21:17 UTC
We understand that customers rely on Application Insights as a critical service and apologize for any impact this incident caused.

-Jeff

Initial Update: Friday, 19 February 2021 21:06 UTC

We are aware of issues within Application Insights in Japan West region and are actively investigating. Some customers may experience delayed or missed Log Search Alerts and Data Latency.
  • Work Around: None
  • Next Update: Before 02/19 22:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Jeff

%3CLINGO-SUB%20id%3D%22lingo-sub-2150475%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Latency%20issue%20in%20Azure%20Portal%20for%20Many%20Data%20Types%20-%2002%2F19%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2150475%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%20Friday%2C%2019%20February%202021%2021%3A28%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2002%2F19%2C%2021%3A17%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2002%2F19%2C%2020%3A24%20UTC%20and%20that%20during%20the%2053%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20customers%20would%20have%20received%20503%20errors%20resulting%20in%20Data%20latency%20and%20data%20gaps%20as%20well%20as%20misfired%20alerts%20as%20a%20result%20of%20the%20data%20latency%20and%20gaps.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20a%20backend%20component%20that%20became%20unhealthy.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%2053%20minutes%20-%2002%2F19%2C%2020%3A24%20UTC%20through%2002%2F19%2C%2021%3A17%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%20Friday%2C%2019%20February%202021%2021%3A06%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20aware%20of%20issues%20within%20Application%20Insights%20in%20Japan%20West%20region%20and%20are%20actively%20investigating.%20Some%20customers%20may%20experience%20delayed%20or%20missed%20Log%20Search%20Alerts%20and%20Data%20Latency.%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%2002%2F19%2022%3A30%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-2150475%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EApplication%20Insights%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Version history
Last update:
‎Feb 19 2021 01:38 PM
Updated by: