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 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 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. -HarshitaExperiencing Data Access Issue in Azure portal for Service Map - 02/23 - Resolved
Final Update: Thursday, 25 February 2021 19:55 UTC We've confirmed that all systems are back to normal with no customer impact as of 2/25, 18:40 UTC. Our logs show the incident started on 2/15 and that during the duration of ~10 days that it took to resolve the issue some customers experienced issues seeing performance data in Azure monitor when Azure mode is selected and 5xx errors while viewing performance data on browser. Root Cause: The failure was due to one of the back end services turning unhealthy after a deployment. Incident Timeline: 2/15 through 2/25, 18:40 UTC We understand that customers rely on Azure monitor for VM's as a critical service and apologize for any impact this incident caused. -Anupama Update: Thursday, 25 February 2021 04:22 UTC Root cause has been isolated to service turning unhealthy after incorrect deployment which was impacting performance data view in Azure monitor when Azure mode is selected. To address this issue engineers are rolling back the service to previous healthy state. Some customers who have VM's sending data to workspaces, continue to experience issues seeing performance data in Azure monitor when Azure mode is selected and 5xx errors while viewing performance data on browser. Work Around: None Next Update: Before 02/26 04:30 UTC -Anupama Update: Thursday, 25 February 2021 01:28 UTC Root cause has been isolated to service turning unhealthy after incorrect deployment which was impacting performance data view in Azure monitor when Azure mode is selected. To address this issue engineers are rolling back the service to previous healthy state. Some customers who have VM's sending data to workspaces, continue to experience issues seeing performance data in Azure monitor when Azure mode is selected and 5xx errors while viewing performance data on browser. Work Around: None Next Update: Before 02/25 05:30 UTC -Anupama Update: Thursday, 25 February 2021 00:01 UTC Root cause has been isolated to service turning unhealthy after incorrect deployment which was impacting performance data view in Azure monitor when Azure mode is selected. To address this issue we are rolling out a fix to the service. Some customers who have VM's sending data to workspaces, continue to experience issues seeing performance data in Azure monitor when Azure mode is selected and 5xx errors while viewing performance data on browser. Work Around: None Next Update: Before 02/25 02:30 UTC -Anupama Update: Wednesday, 24 February 2021 22:01 UTC We continue to investigate issues within Azure monitor for VM's. Preliminary investigation showed that the root cause was due to one of the back end component becoming inaccessible after a scheduled drill/test in EastUS2EUAP region. Further investigation shows that the root cause is due to regression that happened after a deployment on one of the back end services. Some customers who have VM's sending data to workspaces, continue to experience issues seeing performance data in Azure monitor when Azure mode is selected. Customers might also see 5xx errors while viewing the performance data on the portal. Work Around: None Next Update: Before 02/25 00:30 UTC -Anupama Update: Wednesday, 24 February 2021 12:02 UTC We continue to investigate issues within Service Map. Root cause is due to one of the backend component becoming inaccessible after a scheduled drill/test in EastUS2EUAP region. Some customers who have VM's sending data to EastUS2EUAP workspaces, continue to experience issues seeing performance data in Azure monitor when Azure mode is selected. Work Around: None Next Update: Before 02/25 00:30 UTC -Harshita Update: Wednesday, 24 February 2021 01:32 UTC We continue to investigate issues within Service Map. Root cause is due to one of the backend component becoming inaccessible after a scheduled drill/test in EastUS2EUAP region. Some customers who have VM's sending data to EastUS2EUAP workspaces, continue to experience issues seeing performance data in Azure monitor when Azure mode is selected. Work Around: None Next Update: Before 02/24 14:00 UTC -Anupama Update: Tuesday, 23 February 2021 21:22 UTC We continue to investigate issues within Service map. Root cause is due to one of the backend component becoming inaccessible after a scheduled drill/test in EastUS2EUAP region. Some customers who have VM's sending data to EastUS2EUAP workspaces, continue to experience issues seeing performance data in Azure monitor when Azure mode is selected. The issue started at 16:00 UTC Work Around: None Next Update: Before 02/23 23:30 UTC -AnupamaExperiencing Data Latency and Data Access issues for Azure Monitor
Final Update: Friday, 12 February 2021 06:05 UTC We've confirmed that all systems are back to normal with no customer impact as of 02/12, 05:24 UTC. Our logs show the incident started on 02/12, 01:52 UTC and that during the 3 hours & 32 minutes that it took to resolve the issue some customers may have experienced Data Latency, Data Access and delayed or misfired Alerts in West US region. Root Cause: The failure was due to one of our backend dependent service. Incident Timeline: 3Hours & 32 minutes - 02/12, 01:52 UTC through 02/12, 05:24 UTC We understand that customers rely on Application Insights as a critical service and apologize for any impact this incident caused. -Deepika Initial Update: Friday, 12 February 2021 01:35 UTC We are aware of issues within Azure Monitor Services and are actively investigating. Some customers in West US Region may experience Data Latency, Data Access and delayed or misfired Alerts. Next Update: Before 02/12 06:00 UTC We are working hard to resolve this issue and apologize for any inconvenience. -JayadevExperiencing Data Access issue in Azure Portal for Many Data Types - 02/08 - Resolved
Final Update: Monday, 08 February 2021 18:19 UTC We've confirmed that all systems are back to normal with no customer impact as of 02/08, 17:59 UTC. Our logs show the incident started on 02/08, 14:48 UTC and that during the 3 hours and 11 minutes that it took to resolve the issue some customers using Azure Monitor in US Gov Virginia and US Gov Arizona Regions experienced difficulties in attempting to access data. Additionally log search alerts may have been delayed or misfired. Root Cause: The failure was due to one of the backend dependent services. Incident Timeline: 3 Hours & 11 minutes - 02/08, 14:48 UTC through 02/08, 17:59 UTC We understand that customers rely on Application Insights as a critical service and apologize for any impact this incident caused. -Jayadev Initial Update: Monday, 08 February 2021 16:17 UTC We are aware of issues within Azure Monitor and are actively investigating. Some customers may experience Data access issue in Azure Portal in US Gov Virginia and US Gov Arizona regions with delayed or missed Log Search Alerts. Next Update: Before 02/08 20:30 UTC We are working hard to resolve this issue and apologize for any inconvenience. -JayadevData Gap issue in Azure Monitor Service - 02/01 - Resolved
Final Update: Monday, 01 February 2021 11:34 UTC We've confirmed that all systems are back to normal with no customer impact as of 02/01, 11:20 UTC. We have been tracking an issue in Azure Monitor services which may have impacted a subset of customers in regions Norway East, UAE North, Brazil South East, Germany West. Affected customers may have experienced some data gaps for their data ingested to some of Azure Monitor solutions but impact is very minimal. Root Cause: The failure was due to configuration changes in one of our dependent service. We understand that customers rely on Service Map as a critical service and apologize for any impact this incident caused. -Mohini Initial Update: Monday, 01 February 2021 10:28 UTC We have been tracking an issue in Azure Monitor services which might have impacted a subset of customers in regions Norway East, UAE North, Brazil South East, Germany West. Affected customer might see some data gaps for their data ingested to some of Azure Monitor solutions but impact is very minimal. We provide more information about this issue as we progress the investigation. Work Around: None Next Update: Before 02/02 10:30 UTC We are working hard to resolve this issue and apologize for any inconvenience. -MohiniExperiencing Data Access issue in Azure Portal - 12/10 - Resolved
Final Update: Thursday, 10 December 2020 22:29 UTC We've confirmed that all systems are back to normal with no customer impact as of 12/10, 21:45 UTC. Our logs show the incident started on 12/10, 20:45 UTC and that during the 1 hour that it took to resolve the issue some of customers in East US, EastUS2, South Central US, West Central US, Central Canada, South Africa North experienced data access issues and missed/delayed log search alerts. Root Cause: The failure was due to a recent deployment in one of the backend services. Incident Timeline: 1 hour - 12/10, 20:45 UTC through 12/10, 21:45 UTC We understand that customers rely on Azure monitor as a critical service and apologize for any impact this incident caused. -Anupama Initial Update: Thursday, 10 December 2020 21:42 UTC We are aware of issues within Azure monitor services and are actively investigating. Some customers in multiple regions may experience data access issues, delayed or missed Log Search Alerts. Work Around: None Next Update: Before 12/11 00:00 UTC We are working hard to resolve this issue and apologize for any inconvenience. -AnupamaExperiencing Latency and Data Loss issue in Azure Portal for Many Data Types - 11/28 - Resolved
Final Update: Saturday, 28 November 2020 15:29 UTC We've confirmed that all systems are back to normal with no customer impact as of 11/28, 14:07 UTC. Our logs show the incident started on 11/27, 22:00 UTC and that during the 14 hours and 07 minutes that it took to resolve the issue some customers may have experienced delayed or missed Log Search Alerts, Latency and Data Loss in South Africa North region. Root Cause: The issue was due to power outage in South Africa North region data centers. Incident Timeline: 14 Hours & 07 minutes - 11/27, 22:00 UTC through 11/28, 14:07 UTC We understand that customers rely on Application Insights as a critical service and apologize for any impact this incident caused. -Vyom Initial Update: Saturday, 28 November 2020 05:02 UTC We are aware of issues within Application Insights and are actively investigating. Due to power outage in data center, some customers may experience delayed or missed Log Search Alerts, Latency and Data Loss in South Africa North region. Work Around: none Next Update: Before 11/28 17:30 UTC We are working hard to resolve this issue and apologize for any inconvenience. -VyomExperiencing Data Access issue in Azure Portal for Many Data Types - 11/12 - Resolved
Final Update: Thursday, 12 November 2020 02:14 UTC We've confirmed that all systems are back to normal with no customer impact as of 11/12, 01:20 UTC. Our logs show that the incident started on 11/11, 23:50 UTC and that during the 1 hour and 30 minutes that it took to resolve the issue some of the customers experienced issues with missed or delayed Log Search Alerts or experienced difficulties accessing data for resources hosted in West US2 and North Europe. Root Cause: The failure was due to an issue in one of our backend service. Incident Timeline: 1 Hour & 30 minutes - 11/11, 23:50 UTC through 11/12, 1:20 UTC We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused. -Saika Initial Update: Thursday, 12 November 2020 01:35 UTC We are aware of issues within Log Analytics and are actively investigating. Some customers may experience issues with missed, delayed or wrongly fired alerts or experience difficulties accessing data for resources hosted in West US2 and North Europe. Work Around: None Next Update: Before 11/12 06:00 UTC We are working hard to resolve this issue and apologize for any inconvenience. -Saika