Freshcaller experienced a minor incident on February 15, 2022 affecting Inbound Calls and Outbound Calls and 1 more component, lasting 6h 40m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Feb 15, 2022, 11:06 PM UTC
Our service provider investigating degraded processing with input=“speech dtmf” or input=“speech”. Sessions affected by this would have their processing terminated early (and move on to the next TwiML verb in the document) We expect to provide another update in 1 hour or as soon as more information becomes available
- investigating Feb 16, 2022, 12:13 AM UTC
The issue causing degraded processing with input=“speech dtmf” or input=“speech” has been identified. Our engineering teams are actively working to resolve the issue. We expect to provide another update in 1 hour or as soon as more information becomes available.
- investigating Feb 16, 2022, 01:19 AM UTC
The issue causing degraded processing with input=“speech dtmf” or input=“speech” has been identified. Our engineering teams are actively working to resolve the issue. We expect to provide another update in 2 hours or as soon as more information becomes available.
- investigating Feb 16, 2022, 03:17 AM UTC
The issue causing degraded processing with input=“speech dtmf” or input=“speech” has been identified. Our engineering teams are actively working to resolve the issue. We expect to provide another update in 4 hours or as soon as more information becomes available.
- investigating Feb 16, 2022, 03:43 AM UTC
We are observing recovery in our functionality to collect digits or transcribe speech during a call. We will continue monitoring the service to ensure a full recovery. We will provide another update in 2 hours or as soon as more information becomes available.
- resolved Feb 16, 2022, 05:46 AM UTC
The issue causing degraded processing with input=“speech dtmf” or input=“speech” has been resolved and it is operating normally at this time.