Experiencing 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 Alerting Latency for Activity Log Alerts - 03/29 - Resolved
Final Update: Tuesday, 30 March 2021 03:30 UTC We've confirmed that all systems are back to normal with no customer impact as of 03/30 03:00 UTC. Our logs show the incident started on 03/29, 18:00 UTC and that during the 9 hours that it took to resolve the issue some customers using Azure Monitor experienced issues with delay in Activity Logs and also experienced issues with delayed Activity Log Alerts. Root Cause: The failure was due to issues with one of the backend services. Incident Timeline: 9 Hours - 03/29, 18:00 UTC through 03/30 03:00 UTC We understand that customers rely on Activity Log Alerts as a critical service and apologize for any impact this incident caused. -Jayadev Initial Update: Monday, 29 March 2021 23:23 UTC We are aware of issues within Activity Log Alerts and are actively investigating. Some customers using Azure Monitor may experience issues with delay in Activity Logs and also experience issues with delay in Activity Log Alerts. Next Update: Before 03/30 03:30 UTC We are working hard to resolve this issue and apologize for any inconvenience. -JayadevExperiencing ITSM connectior failures in East US region - 02/19 - Resolved
Final Update: Friday, 19 February 2021 07:44 UTC We've confirmed that all systems are back to normal with no customer impact as of 02/19, 07:16 UTC. Our logs show the incident started on 02/19, 05:19 UTC and that during the 1 hour and 57 minutes that it took to resolve the issue some customers using Azure Monitor Alerts who may have experienced errors when using ITSM connector in East US region to create the work items in external ticketing systems. Root Cause: The failure was due to an issue with one of our dependent service. Incident Timeline: 1 Hour & 57 minutes - 02/19, 05:19 UTC through 02/19, 07:16 UTC We understand that customers rely on Azure Monitor as a critical service and apologize for any impact this incident caused. -MohiniExperiencing delay in Activity logs and Activity Log Alerts - 02/12 - Resolved
Final Update: Friday, 12 February 2021 17:30 UTC We've confirmed that all systems are back to normal with no customer impact as of 02/12, 17:00 UTC. Our logs show the incident started on 02/12, 12:15 UTC and that during the 4 hours and 45 minutes that it took to resolve the issue some customers may have experienced issues with delay in Activity logs and delayed Activity log alerts. Alerts would have eventually fired. Root Cause: The failure was due to issues with one of the backend services. Incident Timeline: 4 Hours & 45 minutes - 02/12, 12:15 UTC through 02/12, 17:00 UTC We understand that customers rely on Activity Logs and Activity Log Alerts as a critical service and apologize for any impact this incident caused. -JayadevExperiencing 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 Latency in Activity Logs - 01/29 - Resolved
Final Update: Saturday, 30 January 2021 00:45 UTC We've confirmed that all systems are back to normal with no customer impact as of 1/30, 00:30 UTC. Our logs show the incident started on 1/29, 02:00 UTC and that during the 22 hours and 30 minutes that it took to resolve the issue some customers could have experienced Data Latency with Activity Logs that are generated from Azure Resource manager as well as delayed Activity Log Alerts. Root Cause: The failure was due to a backend dependency. Incident Timeline: 22 Hours & 30 minutes - 1/29, 02:00 UTC through 1/30, 00:30 UTC We understand that customers rely on Azure Monitor as a critical service and apologize for any impact this incident caused. -Eric Singleton Update: Friday, 29 January 2021 22:27 UTC Root cause has been isolated to a misconfiguration from a backend dependency. To address this issue the team is currently implementing a hotfix to decrease the latency. Some customers may experience Data Latency with Activity Logs that are generated from Azure Resource Manager as well as delayed Activity Log Alerts. Work Around: None Next Update: Before 01/30 02:30 UTC -Eric Singleton Initial Update: Friday, 29 January 2021 20:36 UTC We are aware of issues within Activity Logs and are actively investigating. Some customers may experience Data Latency with Activity Logs that are generated from Azure Resource Manager. Investigation points to a start time of 1/29 02:00 UTC. Work Around: None Next Update: Before 01/29 23:00 UTC We are working hard to resolve this issue and apologize for any inconvenience. -Eric SingletonExperiencing errors when accessing alerts in Azure Monitor - 01/27 - Resolved
Final Update: Wednesday, 27 January 2021 10:28 UTC We've confirmed that all systems are back to normal with no customer impact as of 01/27, 10:00 UTC. Our logs show the incident started on 01/27, 09:15 UTC and that during the 45 minutes that it took to resolve the issue some of customers may have received errors when accessing alerts. The alerts notifications were not impacted. Root Cause: We determined that a recent deployment task impacted instances of the backend service which became unhealthy, causing these errors. Incident Timeline: 45 minutes - 01/27, 09:15 UTC through 01/27, 10:00 UTC We understand that customers rely on Azure Monitor as a critical service and apologize for any impact this incident caused. -AnmolExperiencing failures while querying API's in Azure Activity Logs - 12/12 - Resolved
Final Update: Saturday, 12 December 2020 16:46 UTC We've confirmed that all systems are back to normal with no customer impact as of 12/12, 16:15 UTC. Our logs show the incident started on 12/11, ~12:30 UTC and that during the 27 hours 45 min that it took to resolve the issue a subset of customers experienced failures while querying API's in Azure Activity Logs. Root Cause: The failure was due to one of the backend services reaching operational threshold and becoming unhealthy. Incident Timeline: 27 Hours & 45 minutes - 12/11, 12:30 UTC through 12/12, 16:15 UTC We understand that customers rely on Azure Activity Logs as a critical service and apologize for any impact this incident caused. -Anupama Update: Saturday, 12 December 2020 15:17 UTC We continue to investigate issues within Activity Logs. Some customers may experience failures while querying API's in Azure Activity Logs. Our initial findings indicate that the problem began at 12/11 ~12:30 UTC. We currently have no estimate for resolution. Work Around: None Next Update: Before 12/12 19:30 UTC -SandeepExperiencing 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/22 - Resolved
Final Update: Sunday, 22 November 2020 11:11 UTC We've confirmed that all systems are back to normal with no customer impact as of 11/22, 07:57 UTC. Our logs show the incident started on 11/22, 07:14 UTC and that during the 43 minutes that it took to resolve the issue some of the customers using Azure Alerts may have experienced missed or delayed alerts and notifications in China Gov Cloud and US gov Cloud. Root Cause: The failure was due to an issue with dependent backend service. Incident Timeline: 43 minutes - 11/22, 07:14 UTC through 11/22, 07:57 UTC We understand that customers rely on Application Insights as a critical service and apologize for any impact this incident caused. -Harshita