Twilio: SMS Delivery Failures from a Subset of Twilio Alphanumeric Sender IDs to United Arab Emirates
Affected components: CARRIER NETWORK - SMS, Middle East & AfricaSMS, Middle East & Africa
Timeline of updates
- investigating
Twilio customers may be experiencing SMS delivery failures from a subset of Twilio Alphanumeric Sender IDs to Etisalat network subscribers in the United Arab Emirates. Our team is actively investigating this issue. We will provide another update in 1 hour or as soon as more information becomes available.
- identified
Twilio customers may be experiencing SMS delivery failures from a subset of Twilio Alphanumeric Sender Type to Etisalat network subscribers in the United Arab Emirates. Our team has identified the cause, and is working to resolve the issue. We will provide another update in 1 hour or as soon as more information becomes available.
- identified
Twilio customers may be experiencing SMS delivery failures from a subset of Twilio Alphanumeric Sender Type to the United Arab Emirates. Our team has identified the cause, and is working to resolve the issue. We will provide another update in 1 hour or as soon as more information becomes available.
- monitoring
We have observed a recovery in SMS delivery from a subset of Twilio Alphanumeric Sender IDs to the United Arab Emirates and are monitoring service stability. We will provide another update in 2 hours or as soon as more information becomes available.
- resolved
The incident has been resolved and SMS delivery from a subset of Twilio Alphanumeric Sender IDs to the United Arab Emirates is operating normally.
Changes Rewindex caught on this incident
- Incident updated: SMS Delivery Failures from a Subset of Twilio Alphanumeric Sender Type to Etisalat United Arab Emirates
- Incident updated: SMS Delivery Failures from a Subset of Twilio Alphanumeric Sender Type to United Arab Emirates
- Incident updated: SMS Delivery Failures from a Subset of Twilio Alphanumeric Sender IDs to United Arab Emirates
- Incident updated: SMS Delivery Failures from a Subset of Twilio Alphanumeric Sender IDs to United Arab Emirates
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-20 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
971dd4fe17f1567c…Version 2 captured
In the 2026-10-20 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
4d052f4be0661eaa…Version 3 captured
In the 2026-10-20 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
08003c1e81477b9c…Version 4 captured
In the 2026-10-20 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
8e0d7a6b76fba99e…Version 5 captured
In the 2026-10-21 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
d5c9630193f13a9d…
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Twilio, started 2026-10-20 20:45 UTC, resolved after 3.8 h, 5 update(s); edited after publishing.
- Title
- SMS Delivery Failures from a Subset of Twilio Alphanumeric Sender IDs to United Arab Emirates
- Vendor
- Twilio
- Date
- URL
- https://rewindex.com/company/twilio/incidents/pwfkkq1r3jgd
Twilio profileRecent Twilio incidentsAll outages on October 20, 2026Twilio in October 2026MarkdownJSON