Twilio: SMS Delivery Delays and Failures between a Subset of Twilio Long Codes and Multiple Networks in South Africa
Affected components: CARRIER NETWORK - SMS, Middle East & AfricaSMS, Middle East & Africa
Timeline of updates
- investigating
Twilio customers may be experiencing SMS delivery delays between a subset of Twilio Long Codes and multiple networks in South Africa. 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 delays and failures between a subset of Twilio Long Codes and network subscribers on multiple networks in South Africa. 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 delays and failures between a subset of Twilio Long Codes and network subscribers on multiple networks in South Africa. Our team has identified the cause, and is working to resolve the issue. We will provide another update in 2 hours or as soon as more information becomes available.
- monitoring
We have observed a recovery in SMS delivery between a subset of Twilio Long Codes and network subscribers on multiple networks in South Africa 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 between a subset of Twilio Long Codes and network subscribers on affected networks in South Africa is operating normally.
Changes Rewindex caught on this incident
- Incident updated: SMS Delivery Delays and Failures Between a Subset of Twilio Long Codes and Multiple Networks in South Africa
- Incident updated: SMS Delivery Delays between a Subset of Twilio Long Codes and Multiple Networks in South Africa
- Incident updated: SMS Delivery Delays and Failures between a Subset of Twilio Long Codes and Multiple Networks in South Africa
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-27 checkpoint, timestamped by DigiCert and FreeTSA on . Record hash
777065d13f39163e…Version 2 captured
In the 2026-10-27 checkpoint, timestamped by DigiCert and FreeTSA on . Record hash
65dc602601e875ac…Version 3 captured
In the 2026-10-27 checkpoint, timestamped by DigiCert and FreeTSA on . Record hash
1f74fffa4d6d3a10…Version 4 captured
In the 2026-10-27 checkpoint, timestamped by DigiCert and FreeTSA on . Record hash
d9c3edf174807caf…
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 2026-10-27 01:34 UTC, resolved after 3.7 h, 5 update(s); edited after publishing.
- Title
- SMS Delivery Delays and Failures between a Subset of Twilio Long Codes and Multiple Networks in South Africa
- Vendor
- Twilio
- Date
- URL
- https://rewindex.com/company/twilio/incidents/mr1t016jmyc4
Twilio profileRecent Twilio incidentsAll outages on October 27, 2026Twilio in October 2026MarkdownJSON