OFFLINE
Awaiting data
Twilio service status
MinorresolvedCloud

Issue with 500 Errors on Porting Request Submissions

We are no longer experiencing an issue with 500 errors on porting request submissions. This incident has been resolved. (Affected: PHONE NUMBERS)

Started

Oct 22, 2026, 5:10 PM UTC

Resolved

Oct 22, 2026, 7:30 PM UTC

Duration

2h 20m

PHONE NUMBERS
InvestigatingOct 22, 5:10 PM

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.

InvestigatingOct 22, 5:24 PM

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.

IdentifiedOct 22, 6:16 PM

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.

MonitoringOct 22, 7:03 PM

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.

ResolvedOct 22, 7:30 PM

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