Experiencing Data Latency issue in Azure Portal for Many Data Types - 10/07 - Resolved
Final Update: Wednesday, 07 October 2020 20:09 UTC We've confirmed that all systems are back to normal with no customer impact as of 10/7, 19:00 UTC. Our logs show the incident started on 10/7, at approximately 18:30 UTC and that during the 30 minutes that it took to resolve the issue most Application Insights and Log Analytics customers experienced outages with various services. Root Cause: The failure was due to a back-end networking issue that caused problems with a large number of Azure services. Incident Timeline: 0 Hours & 30 minutes - 10/7, 18:30 UTC through 10/7, 19:00 UTC We understand that customers rely on Application Insights and Log Analytics as critical services and apologize for any impact this incident caused. -Jack CantwellExperiencing Data Access issue in Azure Portal for Many Data Types - 09/28 - Resolved
Final Update: Tuesday, 29 September 2020 03:04 UTC We've confirmed that all systems are back to normal with no customer impact as of 09/29, 02:30 UTC. Our logs show the incident started on 09/28, 21:00 UTC . Root Cause: AAD outage which was impacting data access. Incident Timeline: 5 Hours & 30 minutes - 09/28 ,21:00 UTC through 09/29, 02:30 UTC We understand that customers rely on Application Insights as a critical service and apologize for any impact this incident caused. -Vincent Update: Tuesday, 29 September 2020 01:56 UTC Root cause has been isolated to AAD outage which was impacting data access. Live Metrics, Distributed Tracing and Log Search Alerting are now working as expected. Customers in all Public & US gov region may experience issues in Availability Test and Work Item Integration. Next Update: Before 09/29 04:00 UTC -Vincent Initial Update: Monday, 28 September 2020 23:31 UTC We are aware of issues within Application Insights and are related to AAD. Customers in all Public & US gov region may experience Data Access issues and issues with Availability Test, Live Metrics, Work Item Integration, Distributed Tracing and Log Search Alerting. Next Update: Before 09/29 02:00 UTC We are working hard to resolve this issue and apologize for any inconvenience. -VincentExperiencing issues in Azure Portal for Many Data Types in SUK- 09/14 - Resolved
Final Update: Tuesday, 15 September 2020 01:42 UTC We've confirmed that all systems are back to normal with no customer impact as of 9/15, 00:41 UTC. Our logs show the incident started on 9/14 13:54 UTC and that during the 10 hours and 47 minutes that it took to resolve the issue customers experienced data loss and data latency which may have resulted in false and missed alerts. Root Cause: The failure was due to a cooling failure at our data center that resulted in shutting down portions of the data center. Incident Timeline: 10 Hours & 47 minutes - 9/14 13:54 UTC through 9/15, 00:41 UTC We understand that customers rely on Application Insights as a critical service and apologize for any impact this incident caused. -Ian Update: Tuesday, 15 September 2020 01:19 UTC Root cause has been isolated to cooling failures and subsequent shutdowns in our data center which were impacting storage and our ability to access and insert data. Our infrastructure has been brought back online. We are making progress with brining the final storage devices back online. Customers should start to see signs of recover soon. Work Around: None Next Update: Before 09/15 05:30 UTC -Ian Update: Monday, 14 September 2020 20:14 UTC Starting at approximately 14:00 UTC on 14 Sep 2020, a single Zone in UK South has experienced a cooling failure. As a result, Storage, Networking and Compute resources were shut down as part of our automated processes to preserve the equipment and prevent damage. As a result the Azure Monitoring Services have experienced missed or latent data which is causing false and missed alerts. Mitigation for the cooling failure is currently in progress. An estimated time for resolution of this issue is still unknown. We apologize for the inconvenience. Work Around: None Next Update: Before 09/15 00:30 UTC -Ian Update: Monday, 14 September 2020 16:28 UTC We continue to investigate issues within Azure Monitoring Services. Root cause is related to an ongoing storage account issue. Some customers continue to experience missed or latent data which is causing false and missed alerts. We are working to establish the start time for the issue, initial findings indicate that the problem began at 9/14 13:35 UTC. We currently have no estimate for resolution. Work Around: None Next Update: Before 09/14 19:30 UTC -Ian Initial Update: Monday, 14 September 2020 14:44 UTC We are aware of issues within Azure Monitoring Services and are actively investigating. There is an outage on storage event in UK South which caused multiple services to be impacted. Work Around: None Next Update: Before 09/14 19:00 UTC We are working hard to resolve this issue and apologize for any inconvenience. -MohiniExperiencing Alerting failure for alerts and action rules - 08/29 - Mitigated
Final Update: Saturday, 29 August 2020 14:15 UTC We've confirmed that all systems are back to normal with no customer impact as of 08/29, 14:05 UTC. Our logs show the incident started on 08/29, 09:15 UTC and that during the 4 hours 50 minutes that it took to resolve some of customers may experience failures accessing alerts and action rules for the resources. Alerting notifications are not impacted. Root Cause: The failure due to one of dependent service miss configuration . Incident Timeline: 4 Hours & 50 minutes - 08/29, 09:15 UTC through 08/29, 14:05 UTC We understand that customers rely on Alerts as a critical service and apologize for any impact this incident caused. -Subhash Update: Saturday, 29 August 2020 13:46 UTC We continue to investigate issues within alerting management. Some customers may experience failures accessing alerts and action rules for resources. Alerting notifications are not impacted. The problem began at 08/29 09:15 AM UTC. Work Around: None Next Update: Before 08/29 18:00 UTC -Subhash Update: Saturday, 29 August 2020 12:02 UTC We continue to investigate issues within alerting management. Some customers may experience failures accessing alerts and action rules for resources. Alerting notifications are not impacted. The problem began at 08/29 09:15 AM UTC. Work Around: None Next Update: Before 08/29 16:00 UTC -SubhashExperiencing Alerting failure issue in Azure Portal for Many Data Types - 08/28 - Resolved
Final Update: Friday, 28 August 2020 23:39 UTC We've confirmed that all systems are back to normal with no customer impact as of 8/28, 21:30 UTC. Our logs show the incident started on 8/28, 17:30 UTC and that during the 4 hours that it took to resolve the issue, customers in the West US Region could have experience delayed or lost Diagnostic Logs. Customers using App Services Logs in Public Preview could have also experienced missed or delayed logs in all US and Canada Regions. Root Cause: The failure was due to a backend dependency. Incident Timeline: 4 Hours - 8/28, 17:30 UTC through 8/28, 21:30 UTC We understand that customers rely on Azure Monitor as a critical service and apologize for any impact this incident caused. -Eric SingletonExperiencing Data Latency in Azure portal for Log Alerts - 08/06 - Resolved
Final Update: Thursday, 06 August 2020 13:30 UTC We've confirmed that all systems are back to normal with no customer impact as of 8/6, 13:00 UTC. Our logs show the incident started on 8/06, 10:00 UTC and that during the 3 hours that it took to resolve the issue customers could have experienced a delay in alerting. Root Cause: The failure was due to some backend dependencies. Incident Timeline:3 Hours - 8/06, 10:00 UTC through 8/06, 13:00 UTC We understand that customers rely on Azure Monitor as a critical service and apologize for any impact this incident caused. -Eric SingletonExperiencing Latency, Data Gap and Alerting failure for Azure Monitoring - 07/18 - Resolved
Final Update: Saturday, 18 July 2020 15:37 UTC We've confirmed that all systems are back to normal with no customer impact as of 07/18, 11:40 UTC. Our logs show the incident started on 07/18, 07:50 UTC and that during the 3 hours 50 minutes that it took to resolve the issue some customers may have experienced Data access, Data latency, Data Loss, incorrect Alert activation, missed or delayed Alerts and Azure Alerts created during the impact duration may have been available to be viewed with some delay in the Azure portal in multiple regions. Root Cause: The failure was due to an issue in one of our dependent services. Incident Timeline: 3 Hours & 50 minutes - 07/18, 7:50 UTC through 07/18, 11:40 UTC We understand that customers rely on Application Insights as a critical service and apologize for any impact this incident caused. -Anmol Update: Saturday, 18 July 2020 11:17 UTC We continue to investigate issues within Azure Monitoring services. Some customers continue to experience Data access, Data latency and Data Loss, incorrect Alert activation, missed or delayed Alerts and Azure Alerts created during the impact duration may not be available to be viewed in the Azure portal in multiple regions. We are working to establish the start time for the issue, initial findings indicate that the problem began at 07/18 ~07:58 UTC. We currently have no estimate for resolution. Work Around: None Next Update: Before 07/18 14:30 UTC -Anmol Initial Update: Saturday, 18 July 2020 08:58 UTC We are aware of issues within Application Insights and Log Analytics and are actively investigating. Some customers may experience Data access issues in the Azure portal, Incorrect Alert Activation, Latency and Data Loss in multiple regions. Work Around: None. Next Update: Before 07/18 11:00 UTC We are working hard to resolve this issue and apologize for any inconvenience. -MadhuriExperiencing Data Latency in Azure portal for Log Alerts - 06/15 - Resolved
Final Update: Monday, 15 June 2020 08:23 UTC We've confirmed that all systems are back to normal with no customer impact as of 06/15, 04:54 UTC. Our logs show the incident started on 06/15, 03:15 UTC and that during the 1 hour and 39 minutes that it took to resolve the issue some customers using Activity Logs Alerts might have experienced delayed alerts. Root Cause: The failure was due to one of our dependent services. Incident Timeline: 1 Hour & 39 minutes - 06/15, 03:15 UTC through 06/15, 04:54 UTC We understand that customers rely on Activity Log Alerts as a critical service and apologize for any impact this incident caused. -SanthoshExperiencing Alerting failure for Log Alerts - 06/11 - Resolved
Final Update: Thursday, 11 June 2020 12:48 UTC We've confirmed that all systems are back to normal with no customer impact as of 06/11, 12:26 UTC. Our logs show the incident started on 06/09, 08:26 UTC and that during the 2 days 4 hours that it took to resolve the issue some the of customers experienced missing alerts in azure portal globally. Root Cause: The failure was due to one our back end services. Incident Timeline: 2 days 4 Hours - 06/09, 08:26 UTC through 06/11, 12:26 UTC We understand that customers rely on Log Alerts as a critical service and apologize for any impact this incident caused. -SyedExperiencing Alerting failure for Activity Log Alerts - 06/09 - Resolved
Final Update: Wednesday, 10 June 2020 09:09 UTC We've confirmed that all systems are back to normal with no customer impact as of 06/09, 20:00 UTC. Our logs show the incident started on 05/19, 00:00 UTC and that during the 21 days and 20 hours that it took to resolve the issue some customers fail to receive their Azure Alerts into external ITSM systems.This outage might have affected customers that have added a new ITSM action or updated their existing ITSM action via Azure Portal since 19 May 2020 issue. Root Cause: The failure was due to one of our back end services. Incident Timeline: 21 days 20 Hours - 05/19, 00:00 UTC through 06/09, 20:00 UTC We understand that customers rely on Activity Log Alerts as a critical service and apologize for any impact this incident caused. -Syed Initial Update: Tuesday, 09 June 2020 14:38 UTC We are aware of the issue with ITSM action that Since 19 May 2020 some of ITSM Connector customers fail to receive their Azure Alerts into external ITSM systems.This outage affects customers that have added a new ITSM action or updated their existing ITSM action via Azure Portal since 19 May 2020.The fix for the broken ITSM action management experience was deployed on 09 June 2020. We are also deploying a fix for the corrupted ITSM actions, to be expected by 15 June 2020. Work Around: Customers can re-create the corrupted actions. Next Update: Before 06/10 15:00 UTC We are working hard to resolve this issue and apologize for any inconvenience. -Syed