Final Update: Thursday, 09 June 2022 11:04 UTC
We've confirmed that all systems are back to normal with no customer impact as of 6/9, 10:35 UTC. Our logs show the incident started on 6/9, 00:10 UTC and that during the 10 hours and 25 minutes that it took to resolve the issue. Some customers may have experienced data latency and possibly delayed or missed alerts.
We've confirmed that all systems are back to normal with no customer impact as of 6/9, 10:35 UTC. Our logs show the incident started on 6/9, 00:10 UTC and that during the 10 hours and 25 minutes that it took to resolve the issue. Some customers may have experienced data latency and possibly delayed or missed alerts.
- Root Cause: The failure was due to dependent backend service.
- Incident Timeline: 10 Hours & 25 minutes - 6/9, 00:10 UTC through 6/9, 10:35 UTC
-Surya
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.
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
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.
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
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.
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
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
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.
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
Updated Jun 09, 2022
Version 7.0