Twilio incident: Issue with 500 Errors on Porting Request Submissions

Affected components

• PHONE NUMBERS

1. resolvedOct 22, 2026, 19:30 UTC

   We are no longer experiencing an issue with 500 errors on porting request submissions. This incident has been resolved.

2. monitoringOct 22, 2026, 19:03 UTC

   We have started seeing recovery for the issue with 500 errors on porting request submissions. We will continue to monitor to ensure a full recovery. We expect to provide another update in 30 minutes or as soon as more information becomes available.

3. identifiedOct 22, 2026, 18:16 UTC

   We have identified the issue with 500 Errors on Porting Request Submissions. This issue is affecting wireless only submissions on the Port-in US Toll-free and Port a number tabs. The Port-in US Local tab is still currently functional and the Port-in API is still functional. We are actively working to resolve this issue. If customers have an urgent porting request, they can submit it manually by sending an email to [email protected] at this time. We will provide another update in 2 hours or as soon as additional information is available.

4. investigatingOct 22, 2026, 17:24 UTC

   We are observing an issue with 500 Errors on Porting Request Submissions. This issue is affecting the Port-in US Toll-free and Port a number tabs. The Port-in US Local tab is still currently functional and the Port-in API is still functional. We expect to provide another update in 1 hour or as soon as more information becomes available.

5. investigatingOct 22, 2026, 17:10 UTC

   Our monitoring systems have detected a potential issue with porting request submissions returning 500 errors. Our engineers have been alerted and are investigating. We will provide an update when we have more details.

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.

• Elasticsearch: 403 error when trying to access Autoops in newly created serverless projectsMajor · Oct 22, 2026, 11:19 UTC
• Cloudflare: Network Error Log Processing UnavailableMajor · Oct 22, 2026, 16:30 UTC
• HashiCorp Vault: GitHub and Other VCS workloads experiencing intermittent issuesMajor · Oct 22, 2026, 17:15 UTC
• Cloudflare: Delayed audit log delivery for WARP and Zero Trust servicesMajor · Oct 22, 2026, 17:32 UTC
• SendGrid: SMS Delivery Delays and Failures from a Subset of Twilio Alphanumeric Sender IDs to Mobile ChinaMinor · Oct 9, 2026, 06:42 UTC
• SendGrid: Voice Call Post Dial Delay from a Subset of Twilio Phone Numbers to ThailandMinor · Oct 12, 2026, 11:53 UTC
• SendGrid: SMS Delivery Delays and Failures Between a Subset of Twilio Long Codes and Multiple Networks in ItalyMinor · Oct 19, 2026, 16:53 UTC
• SendGrid: Voice Call Post Dial Delay From a Subset of Twilio Phone Numbers to IsraelMinor · Oct 21, 2026, 03:10 UTC
• Akamai: Web Security Analytics, Reporting and Configuration Deployment IssuesMinor · Oct 21, 2026, 15:30 UTC
• SendGrid: SMS Delivery Failures from United Kingdom to a Subset of Twilio Long CodesMinor · Oct 21, 2026, 16:10 UTC

How often does Twilio have incidents?

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