- Level
- confirmed
- Worst impact
- Degraded
- Components
- PHONE NUMBERS
- Regions
- us
- Down Index
- 23of 100
What to do
Check whether you use Twilio PHONE NUMBERS in us. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 2h 20m it lasted.
Anything that failed between 2026-10-22 17:10 UTC and 2026-10-22 19:30 UTC may need a replay.Subscribe to Twilio's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=twilio works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Twilio 5
- 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.
provider
- 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.
provider
- 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.
provider
- 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.
provider
- resolved
We are no longer experiencing an issue with 500 errors on porting request submissions. This incident has been resolved.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-16896cc0a2
Is Twilio still down?
No, this incident was resolved 2026-10-22 19:30 UTC. For Twilio's live state, see https://down.guide/twilio.
How long did it last?
2h 20m, from 2026-10-22 17:10 UTC to 2026-10-22 19:30 UTC, by the times Twilio posted.
What was affected?
Twilio named PHONE NUMBERS in us.
What caused it?
Twilio hasn't published a root cause. If it does, it shows here.
Where does this come from?
Twilio's official status page, https://status.twilio.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.