%3CLINGO-SUB%20id%3D%22lingo-sub-1207078%22%20slang%3D%22en-US%22%3EExperiencing%20issues%20in%20Azure%20Monitoring%20Services%20in%20East%20US-%2003%2F03%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1207078%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%3CU%3EFinal%20Update%3C%2FU%3E%3A%20Tuesday%2C%2003%20March%202020%2018%3A51%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20as%20of%2003%2F03%2C%2018%3A59%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2003%2F03%2C%2015%3A42%20UTC%20and%20that%20during%20the%203%20hours%2017minutes%20that%20it%20took%20to%20resolve%20the%20issue%20customers%20may%20have%20experienced%20ingestion%20delay%2C%20gaps%20in%20data%2C%20data%20access%20issues%2C%20delayed%20or%20missed%20or%20misfired%20log%20search%20alerts%20and%20availabilty%20tests%20failing%20in%20East%20US%20region.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20Azure%20outage%20cuased%20by%20thermal%20issues%20which%20impacted%20storage%20and%20network.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%203%20Hours%20%26amp%3B%2017%20minutes%20-%2003%2F03%2C%2015%3A42%20UTC%20through%2003%2F03%2C%2018%3A59%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20understand%20that%20customers%20rely%20on%20Azure%20Monitoring%20Services%20as%20a%20critical%20service%20and%20apologize%20for%20any%20impact%20this%20incident%20caused.%3CBR%20%2F%3E%3CBR%20%2F%3E-Sindhu%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%3CDIV%20style%3D%22%22%3E%3CDIV%20style%3D%22%22%3EInitial%20Update%3A%20Tuesday%2C%2003%20March%202020%2016%3A30%20UTC%3C%2FDIV%3E%3CDIV%20style%3D%22%22%3E%3CBR%20%2F%3E%3C%2FDIV%3E%3CDIV%20style%3D%22%22%3EWe%20are%20aware%20of%20issues%20within%20Azure%20Monitoring%20Services.%20Customers%20may%20experience%20ingestion%20delay%2C%20data%20access%20issues%2C%20delayed%20or%20missed%20or%20misfired%20log%20search%20alerts%20and%20availabilty%20tests%20failing%20in%20East%20US%20region.%20Initial%20investigation%20points%20to%20Azure%20outage%20due%20to%20impact%20on%20virtual%20machines%20in%20East%20US%20region.%26nbsp%3B%3C%2FDIV%3E%3CDIV%20style%3D%22%22%3EWork%20Around%3A%20None%3C%2FDIV%3E%3CDIV%20style%3D%22%22%3ENext%20Update%3A%20Before%2003%2F03%2020%3A30%20UTC%3C%2FDIV%3E%3CDIV%20style%3D%22%22%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3C%2FDIV%3E%3CDIV%20style%3D%22%22%3E-Sindhu%3C%2FDIV%3E%3C%2FDIV%3E%3CHR%20style%3D%22border-top-color%3Alightgray%22%20%2F%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1207078%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EApplication%20Insights%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EAzure%20Log%20Analytics%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ELog%20Search%20Alerts%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Tuesday, 03 March 2020 18:51 UTC

We've confirmed that all systems are back to normal as of 03/03, 18:59 UTC. Our logs show the incident started on 03/03, 15:42 UTC and that during the 3 hours 17minutes that it took to resolve the issue customers may have experienced ingestion delay, gaps in data, data access issues, delayed or missed or misfired log search alerts and availabilty tests failing in East US region.
  • Root Cause: The failure was due to Azure outage cuased by thermal issues which impacted storage and network.
  • Incident Timeline: 3 Hours & 17 minutes - 03/03, 15:42 UTC through 03/03, 18:59 UTC
We understand that customers rely on Azure Monitoring Services as a critical service and apologize for any impact this incident caused.

-Sindhu

Initial Update: Tuesday, 03 March 2020 16:30 UTC

We are aware of issues within Azure Monitoring Services. Customers may experience ingestion delay, data access issues, delayed or missed or misfired log search alerts and availabilty tests failing in East US region. Initial investigation points to Azure outage due to impact on virtual machines in East US region. 
Work Around: None
Next Update: Before 03/03 20:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Sindhu