Twilio: Issue with 500 Errors on Porting Request Submissions
Affected components: PHONE NUMBERS
Timeline of updates
- 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.
- investigating
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. - 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. - 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.
- resolved
We are no longer experiencing an issue with 500 errors on porting request submissions. This incident has been resolved.
Changes Rewindex caught on this incident
- Incident updated: Issue with 500 Errors on Porting Request Submissions
- Incident updated: Issue with 500 Errors on Porting Request Submissions
- Incident updated: Issue with 500 Errors on Porting Request Submissions
- Incident updated: Issue with 500 Errors on Porting Request Submissions
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-22 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
6101ab66f3ffc951…Version 2 captured
In the 2026-10-22 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
ded9d0c11bb06734…Version 3 captured
In the 2026-10-22 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
18f1d85661ea9aef…Version 4 captured
In the 2026-10-22 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
61b4394b48cfab99…Version 5 captured
In the 2026-10-22 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
2dc233c129d62be7…
Impact, status and times are the vendor’s own, as last archived. View on status.twilio.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Twilio, started 2026-10-22 17:10 UTC, resolved after 2.3 h, 5 update(s); edited after publishing.
- Title
- Issue with 500 Errors on Porting Request Submissions
- Vendor
- Twilio
- Date
- URL
- https://rewindex.com/company/twilio/incidents/r6x5tb0y1s5h
Twilio profileRecent Twilio incidentsAll outages on October 22, 2026Twilio in October 2026MarkdownJSON