Twilio incident: Users are unable to create a SIP Trunking Phone Number Resource

1. resolvedJul 14, 2026, 17:50 UTC

   Users are no longer experiencing unexpected 404 errors when attempting to create a SIP Trunking Phone Number Resource, this issue have 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.

• Sentry: Error ingestion degraded in DE regionCritical · Jul 14, 2026, 14:44 UTC
• Grafana Cloud: Mimir Partial Write OutageMajor · Jul 14, 2026, 17:09 UTC
• Mux: Video Playback IssuesMajor · Jul 14, 2026, 17:09 UTC
• ElevenLabs: Speech Engine Conversation FailuresMajor · Jul 14, 2026, 17:27 UTC
• LaunchDarkly: LaunchDarkly is operational but customer action may be requiredMinor · Jul 10, 2026, 16:00 UTC
• DigitalOcean: Serverless Inference - Gemma4 Latency Issues Causing Timeouts & Slow ResponsesMinor · Jul 13, 2026, 19:04 UTC
• CircleCI: Issues with network routing for Mac jobsMinor · Jul 13, 2026, 21:52 UTC
• Grafana Cloud: Issue with Dashboard Views Being RegisteredMinor · Jul 14, 2026, 08:10 UTC
• Linode: Service Issue - Linode API/CLIMinor · Jul 14, 2026, 12:21 UTC
• GitHub: Incident with WebhooksMinor · Jul 14, 2026, 17:38 UTC

How often does Twilio have incidents?

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