← Back to Twilio History
minor✓ Resolved
Degradation to multiple Twilio products
Status
resolved
Duration
8h 54m
Updates
17
Coverage
0 articles
INCIDENT TIMELINE
✓ ResolvedFri, May 8, 2026, 08:40 AM
This incident has been resolved.
monitoringFri, May 8, 2026, 06:49 AM
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.
monitoringFri, May 8, 2026, 06:23 AM
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.
monitoringFri, May 8, 2026, 05:55 AM
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.
investigatingFri, May 8, 2026, 05:45 AM
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.
investigatingFri, May 8, 2026, 05:11 AM
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.
investigatingFri, May 8, 2026, 04:38 AM
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.
investigatingFri, May 8, 2026, 03:34 AM
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.
investigatingFri, May 8, 2026, 03:09 AM
We are continuing to investigate this issue.
investigatingFri, May 8, 2026, 02:59 AM
We are continuing to investigate this issue.
investigatingFri, May 8, 2026, 02:50 AM
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.
investigatingFri, May 8, 2026, 02:13 AM
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.
investigatingFri, May 8, 2026, 02:05 AM
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.
investigatingFri, May 8, 2026, 01:31 AM
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.
investigatingFri, May 8, 2026, 01:27 AM
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.
investigatingFri, May 8, 2026, 12:27 AM
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.
investigatingFri, May 8, 2026, 12:13 AM
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.
investigatingThu, May 7, 2026, 11:46 PM
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.
📊 TECHNICAL DETAILS
Internal ID
7783b19c-cdc5-4c35-acab-eda9c88425ef
External ID
rqlltbpn6m1z
🕐 Started
Thu, May 7, 2026, 11:46 PM
🔄 Last Updated
Fri, May 8, 2026, 08:40 AM
✓ Resolved
Fri, May 8, 2026, 08:40 AM
MINOR
Impact Level
8h 54m
Total Duration
17
Status Updates
Affected Components
ConsoleFlex Application PlatformVerifyEvent StreamsDebugger & AlarmsFlex InsightsBillingDocumentationFlex Agent DesktopREST APISyncFlex Queue StatsBulk ExportFlex Teams ViewFlex Admin ConsoleFlex RoutingFlex ConversationsCustomer Support CenterFlex Programmable ChatMMSVoice Insights US1OtherFlex Programmable VoiceSMSAccount InsightsProxySMPPTrust HubFlex PluginsMessaging ChannelsFlex BillingOrganizationNotifyConversationsMessaging ServicesContent APIVoice REST API US1RCS MessagingProgrammable Messaging APIIntelligent Alerts
REQUEST COVERAGE
No article has been written for this incident yet. When 100 people request coverage, we automatically generate one.
0 / 100 requests100 more needed