Issue with 500 Errors on Porting Request Submissions

Incident Report for Twilio

Resolved

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

Posted Oct 22, 2026 - 12:30 PDT

Monitoring

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.

Posted Oct 22, 2026 - 12:03 PDT

Identified

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 porting@twilio.com at this time.

We will provide another update in 2 hours or as soon as additional information is available.

Posted Oct 22, 2026 - 11:16 PDT

Update

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.

Posted Oct 22, 2026 - 10:24 PDT

Investigating

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.

Posted Oct 22, 2026 - 10:10 PDT

This incident affected: PHONE NUMBERS.