This article is contributed. See the original author and article here.
Update: Saturday, 24 October 2020 08:04 UTC
Root cause has been isolated to a backend infrastructure component that was accidentally deleted. We have recovered the component and waiting for complete propagation of the restored configuration. Customers may continue to experience data gaps and latency in East US2 region.
- Work Around: None
- Next Update: Before 10/24 20:30 UTC
Update: Saturday, 24 October 2020 04:24 UTC
Root cause has been isolated to a backend infrastructure component that was accidentally deleted. We have recovered the component and waiting for complete propagation of the restored configuration.
Root cause has been isolated to a backend infrastructure component that was accidentally deleted. We have recovered the component and waiting for complete propagation of the restored configuration.
- Work Around: None
- Next Update: Before 10/24 08:30 UTC
Update: Saturday, 24 October 2020 03:18 UTC
Root cause has been isolated to a backend infrastructure component that was accidentally deleted. We have recovered the component and waiting for complete propagation of the restored configuration.
Root cause has been isolated to a backend infrastructure component that was accidentally deleted. We have recovered the component and waiting for complete propagation of the restored configuration.
- Work Around:
- Next Update: Before 10/24 06:30 UTC
Update: Saturday, 24 October 2020 02:55 UTC
We continue to investigate issues that impacts Workspace-enabled Application Insights resource only. Root cause is not fully understood at this time. Customers might experience data gaps and latency. We are working to establish the start time for the issue, initial findings indicate that the problem began at <10/23 ~19:05 UTC>.
We continue to investigate issues that impacts Workspace-enabled Application Insights resource only. Root cause is not fully understood at this time. Customers might experience data gaps and latency. We are working to establish the start time for the issue, initial findings indicate that the problem began at <10/23 ~19:05 UTC>.
- Work Around:
- Next Update: Before 10/24 05:00 UTC
Initial Update: Saturday, 24 October 2020 02:51 UTC
We are aware of issues within Application Insights and are actively investigating. Some customers may experience Latency and Data Loss.
-Chandar
We are aware of issues within Application Insights and are actively investigating. Some customers may experience Latency and Data Loss.
- Work Around:
- Next Update: Before 10/24 05:00 UTC
-Chandar
Brought to you by Dr. Ware, Microsoft Office 365 Silver Partner, Charleston SC.
Recent Comments