Twilio outage on October 22, 2026: Issue with 500 Errors on Porting Request Submissions

Twilio reported an incident affecting Twilio for 2 hours 20 minutes on 22 October 2026, from 17:10 to 19:30 UTC.

www.twilio.com All times UTC

Resolved

Official incident reported by Twilio

Started: 17:10; 22 Oct 2026 UTC
Resolved: 19:30; 22 Oct 2026 UTC
Duration: 2h 20m; 2 hours 20 minutes
Impact: Minor; as rated by Twilio
Updates: 5; posted by Twilio

Timeline

All times UTC.

Official incident from Twilio

Issue with 500 Errors on Porting Request Submissions

Resolved Minor impact 22 Oct 2026 17:10 UTC View on Twilio's status page

17:10 Official
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.
17:24 Official
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.
18:16 Official
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 [email protected] at this time. We will provide another update in 2 hours or as soon as additional information is available.
19:03 Official
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.
19:30 Official
Resolved
We are no longer experiencing an issue with 500 errors on porting request submissions. This incident has been resolved.

"Official" rows are quoted from Twilio's public status page, status.twilio.com. Very long posts are shortened.

What our checkpoints saw

HostTracker's checkpoints, which test www.twilio.com from several locations, recorded no outage of 5 minutes or longer during this incident. A provider can report a problem that affects only some features, regions or accounts, which a check of the main address does not see. The live Twilio status shows what our checks see right now.

All Twilio incidents Live Twilio status Every service we track

Does your product depend on Twilio?

An outage like this one reaches your users through your product, and most teams hear about it from a customer rather than from a dashboard. HostTracker watches any endpoint you name - your own site, an API you call, a vendor you resell - from 300+ locations, confirms a failure from several of them before it says anything, and then tells you by email, SMS, voice call or your chat tool.

You get the same record you are reading here for your own services: every outage timestamped, with the checks that observed it.

Start monitoring free Check another address

Independent measurement by HostTracker. Not affiliated with Twilio. Official updates are quoted from Twilio's public status page and remain Twilio's own words.