Experiencing Data Access Issue in Azure portal for Log Analytics - 10/02 - Resolved
Final Update: Thursday, 03 October 2019 03:55 UTC We've confirmed that all systems are back to normal with no customer impact as of 10/3, 03:45 UTC. Our logs show the incident started on 10/2, 23:45 UTC and that during the 4 hours that it took to resolve the issue any customers in USGov Virginia or services dependent on querying Azure Log Analytics data experienced an inability to query that data. Root Cause: The failure was due to a middle-tier system authentication failure. Incident Timeline: 4 Hours & 0 minutes We understand that customers rely on Azure Log Analytics and associated services as a critical service and apologize for any impact this incident caused. -Jeff Update: Thursday, 03 October 2019 01:39 UTC Root cause has been isolated to a middle tier authentication issue which is impacting the ability for customers and components to query log analytics data in USGov Virginia region. Engineers are working on isolating and updating authentication information. Work Around: None Next Update: Before 10/03 04:00 UTC -Jeff Update: Thursday, 03 October 2019 00:23 UTC We continue to investigate issues within Log Analytics in the USGov Virginia region. Root cause is not fully understood at this time. Customers in the region will continue to experience errors including 502 when attempting to query Log Analytics data. Initial findings indicate that the problem began at <10/02 ~23:45 UTC>. We currently have no estimate for resolution. Work Around: None Next Update: Before 10/03 02:30 UTC -Jeff Initial Update: Wednesday, 02 October 2019 23:56 UTC We are aware of issues within Log Analytics and are actively investigating. Some customers may experience failed queries for data. Work Around: None at this time Next Update: Before 10/03 02:00 UTC We are working hard to resolve this issue and apologize for any inconvenience. -JeffExperiencing Data Access issue in Azure Portal for Log Analytics - 08/19 - Resolved
Final Update: Monday, 19 August 2019 09:19 UTC We've confirmed that all systems are back to normal with no customer impact as of 08/19, 07:15 UTC. Our logs show the incident started on 08/19, 05:50 UTC and that during the 1 hour 25 minutes that it took to resolve the issue 15% of customers in South Central US, France Central and North Europe regions experienced data access issues in the Azure Portal and degraded performance when queried through API. Root Cause: The failure was due to an issue with one of our dependent service. Incident Timeline: 1 hours 25 minutes - 08/19, 05:50 UTC through 08/19, 07:15 UTC We understand that customers rely on Azure Log Analytics and Log Search Alerts as a critical service and apologize for any impact this incident caused. -Anmol Initial Update: Monday, 19 August 2019 06:49 UTC We are aware of issues within Log Analytics and Log Search alert and are actively investigating. Some customers in South Central US may experience data access issue in the azure portal and when queried through API. Next Update: Before 08/19 09:00 UTC We are working hard to resolve this issue and apologize for any inconvenience. -AnmolExperiencing Alerting failure for Log Search Alerts in Mooncake - 06/28 - Resolved
Final Update: Friday, 28 June 2019 11:50 UTC We've confirmed that all systems are back to normal with no customer impact as of 06/28, 06:45 UTC. Our logs show the incident started on 06/28, 05:25 UTC and that during the 1 hour 20 minutes that it took to resolve the issue all the customers in China - Mooncake region experienced alerting failures. Root Cause: The failure was due to the issue in one of our dependent services. Incident Timeline: 1 Hour & 20 minutes - 06/28, 05:25 UTC through 06/28 06:45 UTC We understand that customers rely on Log Search Alerts as a critical service and apologize for any impact this incident caused. -Anmol[Fairfax] Experiencing Data Access issue in App Insights and Log Analytics - 06/21 - Resolved
Final Update: Friday, 21 June 2019 03:48 UTC We've confirmed that all systems are back to normal with no customer impact as of 6/21, 3:40 AM UTC. Our logs show the incident started on 6/21, 1:32 AM UTC and that during the ~2 hours that it took to resolve the issue, all customers in Fairfax ( USGOV) region experienced Data access issues. Root Cause: The failure was due to invalid configuration file preventing requests to reach their proper backend service. Incident Timeline: 2 Hours & 10 minutes - M/D, 6/21,1:32 AM UTC through 6/21,3:40 AM UTC We understand that customers rely on Application Insights and Log analytics as a critical service and apologize for any impact this incident caused. -Anupama Initial Update: Friday, 21 June 2019 02:44 UTC We are aware of issues within Application Insights and Log Analytics and we are actively investigating. All customers in Fairfax ( USGOV region) may experience Data Access issues. Work Around: None Next Update: Before 06/21 05:00 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/30 - Resolved
Final Update: Saturday, 30 March 2019 03:23 UTC We've confirmed that all systems are back to normal with no customer impact as of 3/30, 3:20 AM UTC. Our logs show the incident started on 3/30, 2:56 UTC and that during the ~20 min that it took to resolve the issue some of the customers in south-east Asia might have experienced data access issue in Azure portal. Root Cause: The failure was due to the issues in one of our dependency service. Incident Timeline: 20 minutes - 3/30, 2:56 UTC through 3/30, 3:20 UTC We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused. -Anupama Initial Update: Saturday, 30 March 2019 02:56 UTC We are aware of issues within Log Analytics and are actively investigating. Some customers may experience issues while accessing their data on Azure portal. Query performance and API's will also be affected. Work Around: none Next Update: Before 03/30 06:00 UTC We are working hard to resolve this issue and apologize for any inconvenience. -AnupamaExperiencing Data Access Issue in Azure portal for Log Analytics - 02/27 - Resolved
Final Update: Wednesday, 27 February 2019 22:18 UTC We've confirmed that all systems are back to normal with no customer impact as of 02/27, 22:18 UTC. Our logs show the incident started on 02/27, 12:30 UTC and that during the ~9hr 35m hours that it took to resolve the issue most of the USGov customers would have experienced Data Access issues in Azure Log analytics. Root Cause: The failure was due to one of our internal services impacted due to the Network outage happened in Fairfax this morning. Incident Timeline: 9 Hours & 35 minutes - 02/27, 12:30 UTC through 02/27, 22:05 UTC We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused. -Vishal Update: Wednesday, 27 February 2019 21:43 UTC Root cause has been isolated to one of our internal service which is impacting Data access/Querying in Azure Log analytics. To address this issue we are fixing this through a deployment. Most of US Gov customers may experience data access/querying data in Azure Log analytics and we estimate in next ~1hour before all USGov users Data Access issues in Azure Log Analytics would be addressed. Work Around: NA Next Update: Before 02/28 00:00 UTC -Vishal Initial Update: Wednesday, 27 February 2019 14:19 UTC We are aware of issues within Log Analytics and are actively investigating. Initial investigation points to ongoing outage related to virtual machines in USGov Virginia region. Some customers in USGov Virginia region may experience Data Access issues in azure portal. Work Around: None Next Update: Before 02/27 16:30 UTC We are working hard to resolve this issue and apologize for any inconvenience. -RamaExperiencing Data Latency issue in Azure Portal for Many Data Types - 09/03 - Resolved
Final Update: Thursday, 03 September 2020 22:36 UTC We've confirmed that all systems are back to normal with no customer impact as of 09/03, 21:56 UTC. Our logs show the incident started on 09/03, 09:30 UTC and that during the 12 hours and 26 minutes that it took to resolve the issue some customers might have experienced intermittent data latency, data gaps and incorrect alert activation in West Europe region. Root Cause: The issue was due to hardware failure in one of the region's data centers affecting the network. Incident Timeline: 12 Hours & 26 minutes - 09/03, 09:30 UTC through 09/03, 21:56 UTC We understand that customers rely on Application Insights and Azure Log Analytics as critical services and apologize for any impact this incident caused. -Saika Update: Thursday, 03 September 2020 20:00 UTC Root cause has been isolated to a hardware failure in one of the region's data centers affecting the network and systems are still catching up to get back to normal. Some customers may still continue to experience intermittent data latency, data gaps and incorrect alert activation in West Europe region. Next Update: Before 09/04 00:00 UTC -Saika Update: Thursday, 03 September 2020 15:30 UTC We continue to investigate issues within Application Insights and Azure Log Analytics. Some customers continue to experience intermittent data latency, data gaps and incorrect alert activation in West Europe region. The initial findings suggest that the issue began at 09/03 ~09:30 UTC. Work Around: None Next Update: Before 09/03 20:30 UTC -Sandeep Update: Thursday, 03 September 2020 12:38 UTC We continue to investigate issues within Application Insights and Azure Log Analytics in West Europe region. Root cause is not fully understood at this time. Some customers continue to experience intermittent data latency, data gaps and incorrect alert activation. We are working to establish the start time for the issue, initial findings indicate that the problem began at 09/03 ~09:30 UTC. We currently have no estimate for resolution. Work Around: None Next Update: Before 09/03 15:00 UTC -Rama Initial Update: Thursday, 03 September 2020 10:34 UTC We are aware of issues with Data Latency within Application Insights and Log Analytics in West Europe region and are actively investigating. Some customers may experience intermittent data latency, data gaps and incorrect alert activation. Work Around: None Next Update: Before 09/03 14:00 UTC We are working hard to resolve this issue and apologize for any inconvenience. -SandeepExperiencing Data Access Issue in Azure portal for Log Analytics - 01/31 - Resolved
Final Update: Saturday, 01 February 2020 00:44 UTC We've confirmed that all systems are back to normal with no customer impact as of 01/31, 22:56 UTC. Our logs show the incident started on 01/31, 20:30 UTC and that during the 2 hours 26 minutes that it took to resolve the issue some customers might have experienced issues while querying data or might have seen failures related to log search alerts. Root Cause: The failure was due to .recent configuration change on a dependent service was causing down stream impact to the service. Incident Timeline: 2 Hours & 26 minutes - 01/31, 20:30 UTC through 01/31, 22:56 UTC We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused. -Subhash Initial Update: Friday, 31 January 2020 22:15 UTC We are aware of issues within Log Analytics and are actively investigating. Some customers in West US may experience issues with Data access from Azure portal , query failures in Log Analytics and delayed or missed alerts in Log search alerts. Work Around: Next Update: Before 02/01 02:30 UTC We are working hard to resolve this issue and apologize for any inconvenience. -SubhashExperiencing Query and Alerting Issues in West Europe for Azure Monitor - 12/18 - Resolved
Final Update: Wednesday, 18 December 2019 20:52 UTC We've confirmed that all systems are back to normal with no customer impact at present. Our logs show the incident started on 12/18, 18:00 UTC and that during the 1 hour 15 minutes that it took to resolve the issue some customers experienced data access and alerting failures. Root Cause: The failure was due to memory issue in underlying infrastructure. Incident Timeline: 1 Hour & 15 minutes - 12/18, 18:00 UTC through 12/18, 19:15 UTC We understand that customers rely on Azure Monitor as a critical service and apologize for any impact this incident caused. -Arvind Initial Update: Wednesday, 18 December 2019 18:38 UTC We are aware of issues within Azure Monitor and are actively investigating. Some customers may experience query and alerting failures against the data stored in West Europe region. Work Around: Next Update: Before 12/18 21:00 UTC We are working hard to resolve this issue and apologize for any inconvenience. -Arvind