Freshcaller incident

Latency and Timeout Errors with Twilio Rest API Impacting Multiple Products

Minor Resolved View vendor source →

Freshcaller experienced a minor incident on December 17, 2021 affecting Public API and Public API and 1 more component, lasting 1h 37m. The incident has been resolved; the full update timeline is below.

Started
Dec 17, 2021, 03:35 PM UTC
Resolved
Dec 17, 2021, 05:12 PM UTC
Duration
1h 37m
Detected by Pingoru
Dec 17, 2021, 03:35 PM UTC

Affected components

Public APIPublic APIPublic APIPublic API

Update timeline

  1. investigating Dec 17, 2021, 03:35 PM UTC

    We've become aware of a potential issue with Programmable SMS and MMS. Our engineering team has been alerted and is actively investigating. We will update as soon as we have more information.

  2. investigating Dec 17, 2021, 03:48 PM UTC

    We are currently investigating an issue with latency and timeout errors on Twilio's Rest API. Multiple products are impacted. Our engineers are working on the issue, and we will provide another update in the next 30 minutes or when more information becomes available.

  3. investigating Dec 17, 2021, 04:09 PM UTC

    We are experiencing elevated HTTP 500 errors for SMS, MMS, Phone Numbers, Console, Programmable Wireless and Rest API. Customers may experience sign-up errors, the Buy a Numbers Page in an Endless Loop and unable to place orders for IoT products. Our engineers are working on the issue, and we will provide another update in the next 30 minutes or when more information becomes available.

  4. investigating Dec 17, 2021, 04:13 PM UTC

    We are experiencing elevated HTTP 500 errors for SMS, MMS, Phone Numbers, Console, Programmable Wireless and Rest API. Customers may experience sign-up errors, the Buy a Numbers Page in an Endless Loop and unable to place orders for IoT products. Our engineers are working on the issue, and we will provide another update in the next 30 minutes or when more information becomes available

  5. investigating Dec 17, 2021, 04:31 PM UTC

    We have identified the issue causing elevated HTTP 500 errors for SMS, MMS, Phone Numbers, Console, IoT and Rest API. Our Engineers have worked on mitigating the issue and we are seeing recovery of product and services. The next update will be in 30 minutes

  6. investigating Dec 17, 2021, 04:42 PM UTC

    We are observing recovery to the API degradation causing elevated HTTP 500 errors for SMS, MMS, Phone Numbers, Console, IoT and Rest API. We will continue monitoring the service to ensure a full recovery. We will provide another update in 30 minutes or as soon as more information becomes available

  7. resolved Dec 17, 2021, 05:12 PM UTC

    Our engineering team has confirmed the issue is now fully resolved and the affected products and services are now operating normally.