Twilio incident: IncomingPhoneNumbers API Failures

1. resolvedAug 19, 2026, 16:58 UTC

   We are no longer experiencing 5xx errors for IncomingPhoneNumbers API affecting Hosted Numbers. This incident has been resolved.

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
• Telnyx: AI Assistants with Data Locality Australia FailingMajor · Aug 19, 2026, 14:28 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
• SendGrid: SMS Delivery Failures from a Subset of Twilio Long Codes to Bell Aliant CanadaMinor · Aug 19, 2026, 09:40 UTC
• Supabase: Sign-in failures for `signInWithIdToken` (OIDC) logins on free-tier projectsMinor · Aug 19, 2026, 12:47 UTC
• Cursor: Increased error rates for Composer 2.5Minor · Aug 19, 2026, 12:52 UTC
• Linear: Delayed actions for Linear agent and loops automationsMinor · Aug 19, 2026, 15:26 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