Ciptex incident
Twilio - Voice Call Failures from a Subset of Twilio Phone Numbers to Vodafone to the United Kingdom of Great Britain and Northern Ireland
Ciptex experienced a minor incident on September 23, 2026 affecting Twilio PSTN and Twilio Voice, Europe, lasting 1d 3h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Sep 23, 2026, 07:35 PM UTC
We have detected potential service disruption through our monitoring systems and are actively investigating. A detailed assessment of the impact and affected services will be provided within the next 30 minutes.
- identified Sep 23, 2026, 07:39 PM UTC
Twilio customers may be experiencing voice call failures from a subset of Twilio Phone Numbers to Vodafone network subscribers in the United Kingdom of Great Britain and Northern Ireland. The Twilio engineering 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 Sep 23, 2026, 11:11 PM UTC
Twilio customers may be experiencing voice call failures from a subset of Twilio Phone Numbers to Vodafone network subscribers in the United Kingdom of Great Britain and Northern Ireland. The Twilio engineering team has identified the cause, and is working to resolve the issue. We will provide another update in 8 hours or as soon as more information becomes available.
- identified Sep 24, 2026, 07:17 AM UTC
Twilio customers may be experiencing voice call failures from a subset of Twilio Mobile Numbers to Vodafone network subscribers in the United Kingdom. Twilio has identified the cause, and is working to resolve the issue. We will provide another update in 8 hours or as soon as more information becomes available.
- identified Sep 24, 2026, 10:52 AM UTC
Twilio customers may be experiencing voice call failures from a subset of Twilio Phone Numbers to Vodafone network subscribers in the United Kingdom. Twilio team has identified the cause, and is working to resolve the issue. We will provide another update in 16 hours or as soon as more information becomes available.
- resolved Sep 24, 2026, 11:25 PM UTC
Following comprehensive monitoring, we can confirm that the incident has been fully resolved and all services have returned to normal operation.