We have now been able to successfully restore access to all available call recordings and voicemails.
Posted almost 2 years ago. Mar 03, 2017 - 10:14 PST
We have successfully restored access to nearly all voicemails. Call recordings are continuing to appear progressively and we expect this job will be completed some time tomorrow. We will update this incident again once that import is complete.
Posted almost 2 years ago. Mar 02, 2017 - 16:12 PST
Our engineers are working along with our telecom provider to restore access to yesterday's missing recordings as soon as possible. Recordings are already starting to become available progressively. We expect all recordings to be available by the end of day tomorrow. We will update this incident again either once completed or if there is a new estimate.
Posted almost 2 years ago. Mar 01, 2017 - 15:49 PST
Talkdesk is now recovering from the earlier outage. We are in the process of backfilling recordings which will take some time. We will update with more precise information when this is available.
Posted almost 2 years ago. Feb 28, 2017 - 14:47 PST
The continuing outage at AWS is now affecting inbound and outbound calls.
The latest update from AWS is:
Update at 11:35 AM PST: The service updates are below. We continue to experience high error rates with S3 in US-EAST-1, which is impacting various AWS services. We are working hard at repairing S3, believe we understand root cause, and are working on implementing what we believe will remediate the issue.
Posted almost 2 years ago. Feb 28, 2017 - 11:40 PST
Problems remain with Amazon Web Services (AWS) affecting many areas of Talkdesk including some inbound calls. We have added a new temporary phone number if you need to call us for Support: +1 855-622-5515
Posted almost 2 years ago. Feb 28, 2017 - 10:49 PST
Due to the current incident with AWS, as well as Call Recordings, Voicemails and Greeting Messages in IVRs may also be affected.
Posted almost 2 years ago. Feb 28, 2017 - 10:32 PST
The issue with accessing recordings continues. This is caused by an incident with AWS. This is their latest update:
"We've identified the issue as high error rates with S3 in US-EAST-1, which is also impacting applications and services dependent on S3. We are actively working on remediating the issue."
Posted almost 2 years ago. Feb 28, 2017 - 10:23 PST
We seeing errors with Recordings due to problems with a vendor. More updates soon.
Posted almost 2 years ago. Feb 28, 2017 - 10:09 PST