Freshcaller incident

Degraded Performance

Minor Resolved View vendor source →

Freshcaller experienced a minor incident on May 4, 2021 affecting Inbound Calls and Inbound Calls and 1 more component, lasting 5h 41m. The incident has been resolved; the full update timeline is below.

Started
May 04, 2021, 01:51 PM UTC
Resolved
May 04, 2021, 07:32 PM UTC
Duration
5h 41m
Detected by Pingoru
May 04, 2021, 01:51 PM UTC

Affected components

Inbound CallsInbound CallsInbound CallsInbound Calls

Update timeline

  1. investigating May 04, 2021, 01:51 PM UTC

    We are observing call failures to UK phone numbers. We are currently working with our carrier partner to resolve the issue. We expect to provide another update as soon as more information becomes available.

  2. identified May 04, 2021, 02:17 PM UTC

    The issue causing inbound call failures to a subset of UK phone numbers has been identified. We are actively working with our carrier partner to resolve the issue. We expect to provide another update as soon as more information becomes available.

  3. investigating May 04, 2021, 03:15 PM UTC

    The issue causing inbound call problems to a subset of Twilio UK phone numbers has been identified. We are continuing to actively work with our carrier partner to resolve the issue. More updates to follow.

  4. investigating May 04, 2021, 05:24 PM UTC

    The issue causing inbound call problems to a subset of Twilio UK phone numbers has been identified. We are continuing to actively work with our carrier partner to resolve the issue. We’ll follow up with more information as soon as we have it.

  5. investigating May 04, 2021, 05:51 PM UTC

    We have started seeing recovery for inbound calls to a subset of Twilio UK phone numbers. We will continue to monitor to ensure a full recovery. More updates to follow.

  6. resolved May 04, 2021, 07:32 PM UTC

    Our carrier partner confirmed that the issue causing inbound call failures to a subset of Twilio UK phone numbers had been resolved since 10:19 AM Pacific Time, and the service has been operational throughout the monitoring period. The incident is now resolved.