Experiencing Data Access Issue in Azure portal for Log Analytics - 04/13 - Resolved
Final Update: Tuesday, 13 April 2021 11:43 UTC We've confirmed that all systems are back to normal with no customer impact as of 04/13, 11:10 UTC. Our logs show the incident started on 04/13, 10:00 UTC and that during the 1hour & 10 minutes that it took resolve the issue some customers may have experienced data access issue, missed or delayed log search alerts in West Europe region Root Cause: The failure was due to one of our backened service Incident Timeline: 1 Hours & 10 minutes - 04/13, 10:00 UTC through 04/13, 11:10 UTC We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused. -DeepikaExperiencing delayed ingestion for Log Analytics in East US - 03/17 - Resolved
Final Update: Wednesday, 17 March 2021 01:54 UTC We've confirmed that all systems are back to normal with no customer impact as of 03/17, 01:45 UTC. Our logs show the incident started on 03/17, 00:42 UTC and that during the one hour that it took to resolve the issue approximately 50% customers in the East US region experienced data ingestion latency and possibly delayed or misfired alerts. Root Cause: The failure was due to a back end system reaching its operational threshold. Once the system was restarted and scaled out, the backlog of ingestion data began to drain. Incident Timeline: 1 hour and 3 minutes - 03/17, 00:42 UTC through 03/17, 01:45 UTC We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused. -Jack Update: Wednesday, 17 March 2021 01:39 UTC Root cause has been isolated to a back end system reaching its system limits which caused ingestion to back up and result in latency and possible missed or late-firing alerts. To address this issue we scaled out the back end service. The ingestion back up is mostly resolved and ingestion will shortly be back working as expected. Some customers may continue to experience data latency and improperly fired alerts. We estimate less than one hour before all latency in data and alerting is addressed. Next Update: Before 03/17 03:00 UTC -JackExperiencing Data Access and Latency issues in Azure Portal - 03/15 - Resolved
Final Update: Tuesday, 16 March 2021 12:46 UTC We've confirmed that all systems are back to normal with no customer impact as of 03/16, 12:00 UTC. Our logs show the incident started on 03/15, 11:10 UTC and that during the 1 day and 50 minutes that it took to resolve the issue some customers using Azure Monitor Service may have experienced intermittent data latency, data access, and incorrect alert activation in East US and West Europe region. Root Cause: The root cause has been isolated to failures in Azure Active Directory which was impacting all of Azure Monitor Service. Incident Timeline: 1 Day & 50 minutes - 03/15, 11:10 UTC through 03/16, 12:00 UTC We understand that customers rely on Azure Monitor as a critical service and apologize for any impact this incident caused. -Anmol Update: Tuesday, 16 March 2021 11:36 UTC Root cause has been isolated to failures in Azure Active Directory which was impacting all of Azure Monitor Service. Azure Active Directory is now recovering, though each service may recover completely at a different time, due to differences in the timing of refreshing Azure Active Directory tokens. Some customer using Azure Monitor Service may continue to experience intermittent data latency, data access and incorrect alert activation in East US and West Europe region. Work Around: None Next Update: Before 03/16 18:00 UTC -Madhav Update: Tuesday, 16 March 2021 03:23 UTC There is currently just one service within Azure Monitor that is still experiencing problems: Data ingestion: Some data gaps as well as continued delays in East US Next Update: Before 03/16 05:30 UTC -Jack Update: Monday, 15 March 2021 21:51 UTC Root cause has been isolated to failures in Azure Active Directory which was impacting all of Azure Monitor. Azure Active Directory is now recovering, though each service may recover completely at a different time, due to differences in the timing of refreshing Azure Active Directory tokens. Some customers may continue to experience challenges connecting to the data access API or with data latency. We estimate 1 - 2 hours before all problems are completely addressed. Next Update: Before 03/15 23:00 UTC -JackExperiencing Data Access Issue in Azure portal for Log Analytics - 04/03 - Resolved
Final Update: Saturday, 03 April 2021 13:44 UTC We've confirmed that all systems are back to normal with no customer impact as of 4/03, 12:15 UTC. Our logs show the incident started on 4/03, 09:20 UTC and that during the 2 hours & 55 minutes that it took to resolve the issue some customers may experience data access issue and delayed or missed alerts in East US 2 region. Root Cause: The failure was due to issues with one of our dependent service. Incident Timeline: 2 Hours & 55 minutes - 4/03, 09:20 UTC through 4/03, 12:15 UTC We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused. -Harshita Initial Update: Saturday, 03 April 2021 10:12 UTC We are aware of issues within Log Analytics and are actively investigating. Some customers may experience data access issue and delayed or missed alerts in East US 2 region. Work Around: None Next Update: Before 04/03 16:30 UTC We are working hard to resolve this issue and apologize for any inconvenience. -HarshitaExperiencing Data Access issue in Azure Portal for Many Data Types - 04/01 - Resolved
Final Update: Friday, 02 April 2021 05:47 UTC We've confirmed that all systems are back to normal with no customer impact as of 4/02, 04:30 UTC. Our logs show the incident started on 4/01, 21:20 UTC and that during the 7 Hours & 10 minutes that it took to resolve the issue some customers may have experienced data access issue, missed or delayed azure alerts and data ingestion latency issue. Root Cause: The failure was due to DNS outage. Incident Timeline: 7 Hours & 10 minutes - 4/01, 21:20 UTC through 4/02, 04:30 UTC We understand that customers rely on Azure Monitor service as a critical service and apologize for any impact this incident caused. -Harshita Update: Friday, 02 April 2021 03:10 UTC We continue to have residual effect in Azure monitor services due to DNS outage. Some customers in East US2 may still experience data access issue and missed/delayed Azure alerts. Customers in Central US region may still experience data ingestion latency. Work Around: None Next Update: Before 04/02 05:30 UTC -Anupama Update: Friday, 02 April 2021 01:34 UTC We continue to have residual effect in Azure monitor services due to DNS outage. Some customers in East US2 may still experience missed/delayed Azure alerts. The issue with data access and data ingestion has been recovered and services are healthy in East US. We currently have no estimate for resolution. Work Around: None Next Update: Before 04/02 03:00 UTC -Anupama Update: Thursday, 01 April 2021 23:46 UTC We continue to have issues within Azure monitor services due to DNS outage. Some customers in East US and East US2 continue to experience issues accessing data, issues with data ingestion and missed/delayed Azure alerts. We currently have no estimate for resolution. Work Around: None Next Update: Before 04/02 02:00 UTC -Anupama Initial Update: Thursday, 01 April 2021 22:29 UTC We are aware of issues within Azure monitoring services due to a DNS outage and we are actively investigating. Some customers may experience issues accessing data, issues with data ingestion and missed/delayed Azure alerts. Work Around: None Next Update: Before 04/02 00:30 UTC We are working hard to resolve this issue and apologize for any inconvenience. -AnupamaExperiencing Data Access Issue in Azure portal for Log Analytics - 03/31 - Resolved
Final Update: Wednesday, 31 March 2021 14:17 UTC We've confirmed that all systems are back to normal with no customer impact as of 03/31, 14:00 UTC. Our logs show the incident started on 03/31, 12:05 UTC and that during the 1 Hour & 55 minutes that it took to resolve the issue some customers may have experienced data access issue and delayed or missed alerts in East US 2 region. Root Cause: The failure was due to issues with one of our dependent service. Incident Timeline: 1 Hour & 55 minutes - 03/31, 12:05 UTC through 03/31, 14:00 UTC We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused. -Harshita Initial Update: Wednesday, 31 March 2021 13:03 UTC We are aware of issues within Log Analytics and are actively investigating. Some customers may experience data access issue and delayed or missed alerts in East US 2 region. Work Around: None Next Update: Before 03/31 16:30 UTC We are working hard to resolve this issue and apologize for any inconvenience. -HarshitaExperiencing Issues in Azure portal for Log Analytics and Service Map - 03/31 - Resolved
Final Update: Wednesday, 31 March 2021 07:37 UTC We've confirmed that all systems are back to normal with no customer impact as of 03/31, 07:30 UTC. Our logs show the incident started on 03/31, 04:44 UTC and that during the 2 hours 46 minutes that it took to resolve the issue some customers experienced data access issues, missed or delayed Log Search Alerts, service unavailable and/or experienced difficulties accessing data in Service Map for resources hosted in West Central US region. Root Cause: The failure was due to an outage in one of the dependent service. Incident Timeline: 2 Hours & 46 minutes - 03/31, 04:44 UTC through 03/31, 07:30 UTC We understand that customers rely on Application Insights and Azure Log Analytics as critical services and apologize for any impact this incident caused. -Harshita Initial Update: Wednesday, 31 March 2021 07:18 UTC We are aware of issues within Log Analytics and Service Map and are actively investigating. Some customers may have experienced data access issues, missed or delayed Log Search Alerts, service unavailable and/or experienced difficulties accessing data in Service Map for resources hosted in West Central US region. Work Around: None Next Update: Before 03/31 11:30 UTC We are working hard to resolve this issue and apologize for any inconvenience. -HarshitaIssues with registering subscriptions to microsoft.insights in Azure Portal - 03/30 - Resolved
Final Update: Tuesday, 30 March 2021 18:26 UTC We've confirmed that all systems are back to normal with no customer impact as of 03/30, 17:00 UTC. Our logs show the incident started on 03/22, 10:00 UTC and that during the 8 days and 7 hours that it took to resolve the issue some of the customers who have tried to register their subscriptions to microsoft.insights would have experienced a message stuck in the registering state. If the problem is still being experienced re-registering from portal will fix the issue. Root Cause: The failure was due to a deployment that happened for one of the backend services. Incident Timeline: 8 Days & 7 Hours - 03/22, 10:00 UTC through 03/30, 17:00 UTC We understand that customers rely on Application Insights as a critical service and apologize for any impact this incident caused. -JayadevExperiencing Data Access Issue in Azure portal for Log Analytics - 03/30 - Resolved
Final Update: Tuesday, 30 March 2021 10:43 UTC We've confirmed that all systems are back to normal with no customer impact as of 03/30, 10:15 UTC. Our logs show the incident started on 03/30, 08:50 UTC and that during the 1 Hour & 25 Minutes that it took to resolve the issue some customers may have experienced data access issue and delayed or missed alerts in West US 2 region. Root Cause: The failure was due to issues with one of the backend services. Incident Timeline: 1 Hours & 25 minutes - 03/30, 08:50 UTC through 03/30, 10:15 UTC We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused. -Harshita Initial Update: Tuesday, 30 March 2021 09:42 UTC We are aware of issues within Azure Log Analytics and are actively investigating. Some customers may experience data access issue and delayed or missed Log Search Alerts in West US 2 region. Work Around: None Next Update: Before 03/30 13:00 UTC We are working hard to resolve this issue and apologize for any inconvenience. -HarshitaExperiencing Data Access Issue in Azure portal for Log Analytics - 03/30 - Resolved
Final Update: Tuesday, 30 March 2021 15:32 UTC We've confirmed that all systems are back to normal with no customer impact as of 03/30, 14:55 UTC. Our logs show the incident started on 03/30, 14:05 UTC and that during the 50 minutes that it took to resolve the issue some customers may have experienced data access issue and delayed or missed alerts in South UK region. Root Cause: The failure was due to issues with one of our dependent service. Incident Timeline: 50 minutes - 03/30, 14:05 UTC through 03/30, 14:55 UTC We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused. -Mohini Initial Update: Tuesday, 30 March 2021 15:15 UTC We are aware of issues within Azure Log Analytics and are actively investigating. Some customers may experience data access issue and delayed or missed alerts in South UK region. Work Around: None Next Update: Before 03/30 17:30 UTC We are working hard to resolve this issue and apologize for any inconvenience. -Mohini