Twilio incident: Caller ID Name Failures

1. resolvedAug 19, 2026, 19:41 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.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Twilio's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• DigitalOcean: Major Service Interruption in MKC1Critical · Aug 19, 2026, 11:10 UTC
• Elasticsearch: Elasticsearch 9.5.1: false-positive matches in certain boolean queriesMajor · Aug 14, 2026, 09:22 UTC
• Supabase: 401 errors due to JWT rejectionsMinor · Aug 14, 2026, 02:23 UTC
• Telnyx: Programmable Wireless data loss in AustraliaMinor · Aug 17, 2026, 19:27 UTC
• SendGrid: SMS Delivery Receipt Delays from Twilio to Telecall BrazilMinor · Aug 19, 2026, 06:08 UTC
• LiveKit: Investigating delayed session data ingestion on Cloud DashboardMinor · Aug 19, 2026, 19:33 UTC
• SendGrid: SMS Delivery Delays from Twilio to T-Mobile GermanyMinor · Aug 19, 2026, 19:36 UTC

How often does Twilio have incidents?

Twilio reported 501 incidents in the last 90 days, 2 of them major or critical. A typical incident lasted 5h 49m. See Twilio's uptime and incident history