Some Fuse applications are experiencing degradation

Update timeline

1. investigating Jul 26, 2024, 04:03 PM UTC

   A subset of Fuse applications may be experiencing degradation when handling input prompts in IVR flows. We have all necessary resources engaged and will restore service as soon as possible..

2. identified Jul 26, 2024, 04:42 PM UTC

   We have successfully isolated the fault zone and are working through additional troubleshooting steps to identify the source of the disruption. All resources continue to be engaged until this is identified and resolved..

3. identified Jul 26, 2024, 04:45 PM UTC

   We have identified the issue and are working to introduce a fix. Our target is within the next 15 minutes..

4. identified Jul 26, 2024, 04:57 PM UTC

   We are introducing a fix across a collective of supporting resources. Incremental recovery will be experienced over the next 30-45 minutes. In parallel we are pursuing options to accelerate our full restoration time..

5. identified Jul 26, 2024, 05:18 PM UTC

   We have encountered a disruption to our restoration method and are pursuing alternative options..

6. identified Jul 26, 2024, 05:39 PM UTC

   We have identified the fault zone, have tested a fix in our preproduction environment, and are coordinating the best option to release to production..

7. identified Jul 26, 2024, 06:06 PM UTC

   We are continuing our investigation to determine the most appropriate means of applying an identified fix..

8. identified Jul 26, 2024, 06:29 PM UTC

   We have determined the best course of action to fix this issue. This approach is estimated to take 2 hours to implement. We are investigating alternative options with quicker resolution times in the interim. .

9. identified Jul 26, 2024, 06:58 PM UTC

   We are continuing to work on a fix for this incident..

10. identified Jul 26, 2024, 07:22 PM UTC

    We are implementing a fix and will be monitoring recovery shortly..

11. monitoring Jul 26, 2024, 07:26 PM UTC

    We have observed recovery from the fix and are monitoring..

12. identified Jul 26, 2024, 08:04 PM UTC

    Our previously released fix resolved the majority of user experiences, but some configurations were still encountering errors. We have identified the remaining issue and are implementing a fix..

13. monitoring Jul 26, 2024, 08:13 PM UTC

    We have implemented a secondary fix and are seeing recovery. We will continue to monitor the results..

14. resolved Jul 26, 2024, 08:30 PM UTC

    This issues has been resolved. We have observed sustained recovery since our latest fix..