Twilio incident

Caller ID Name Failures

Minor Resolved View vendor source →

Twilio experienced a minor incident on August 19, 2026 affecting Origination US1, lasting 2h 31m. The incident has been resolved; the full update timeline is below.

Started
Aug 19, 2026, 05:09 PM UTC
Resolved
Aug 19, 2026, 07:41 PM UTC
Duration
2h 31m
Detected by Pingoru
Aug 19, 2026, 05:09 PM UTC

Affected components

Origination US1

Update timeline

  1. investigating Aug 19, 2026, 05:09 PM UTC

    We are experiencing an issue looking up Caller ID Name (CNAM) information for Trunking Originating calls in the us2 region. Customers may also experienced increased post dial delay (PDD). Our engineers are working to resolve the issue. We will provide another update in 1 hour or as soon as more information becomes available.

  2. identified Aug 19, 2026, 06:06 PM UTC

    The issue looking up Caller ID Name (CNAM) information for Trunking Originating calls in the us2 region has been identified. We are actively working with our Engineering Team to resolve the issue. We expect to provide another update in 1 hour or as soon as more information becomes available.

  3. identified Aug 19, 2026, 06:55 PM UTC

    The issue looking up Caller ID Name (CNAM) information for Trunking Originating calls in the us2 region has been identified. We are actively working with our Engineering Team to resolve the issue. We expect to provide another update in 2 hours or as soon as more information becomes available.

  4. monitoring Aug 19, 2026, 07:11 PM UTC

    Caller ID Name (CNAM) information look up for Trunking Originating calls in the us2 region is now operating normally. We will continue to monitor for system stability. We'll provide another update in 30 minutes or as soon as more information becomes available.

  5. resolved Aug 19, 2026, 07:41 PM UTC

    The issue has been resolved and Caller ID Name (CNAM) information look up for Trunking Originating calls in the us2 region is operating normally at this time.