Twilio: SMS Delivery Failures to Syriatel in Syria
Timeline of updates
- resolved
Our engineers have identified the root cause of the SMS delivery failures to Syriatel in Syria. The carrier has begun enforcing Sender ID registration. This means messages to Syriatel can only be delivered when sent from a registered alphanumeric Sender ID; no other Sender ID types are supported. Please note that in July 2025, Twilio announced through direct customer communications that SMS delivery to Syria will no longer be supported starting September 15, 2025. Customers were advised to remove Syria traffic from Twilio and transition to alternative messaging providers. From now until September 15, 2025, SMS delivery to Syriatel in Syria will be on a best-effort basis only. If messages fail, Twilio will not be able to provide troubleshooting support. After September 15, 2025, all messaging traffic to Syria will be blocked.
From Twilio’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
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.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.twilio.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Twilio, started 2025-08-21 03:45 UTC, resolved after 26 h, 1 update(s).
- Title
- SMS Delivery Failures to Syriatel in Syria
- Vendor
- Twilio
- Date
- URL
- https://rewindex.com/company/twilio/incidents/t3mgzc13d0sp
Twilio profileRecent Twilio incidentsAll outages on August 21, 2025Twilio in August 2025MarkdownJSON