Freshcaller incident

Elevated Rate for HTTP 401 Errors Across Multiple Twilio Products

Minor Resolved View vendor source →

Freshcaller experienced a minor incident on November 19, 2020 affecting Public API and Public API and 1 more component, lasting 1h 6m. The incident has been resolved; the full update timeline is below.

Started
Nov 19, 2020, 08:44 PM UTC
Resolved
Nov 19, 2020, 09:50 PM UTC
Duration
1h 6m
Detected by Pingoru
Nov 19, 2020, 08:44 PM UTC

Affected components

Public APIPublic APIPublic APIPublic API

Update timeline

  1. investigating Nov 19, 2020, 08:44 PM UTC

    Our monitoring systems have detected a potential issue with APIs returning 4XX errors across various platforms. Our engineering team has been alerted and is actively investigating. We will update as soon as we have more information.

  2. investigating Nov 19, 2020, 09:00 PM UTC

    We are continuing to investigate this issue.

  3. investigating Nov 19, 2020, 09:14 PM UTC

    Twilio observed elevated HTTP 401 Errors between 11:34 and 12:43 Pacific Time on 11/19/2020. During this period, about 0.3% percentage of API requests failed and customers may have received 401 errors. The issue has been resolved and we are closely monitoring the issue and will provide another update in 30 minutes.

  4. resolved Nov 19, 2020, 09:50 PM UTC

    HTTP 401 Errors has been resolved and API requests are operating normally at this time.