Twilio experienced a minor incident on May 8, 2026 affecting Console and Flex Application Platform and 1 more component, lasting 8h 22m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating May 07, 2026, 11:46 PM UTC
Our monitoring systems have detected a potential issue with errors when receiving updates from Sync. Our engineers have been alerted and are investigating. We will provide an update when we have more details.
- investigating May 08, 2026, 12:13 AM UTC
We are investigating intermittent 5xx errors in across APIs. We expect to provide another update in 15 minutes or as soon as more information becomes available.
- investigating May 08, 2026, 12:27 AM UTC
We are continuing to investigate an issue with intermittent 5xx errors in across APIs. We expect to provide another update in 30 minutes or as soon as more information becomes available.
- investigating May 08, 2026, 01:27 AM UTC
We are continuing to investigate the cause of the degradation to several Twilio products and work to fully remediate all impacts. We will provide another update in 30 minutes or as soon as we have more information.
- investigating May 08, 2026, 01:31 AM UTC
We are continuing to investigate the cause of the degradation to several Twilio products and work to fully remediate all impacts. We will provide another update in 30 minutes or as soon as we have more information.
- investigating May 08, 2026, 02:05 AM UTC
We are continuing to investigate the cause of the degradation to several Twilio products and work to fully remediate all impacts. We will provide another update in 30 minutes or as soon as we have more information.
- investigating May 08, 2026, 02:13 AM UTC
Some customers may be experiencing higher than normal latency. Our team is actively investigating the issue and we will provide another update in 30 minutes or as soon as more information becomes available.
- investigating May 08, 2026, 02:50 AM UTC
Some customers may be experiencing higher than normal latency. Our team is actively investigating the issue and we will provide another update in 30 minutes or as soon as more information becomes available.
- investigating May 08, 2026, 02:59 AM UTC
We are continuing to investigate this issue.
- investigating May 08, 2026, 03:09 AM UTC
We are continuing to investigate this issue.
- investigating May 08, 2026, 03:34 AM UTC
We are continuing to investigate the cause of degradation impacting few Twilio products and are working to fully remediate the issue. We will provide another update in 30 minutes or as soon as we have more information.
- investigating May 08, 2026, 04:38 AM UTC
We are continuing to investigate the cause of degradation impacting few Twilio products and are working to fully remediate the issue. We will provide another update in 30 minutes or as soon as we have more information.
- investigating May 08, 2026, 05:11 AM UTC
We are continuing to investigate the cause of degradation impacting few Twilio products and are working to fully remediate the issue. We will provide another update in 30 minutes or as soon as we have more information.
- investigating May 08, 2026, 05:45 AM UTC
We are continuing to investigate the cause of degradation impacting few Twilio products and are working to fully remediate the issue. We will provide another update in 30 minutes or as soon as we have more information.
- monitoring May 08, 2026, 05:55 AM UTC
All Twilio products are now observing recovery. We are continuing to monitor the issue and are awaiting further updates from our vendor. We will provide another update in 30 minutes or as soon as more information becomes available.
- monitoring May 08, 2026, 06:23 AM UTC
All Twilio products are now observing recovery. We are continuing to monitor the issue and are awaiting further updates from our vendor. We will provide another update in 30 minutes or as soon as more information becomes available.
- monitoring May 08, 2026, 06:49 AM UTC
All Twilio products are now observing recovery. We are continuing to monitor the issue and are awaiting further updates from our vendor. We will provide another update in 2 hours or as soon as more information becomes available.
- resolved May 08, 2026, 08:36 AM UTC
This incident has been resolved, and all affected services are operating normally.