SendGrid: 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.
How the archive is checked, and what it cannot prove.
Rewindex captured this after the last checkpoint; the next run () commits it.
Impact, status and times are the vendor’s own, as last archived. View on status.sendgrid.com (opens in new tab).