Minor impactResolvedCommunication

Twilio incident: Phone Numbers Porting are failing in both Twilio Console and API

Twilio reported this minor-impact incident on its official status page on May 11, 2026, 02:06 UTC. It was resolved after 2h 21m.

Right now Twilio is operational. Live Twilio status →

🔔 Get alerted when Twilio has issuesFree · email alerts · no credit card

May 11, 2026, 02:06 UTC

started

May 11, 2026, 04:27 UTC

resolved

2h 21m

duration

Minor

impact

Timeline

updates from Twilio's status page ↗

resolvedMay 11, 2026, 04:27 UTC
We are no longer experiencing phone numbers porting in both Twilio console and our API. This incident has been resolved.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Twilio's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

Confluent Cloud: Elevated error rates and latency on produce and consume operations on AWS us-east-1 AZ4Major · May 8, 2026, 01:14 UTC
Intercom: Investigating: Compromised version of intercom-client npm package and intercom-phpMinor · Apr 30, 2026, 16:58 UTC
Shippo: Royal Mail InterSoft Tracking Degradation (Third-Party Issue)Minor · May 4, 2026, 20:48 UTC
Snyk: Snyk Recurring Tests DelayedMinor · May 6, 2026, 15:32 UTC
Linode: [DirtyFrag] Linux Privilege Escalation VulnerabilityMinor · May 8, 2026, 13:40 UTC

How often does Twilio have incidents?

Twilio reported 500 incidents in the last 90 days, 2 of them major or critical. A typical incident lasted 5h 48m. See Twilio's uptime and incident history

← Previous: SMS Delivery Delays from Twilio to Digitel Venezuela (May 10, 2026)Next: SMS Delivery Delays and Failures from a Subset of Twilio Long Codes to CAMTEL Cameroon (May 11, 2026) →