Plum Voice - Notice history

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

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

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.

We have observed recovery from the fix and are monitoring.

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

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.

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

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

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

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.

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

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.

We've identified and resolved an issue affecting autoscaling of Plum Fuse services. This has been resolved 11:19 AM EST.