Minor impactResolvedCommunication

Twilio incident: SMS Delivery Failures from Twilio Phone Numbers to AT&T Mexico

Twilio reported this minor-impact incident on its official status page on May 14, 2026, 21:07 UTC. It was resolved after 9 min.

Right now Twilio is operational. Live Twilio status →

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

May 14, 2026, 21:07 UTC

started

May 14, 2026, 21:16 UTC

resolved

9 min

duration

Minor

impact

Timeline

updates from Twilio's status page ↗

resolvedMay 14, 2026, 21:16 UTC
The incident has been resolved and SMS delivery from Twilio Phone Numbers to AT&T network subscribers in Mexico is operating normally.

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
Shippo: Royal Mail InterSoft Tracking Degradation (Third-Party Issue)Minor · May 4, 2026, 20:48 UTC
Linode: [DirtyFrag] Linux Privilege Escalation VulnerabilityMinor · May 8, 2026, 13:40 UTC
Linode: [Fragnesia] Linux Privilege Escalation VulnerabilityMinor · May 13, 2026, 21:02 UTC
Expo: High queue times and concurrency errors for Android buildsMinor · May 14, 2026, 17:12 UTC
Anthropic: Elevated errors on Claude Opus 4.7Minor · May 14, 2026, 20:33 UTC

How often does Twilio have incidents?

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

← Previous: SMS Delivery Failures between Twilio Phone Numbers and AT&T in Mexico (May 14, 2026)Next: Voice Call Audio Quality Degradation from a Subset of Twilio Phone Numbers to United States (May 15, 2026) →