Experiencing Data Access issue in Azure Portal for Many Data Types - 03/20 - Resolved

Published Apr 06 2021 11:28 AM 436 Views
Final Update: Saturday, 20 March 2021 09:53 UTC

We've confirmed that all systems are back to normal with no customer impact as of 03/20, 05:50 UTC. Our logs show the incident started on 03/20, 03:45 UTC and that during the 2 hours 05 minutes that it took to resolve the issue some customers may have experienced intermittent data access issues and intermittent data latency in East US and West Europe regions. Customers may also have experienced missed or delayed alerts in these regions.
  • Root Cause: We determined that a backend service which the Application Insight service is dependent upon, became unhealthy and was unable to complete requests from Application Insights. 
  • Incident Timeline: 02 Hours & 05 minutes - 03/20, 03:45 UTC through 03/20, 05:50 UTC
We understand that customers rely on Application Insights as a critical service and apologize for any impact this incident caused.

-Anmol

Update: Saturday, 20 March 2021 06:16 UTC

Root cause has been isolated to a backend service which was impacting East US and West Europe. Some Customers may experience intermittent data access issues and intermittent data latency. Customers may also experience missing or delayed alerts.
  • Work Around: None
  • Next Update: Before 03/20 09:30 UTC
-Anmol

Initial Update: Saturday, 20 March 2021 05:03 UTC

We are aware of issues within Application Insights and are actively investigating. Some Customers may experience intermittent data access issues and intermittent data latency in EUS region. Customers may also experience missing or delayed alerts in this region.
  • Work Around: None
  • Next Update: Before 03/20 11:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Mohini

%3CLINGO-SUB%20id%3D%22lingo-sub-2224351%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Access%20issue%20in%20Azure%20Portal%20for%20Many%20Data%20Types%20-%2003%2F20%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2224351%22%20slang%3D%22en-US%22%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%3EFinal%20Update%3C%2FU%3E%3A%20Saturday%2C%2020%20March%202021%2009%3A53%20UTC%3CBR%20%2F%3E%3CDIV%20style%3D%22%22%3E%3CBR%20%2F%3E%3C%2FDIV%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2003%2F20%2C%2005%3A50%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2003%2F20%2C%2003%3A45%20UTC%20and%20that%20during%20the%202%20hours%2005%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20some%20customers%20may%20have%20experienced%20intermittent%20data%20access%20issues%20and%20intermittent%20data%20latency%20in%20East%20US%20and%20West%20Europe%20regions.%20Customers%20may%20also%20have%20experienced%20missed%20or%20delayed%20alerts%20in%20these%20regions.%3CSPAN%20style%3D%22font-size%3A%2014px%3B%22%3E%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20We%20determined%20that%20a%20backend%20service%20which%20the%20Application%20Insight%20service%20is%20dependent%20upon%2C%20became%20unhealthy%20and%20was%20unable%20to%20complete%20requests%20from%20Application%20Insights.%26nbsp%3B%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%2002%20Hours%20%26amp%3B%2005%20minutes%20-%2003%2F20%2C%2003%3A45%20UTC%20through%2003%2F20%2C%2005%3A50%20UTC%3CBR%20%2F%3E%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-Anmol%3CBR%20%2F%3E%3C%2FSPAN%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%20Saturday%2C%2020%20March%202021%2006%3A16%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3ERoot%20cause%20has%20been%20isolated%20to%20a%20backend%20service%20which%20was%20impacting%20East%20US%20and%20West%20Europe.%20Some%20Customers%20may%20experience%20intermittent%20data%20access%20issues%20and%20intermittent%20data%20latency.%20Customers%20may%20also%20experience%20missing%20or%20delayed%20alerts.%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%2003%2F20%2009%3A30%20UTC%3C%2FLI%3E%3C%2FUL%3E-Anmol%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%20Saturday%2C%2020%20March%202021%2005%3A03%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20aware%20of%20issues%20within%20Application%20Insights%20and%20are%20actively%20investigating.%26nbsp%3BSome%20Customers%20may%20experience%20intermittent%20data%20access%20issues%20and%20intermittent%20data%20latency%20in%20EUS%20region.%20Customers%20may%20also%20experience%20missing%20or%20delayed%20alerts%20in%20this%20region.%3C%2FDIV%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%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%2003%2F20%2011%3A30%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3CBR%20%2F%3E-Mohini%3C%2FDIV%3E%3CHR%20style%3D%22border-top-color%3Alightgray%22%20%2F%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2224351%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EApplication%20Insights%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ELog%20Search%20Alerts%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Version history
Last update:
‎Mar 20 2021 03:09 AM
Updated by: