Minor impactResolvedCommunication

Twilio incident: Messages delayed on RCS and WhatsApp

Twilio reported this minor-impact incident on its official status page on May 13, 2026, 01:57 UTC. It was resolved after 1h 39m.

Right now Twilio is operational. Live Twilio status →

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

May 13, 2026, 01:57 UTC

started

May 13, 2026, 03:36 UTC

resolved

1h 39m

duration

Minor

impact

Timeline

updates from Twilio's status page ↗

resolvedMay 13, 2026, 03:36 UTC
The issue has been resolved and we are no longer experiencing delays on RCS and WhatsApp messages.

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
Linode: [DirtyFrag] Linux Privilege Escalation VulnerabilityMinor · May 8, 2026, 13:40 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: Customer Low Balance Notification and Automatic Recharge of Balance Is Not Working (May 12, 2026)Next: SMS Delivery Delays from Twilio to Tigo Honduras (May 13, 2026) →