%3CLINGO-SUB%20id%3D%22lingo-sub-925951%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Access%20issue%20in%20Azure%20Portal%20for%20Many%20Data%20Types%20-%2010%2F22%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-925951%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%2022%20October%202019%2007%3A52%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2010%2F22%2C%2004%3A30%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2010%2F21%2C%2023%3A20%20UTC%20and%20that%20during%20the%205%20hours%2010%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20customers%20would%20have%20experienced%20Data%20latency%2C%20Data%20access%20and%20Alerting%20failures%20in%20West%20Europe%20region.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20connections%20getting%20timed%20out%20with%20Azure%20storage%20in%20West%20Europe%20region.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%205%20Hours%20%26amp%3B%2010%20minutes%20-%2010%2F21%2C%2023%3A20%20UTC%20through%2010%2F22%2C%2004%3A30%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-Rama%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%20Tuesday%2C%2022%20October%202019%2004%3A56%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%20access%20and%20Data%20latency%20issue%20in%20West%20Europe%20region.%20We%20are%20working%20to%20establish%20the%20start%20time%20for%20the%20issue%2C%20initial%20findings%20indicate%20that%20the%20problem%20began%20at%2010%2F22%20~00%3A10%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%2010%2F22%2009%3A00%20UTC%3C%2FLI%3E%3C%2FUL%3E-Rama%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%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-925951%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EApplication%20Insights%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Tuesday, 22 October 2019 07:52 UTC

We've confirmed that all systems are back to normal with no customer impact as of 10/22, 04:30 UTC. Our logs show the incident started on 10/21, 23:20 UTC and that during the 5 hours 10 minutes that it took to resolve the issue customers would have experienced Data latency, Data access and Alerting failures in West Europe region.
  • Root Cause: The failure was due to connections getting timed out with Azure storage in West Europe region.
  • Incident Timeline: 5 Hours & 10 minutes - 10/21, 23:20 UTC through 10/22, 04:30 UTC
We understand that customers rely on Application Insights as a critical service and apologize for any impact this incident caused.

-Rama

Update: Tuesday, 22 October 2019 04:56 UTC

We continue to investigate issues within Application Insights. Root cause is not fully understood at this time. Some customers continue to experience Data access and Data latency issue in West Europe region. We are working to establish the start time for the issue, initial findings indicate that the problem began at 10/22 ~00:10 UTC. We currently have no estimate for resolution.
  • Work Around: None
  • Next Update: Before 10/22 09:00 UTC
-Rama