Twilio incident: SMS Delivery Delays and Failures from a Subset of Twilio Phone Numbers to Rakuten Japan

1. resolvedMay 29, 2026, 07:52 UTC

   The incident has been resolved and SMS delivery from a subset of Twilio Phone Numbers to Rakuten network subscribers in Japan 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.

• OVHcloud: [GRA5/7/9/11][Compute - Instance] - Some Instances Incident NotificationMajor · May 28, 2026, 10:14 UTC
• ReadMe: Refactored Hubs DownMajor · May 28, 2026, 14:35 UTC
• Elasticsearch: Upstream Azure Outage Causing Service DegradationMajor · May 29, 2026, 06:32 UTC
• Snowflake: Azure - West US 2 (Washington): INC0157956Major · May 29, 2026, 06:47 UTC
• Confluent Cloud: Elevated error rates and latencies in Azure westus2 regionMajor · May 29, 2026, 06:47 UTC
• Akamai: Reporting Issues affecting URL Traffic and URL Responses reportsMinor · May 19, 2026, 10:13 UTC
• OVHcloud: [GRA/RBX/DE][Storage and Backups] - Object Storage Incident NotificationMinor · May 22, 2026, 15:04 UTC
• ClickHouse Cloud: New service provisioning may fail in AzureMinor · May 28, 2026, 18:26 UTC
• DigitalOcean: App Platform DeploymentsMinor · May 29, 2026, 00:14 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