Update: Thursday, 09 June 2022 09:37 UTC
We are still working with our dependency team to mitigate the issue, where our backend services need to be rebalanced to handle the traffic. Some customers continue to experience data latency and possibly delayed or missed alerts. Initial findings indicate that the problem began at 06/09 ~00:10 UTC. We currently have no estimate for resolution.
- Next Update: Before 06/09 13:00 UTC
-Surya
Update: Thursday, 09 June 2022 07:47 UTC
We are still working with our dependency team to mitigate the issue, where our backend services need to be rebalanced to handle the traffic. Some customers continue to experience data latency and possibly delayed or missed alerts. Initial findings indicate that the problem began at 06/09 ~00:10 UTC. We currently have no estimate for resolution.
- Next Update: Before 06/09 10:00 UTC
-Surya
Update: Thursday, 09 June 2022 05:45 UTC
We are still working with our dependency team to mitigate the issue, where our backend services need to be rebalanced to handle the traffic. Some customers continue to experience data latency and possibly delayed or missed alerts. Initial findings indicate that the problem began at 06/09 ~00:10 UTC. We currently have no estimate for resolution.
- Next Update: Before 06/09 08:00 UTC
-Surya
Update: Thursday, 09 June 2022 04:07 UTC
We are still working with our dependency team to mitigate the issue, where our
backend services need to be rebalanced to handle the traffic.
- Next Update: Before 06/09 06:00 UTC
-Vignesh
Update: Thursday, 09 June 2022 02:14 UTC
We continue to investigate issues within Application Insights. Root cause is not fully understood at this time. Some customers continue to experience data latency and possibly delayed or missed alerts. We are working to establish the start time for the issue, initial findings indicate that the problem began at 06/09 ~00:10 UTC. We currently have no estimate for resolution.
- Next Update: Before 06/09 04:30 UTC
-Robin Paul