Freshcaller incident

Call Recording Failures

Minor Resolved View vendor source →

Freshcaller experienced a minor incident on November 11, 2020 affecting Inbound Calls and Outbound Calls and 1 more component, lasting 4h 24m. The incident has been resolved; the full update timeline is below.

Started
Nov 11, 2020, 09:06 PM UTC
Resolved
Nov 12, 2020, 01:30 AM UTC
Duration
4h 24m
Detected by Pingoru
Nov 11, 2020, 09:06 PM UTC

Affected components

Inbound CallsOutbound CallsInbound CallsOutbound CallsInbound CallsOutbound CallsInbound CallsOutbound Calls

Update timeline

  1. investigating Nov 11, 2020, 09:06 PM UTC

    Our monitoring systems have detected a potential issue with recordings. Our engineering team has been alerted and is actively investigating. We will update as soon as we have more information.

  2. investigating Nov 11, 2020, 09:35 PM UTC

    We are experiencing Call Recording Failures for a subset of ongoing calls. No new calls are affected. Calls created and still active from 8:54 am PT until 12:57 pm PT may experience timeouts resulting in an API 500 error if they attempt to record. Our team is actively investigating the issue. We will provide another update in 1 hour.

  3. investigating Nov 11, 2020, 10:45 PM UTC

    We continue to experience Call Recording Failures for a subset of active calls. No new calls are affected. Calls created and still active from 8:54 am PST until 12:57 pm PST may experience timeouts resulting in an API 500 error if they attempt to record. Calls attempted to be modified during this window may result in Errors or Dropped Calls. This issue has been identified and we are monitoring the situation to full recovery. We will provide another update in 2 hours or as soon as more information is made available.

  4. resolved Nov 12, 2020, 01:30 AM UTC

    We no longer experience Call Recording Failures for a subset of calls created between 8:54 AM until 12:57 PM Pacific Time on 11/11/2020. This issue is now resolved.