Ciptex incident

Twilio - Voice Call Failures and Post Dial Delay from Twilio Phone Numbers to DigiMobil Spain

Minor Resolved View vendor source →

Ciptex experienced a minor incident on October 1, 2026 affecting Twilio Voice, Europe, lasting 12h 10m. The incident has been resolved; the full update timeline is below.

Started
Oct 01, 2026, 10:45 AM UTC
Resolved
Oct 01, 2026, 10:55 PM UTC
Duration
12h 10m
Detected by Pingoru
Oct 01, 2026, 10:45 AM UTC

Affected components

Twilio Voice, Europe

Update timeline

  1. investigating Oct 01, 2026, 10:45 AM 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.

  2. investigating Oct 01, 2026, 10:50 AM UTC

    Twilio customers may be experiencing voice call failures and post dial delay from Twilio Phone Numbers to DigiMobil network subscribers in Spain. Twilio team is actively investigating this issue. We will provide another update in 1 hour or as soon as more information becomes available.

  3. identified Oct 01, 2026, 11:25 AM UTC

    Twilio customers may be experiencing voice call failures and post dial delay from Twilio Phone Numbers to network subscribers in Spain. Twilio 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.

  4. monitoring Oct 01, 2026, 01:35 PM UTC

    Twilio have observed a recovery in voice calls from Twilio Phone Numbers to network subscribers in Spain and are monitoring service stability. We will provide another update in 2 hours or as soon as more information becomes available.

  5. monitoring Oct 01, 2026, 03:31 PM UTC

    Twilio have observed a recovery in voice calls from Twilio Phone Numbers to DigiMobil network subscribers in Spain and are monitoring service stability. We will provide another update in 4 hours or as soon as more information becomes available.

  6. resolved Oct 01, 2026, 10:55 PM UTC

    Following comprehensive monitoring, we can confirm that the incident has been fully resolved and all services have returned to normal operation.