Ciptex incident

Twilio - degradation to multiple services

Major Resolved View vendor source →

Ciptex experienced a major incident on May 8, 2026 affecting Twilio Messaging Channels and Twilio Sync and 1 more component, lasting 8h 8m. The incident has been resolved; the full update timeline is below.

Started
May 08, 2026, 12:32 AM UTC
Resolved
May 08, 2026, 08:40 AM UTC
Duration
8h 8m
Detected by Pingoru
May 08, 2026, 12:32 AM UTC

Affected components

Twilio Messaging ChannelsTwilio SyncTwilio SMS, EuropeTwilio SMSTwilio ConversationsTwilio SMS, EuropeTwilio ConsoleTwilio REST APITwilio VerifyTwilio Flex ConversationsTwilio Flex Programmable ChatTwilio Flex Programmable VoiceTwilio Flex PluginsTwilio Flex Queue StatsTwilio Flex Agent DesktopTwilio Flex RoutingTwilio Event StreamsTwilio Messaging Services

Update timeline

  1. investigating May 08, 2026, 12:32 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 May 08, 2026, 12:45 AM UTC

    Twilio monitoring systems have detected an intermittent issue causing 5.xx errors affecting their APIs. We will update you when we know more.

  3. investigating May 08, 2026, 02:36 AM UTC

    This issue appears to be related to an ongoing issue affecting AWS in the US-EAST-1 region. We are actively monitoring the situation and will update you when we know more.

  4. investigating May 08, 2026, 03:18 AM UTC

    We continue to monitor the degradation affecting multiple Twilio products. Customers may experience higher than normal wait times as a result. We will update you in 2 hours, or sooner if we have more information.

  5. monitoring May 08, 2026, 07:32 AM UTC

    Twilio products are now observing recovery. We are continuing to monitor the issue and are awaiting further updates. We will provide another update in 2 hours or as soon as more information becomes available

  6. resolved May 08, 2026, 08:40 AM UTC

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